LLP 0118-0125: hermes log forwarding cluster

[philcunliffe]

What

Docs-only PR: the LLP cluster for a new @hypaware/hermes client adapter that forwards Hermes Agent activity into HypAware. All eight docs are Accepted (approved for implementation; they flip to Active as the implementation PRs land). No code.

The cluster

LLP	Type	Settles
0118	Spec	Requirements R1-R10: hermes sessions land in ai_gateway_messages, idempotent, policy-honoring, read-only against hermes, auto-ongoing, observable
0119	Decision	Capture seam: pull from ~/.hermes/state.db (canonical SQLite store); rejects a hermes-side push plugin and base_url wire attach
0120	Decision	Dataset: materialize via ai_gateway.projected_exchange with client_name='hermes'; no new table
0121	Decision	Packaging: bundled in plugins-workspace/ beside claude/codex
0122	Design	node:sqlite read-only reader, per-session watermark poll, deterministic session-end part, full projection mapping
0123	Plan	T1-T6: engines bump + reader → projector → backfill ∥ source → wiring → hermetic smoke
0124	Decision	Channel sessions (Telegram/Discord/...) get canonical policy scope path ~/.hermes/channels/<source>: default full, standard marking machinery covers local-only/ignore, no bespoke config key
0125	Decision	engines floor moves to Node >=22.12 (Node 20 is EOL; node:sqlite needed); CI gains a 22+24 matrix

Notes

• Grilled 2026-07-20: the channel-privacy scope path (0124), the session-end receipt part (0122), and the engines bump (0125) all came out of that session; id-format concerns were verified moot (graph content-addresses ids).
• Cluster was renumbered from 0115-0121 after claude-desktop-attach claimed 0115-0117.
• The cluster is neutral-drivable: 0118-0121 + 0124-0125 are the accepted request set; 0122 design and 0123 plan are accepted seeds the pipeline can execute from directly.
• ref-check is clean on all eight docs (the 91 repo-wide errors are pre-existing on master).

🤖 Generated with Claude Code