feat(gateway): add active-wake operator receipts

[verybigdog]

Summary

• Reworks the older active-wake draft into the current ACK/active-wake receipt stack.
• Keeps visible send delivery, scheduled wake, session acceptance/start, and operator receipt as separate states.
• Routes trusted internal active-wake events to the intended gateway/operator session instead of a synthetic hermes-active-wake ghost session.
• Persists ack_active_wake / ack_operator_receipt evidence for Kanban terminal ACKs.

Relationship to smaller PRs

This is the integration PR for the ACK/active-wake set. It intentionally depends on/supersets the smaller reviewable primitives:

• fix(send_message): sanitize active-wake snippets #49749 send-message active-wake sanitization
• fix(kanban): preserve ACK subscriptions across task graphs #49751 Kanban ACK subscription preservation
• fix(kanban): surface terminal ACK relay failures #49752 terminal ACK relay visibility

The earlier draft only proved that an adapter wake was scheduled. This update adds honest receipt semantics (scheduled_agent, accepted_by_session, started_by_session, active_wake_status, target_session_key) and prevents treating triggered_agent as proof of operator observation.

Tests

• python3 -m pytest tests/gateway/test_busy_session_auth_bypass.py tests/tools/test_send_message_tool.py::TestActiveWakeReceipt tests/hermes_cli/test_kanban_notify.py tests/gateway/test_api_server_runs.py::TestActiveWakeSmoke tests/hermes_cli/test_kanban_ack_ledger.py tests/hermes_cli/test_kanban_diagnostics.py -q -o addopts=
• python3 -m py_compile gateway/run.py gateway/kanban_watchers.py gateway/platforms/api_server.py hermes_cli/kanban.py hermes_cli/kanban_db.py hermes_cli/kanban_db_ack_ledger.py hermes_cli/kanban_diagnostics.py tools/send_message_tool.py
• git diff --check

Notes

• Kept draft while the prerequisite PRs are reviewed; mark ready after maintainers are comfortable with the split or if they prefer one integration PR.

[teknium1]

Thanks for separating passive delivery, scheduling, and session state. The current main limitation is real: gateway/kanban_watchers.py:517-533 says missing chat_type can route a DM creator into a fresh group session.

Problems

• tools/send_message_tool.py:701 still unconditionally creates SessionSource(chat_type="group"). gateway/session.py:907-959 gives DMs a distinct :dm: session-key shape, so an active wake for a DM target can still create or target the wrong session. The added tests exercise group routing (tests/tools/test_send_message_tool.py:3228-3262), not this DM case.
• gateway/kanban_watchers.py:606-614 writes ack_operator_receipt(status="observed") when a wake is merely accepted or started by a session. That is gateway execution evidence, not operator observation, and conflicts with the PR's stated receipt distinction.

Suggested changes

• Persist/resolve trusted chat type and required identity before constructing a wake source; add DM and group-per-user routing coverage.
• Reserve an observed operator receipt for an explicit acknowledgement, or label the existing row as session acceptance.

Automated hermes-sweeper review.

[teknium1]

This forces every active wake into the group key shape. build_session_key() uses a distinct :dm: shape for direct messages (gateway/session.py:907-915), so a DM target can wake a new group session rather than the intended operator session. Carry trusted chat_type/session identity or fail the wake when it cannot be resolved; add a DM regression test.

[teknium1]

accepted_by_session / started_by_session only show that Hermes accepted or began processing a synthetic event. They do not show that an operator observed it, so writing an ack_operator_receipt with status="observed" here overstates the evidence. Record a separate session-acceptance state, or require an explicit operator acknowledgement before this row.

[verybigdog]

Recommend absorbing the worthwhile parts of this PR and then closing it once they land. The core active-wake mechanism here duplicates #37865 but regresses it: SessionSource hardcodes chat_type=group (breaks DM routing that #37865 fixes by replaying chat_type, default 'dm'), trigger_agent/correlation_id are exposed on SEND_MESSAGE_SCHEMA (#37865 deliberately keeps wake non-model-exposed), and there is no non-default-profile fail-closed / no user_id_alt replay. The receipt vocabulary scheduled/accepted/started is sound, but 'observed' is written on agent accept/start, conflating execution evidence with operator observation — that should be reserved for an explicit operator acknowledgement. The ACK ledger is currently write-only (readers only in tests). The genuinely useful, self-contained subset — classify_ack_relay + the missing-ack-relay diagnostic — is being carried as the reviewed, standalone #49752, and the _sanitize_active_wake_text scrubber can be added to #37865 as optional hardening. Proposing closure AFTER #49752 lands and any snippet-hardening is cherry-picked; nothing is closed by this note. (This PR is not closed.)