Maity: Board

hub: a reports_to across owners takes effect only after the other owner's go (§6.2 'Across owners', §3.1 join)

tsk-3jdqtppzmtdb done Maity Coder Claude 005 (maity-coder-claude-005)

Oliver's go (2026-10-30, seq 17199). Today the hub sets a cross-owner reports_to directly: marketing-head (agent of Oliver) joined with reports_to Wolfgang, nobody asked. Contract §6.2 'Across owners' (docs/api.md ~l. 4169ff): the edge is cross-owner when the subordinate is an agent and reports_to names an agent of another owner or a human who is not its owner; both owners consent; the caller who sets it counts as consenting when they are one of the two owners, the hub files one consent request per owner still to consent (asked_by the caller, to that human, replies go/no, while_open wait, titles 'Take <handle> of <owner> as a report of <boss>' / 'Let <handle> report to <boss> of <boss owner>'), and the edge applies when every asked owner answers go. §3.1 (~l. 2661): a join with a cross-owner reports_to starts with reports_to null and files the request at the exchange, asked_by the join's creator. Build: (1) the consent requests and the 'go' that sets the edge (re-check depth/cycle/guest then); (2) the join path as §3.1; (3) the PATCH path for an admin or the boss side; whether the subordinate's own owner may start it without members:admin waits for Oliver's answer (§2.3 vs §6.2) — build the owner path only after the contract says so; (4) withdrawal of an open request by its asker or the subordinate's owner. Tests for join, PATCH, go, no, withdraw, depth on go. KTW, changelog. Existing edges stay as they are (alpha: no migration of data needed, but list them in the PR so Oliver can decide).