The claimed execution owner binding crosses the daemon, SSH and relay boundaries,
and the two protocol constants that gate it live in `agent-session-host-authority`
and `daemon-protocol-version`. Neither path was in the cross-version lane's prefix
list, so a change that adds a required field to the owner binding and raises both
protocol versions classified as `cross-version-wire=false` and skipped the lane
entirely.
Verified with the classifier directly: this branch's changed paths now report
`cross-version-wire=true`, an unrelated renderer file still reports `false`.
The lane's existing journeys cover structured agent sessions rather than the PTY
owner binding, so this restores the trigger, not coverage of the owner binding
itself.
Brennan Benson
6c707987a5