feat(gateway): add recoverable mobile approvals

[ericlewis]

Summary

• give gateway approvals stable Hermes-owned identities, redacted lifecycle descriptors, expiry/state/resolution metadata, and short-lived terminal tombstones
• synchronize pending approvals into authoritative resume snapshots and publish matching terminal events
• add mobile-scoped, ID-targeted approval.respond with durable client_request_id receipts, stable lineage validation, replay/conflict semantics, and exact out-of-FIFO resolution
• preserve existing ID-less desktop/stdin FIFO behavior and fail closed on missing mobile choice, scope, lineage, or resource identity
• guarantee tombstone TTL cleanup with one coalesced generation-protected timer

Stack / review order

This integration branch intentionally combines the foundations under:

1. feat(gateway): negotiate scoped WebSocket grants #62858 — versioned hello and scoped WebSocket grants
2. feat(gateway): add revisioned conversation sync #63149 — revisioned snapshots and replay
3. feat(gateway): persist mobile mutation receipts #63190 — durable mobile mutation receipts

Approval recovery depends on all three seams, so this PR is the end-to-end integration review for the approval slice. It should remain draft until those foundations are reconciled.

Cuttle contract tracking: https://github.com/ericlewis/cuttle/issues/5
Parent contract: https://github.com/ericlewis/cuttle/issues/1

Safety and compatibility

• approval presentation and resolution metadata are recursively redacted server-side
• mobile responses require conversation.control, exact approval_id, durable client_request_id, and stable expected_stored_session_id
• omitted or blank mobile choices are rejected before receipt reservation or resolution
• duplicate IDs replay; changed semantics conflict; abandoned outcomes never auto-reexecute
• existing legacy ID-less FIFO and all behavior is unchanged

Validation

• 139 passed — focused approval identity + mobile contract/sync/mutation suites
• 732 passed — every test file changed by this branch relative to the revisioned-sync base
• Ruff passed on all changed Python files
• git diff --check passed
• two independent standards/spec reviews completed with no remaining findings

Eight existing async-mock warnings remain in QQ/Slack adapter tests; there were no failures.

[teknium1]

Thanks for the detailed approval-recovery work. The underlying premise remains valid on current main: tools/approval.py:1551-1568 still resolves the oldest pending approval by FIFO, and tui_gateway/server.py:10269-10286 exposes only that ID-less path. The PR’s exact-ID resolver at tools/approval.py:1800-1881 directly addresses that gap.

The branch is currently a conflicting draft (gh api repos/NousResearch/hermes-agent/pulls/63197 reports mergeable: false, rebaseable: false), while current tui_gateway/server.py, approval handling, and gateway transport code have materially moved. Salvage should therefore be treated as a fresh integration against HEAD, with the existing contract tests retained as behavioral targets rather than relying on a mechanical cherry-pick.

Automated hermes-sweeper review.