vault, starters, ingress: the daemon locks, templates go, webhooks reach their connector (plan 6.9, 6.10, and fixes)

[radicalkjax]

Six pieces in one branch: four recorded defects, then the remaining phase 6 items and two gaps earlier work uncovered.

Four defects that a documentation pass had recorded but not fixed.

• Guard mode was captured at deploy, so turning it on protected nothing until redeploy. It was worse than documented: a spawned formation built default constraints, so guard was off even after a redeploy. The toggle now reaches the live formation over the same command channel the other operator verbs use, spawning seeds from the stored row, and every read goes through one accessor. A test flips all five guarded verbs on a live formation with no redeploy.
• A dissolve outcome reported a hardcoded zero failures, in both the gossip record and the durable note. It now reports the lifetime interference count, with a test.
• The autonomy colour array still had five entries after the labels were cut to four.
• The 1265-line dispatch module is split into a module directory, one concern per file, as the crate-structure rule requires. Pure move; every public path stays where it was.

The daemon locks instead of being killed (6.10, finding 113). Following the Secret Service model the plan cites, locking drops the key rather than fencing it: chat sources unwire, the scheduler and heartbeat pause, stream tickets clear, tasks are aborted and joined, the vault locks, and the runtime is dropped so the database handle closes. While locked the router serves only health, readiness reporting the locked state, and unlock, which reruns the boot pipeline. A test asserts the store handle is actually dropped, which any flag-based lock would fail. Sessions clear on lock, so a token minted before a lock cannot be replayed after one.

One way to start (6.9, finding 112). The template system is deleted entirely: the operations module, the routes, the command, the initialisation argument, and the interface types. The two scaffolds the recipe catalogue lacked are added as builtin recipes. Documentation follows.

Webhook ingress. The webhook route verified a signature and then hardcoded one connector's field extraction, so no other connector's webhook could produce chat. Connectors now ingest their own verified payloads, implemented for Telegram and Kick, which is what makes Kick chat arrive at all.

A bridge for subprocess clients. springtale mcp serve forwards a client that can only launch a subprocess onto the daemon's authenticated endpoint. It holds no protocol logic.

Plan errors found and worked around, all recorded: the session map the lock item assumed lives elsewhere, the HTTP middleware crate has no rate limiter so the existing pattern was used, the lock cannot live in the runtime crate because it must drop the runtime, unlock has nothing to compare in constant time since it derives a key, and the starter list is fourteen rather than eight, so six were dropped rather than mapped.

One behaviour change to know: boot no longer exits when the bot loop stops, because after a lock there is no bot loop and the daemon must stay up to accept the unlock.

Verification: clippy -D warnings clean across six crates; 24 test binaries green including ten lock tests; the surface check passes at 123 routes; the contract was regenerated the way CI does; frontend typecheck, lint and build pass.

🤖 Generated with Claude Code

https://claude.ai/code/session_018M415coMKAv5V2xJQsaSf8