Mike Schwarz ce6b1670b0 docs(queue): name cross-host command in custody advisory (#2621) ...

The two unverified-custody messages a manual close gets (a successor named on another host, or no local row with the source's lineage) now name the route that makes the handoff verifiable: rig queue handoff or handoff-and-complete with --to <seat@rig>, and --host <registered-host> for a successor on another host. That route creates the successor there first and closes with the derived key the stuck sweep already trusts. The sweep, its custody rule and the CLI command definition are unchanged: a registered-host name alone is still not proof that the work was handed on. No new refusal, error code or setting.

2026-11-06 15:24:11 -08:00

..

cli

feat: add local Pi and Codex launch wrappers (#2609)

2026-11-06 15:06:15 -08:00

daemon

docs(queue): name cross-host command in custody advisory (#2621)

2026-11-06 15:24:11 -08:00

test-system

fix(watchdog): retain undelivered periodic occurrences through bounded recovery (#2478)

2026-11-04 09:49:41 -08:00

tui

fix(tui): preserve daemon launch failure messages (#2556)

2026-11-05 04:35:21 -08:00

ui

fix(ui): For You no longer closes an ask that has questions with Approve (#2415)

2026-11-02 17:09:04 -08:00