what the verification pass found: momentum truth, load-time signing, utterances that reach their listeners, and docs that match

[radicalkjax]

I read the alignment plan end to end and had every phase re-read against the source, with no keyword search: files located by listing, then read whole. Most of the plan holds. This branch fixes what did not, and corrects the record where the register was wrong.

Momentum counted things that were not work. Idle ticks were handled, but a carried-over dispatch reported alignment 0.8, a merely-claimed task 1.0, a sacrifice yield 0.9, and the observe, suggest and no-task paths returned 1.0 whenever they carried a descriptor. One hung connector call could walk a formation to Fever while also keeping the member marked alive. The action state the plan specified for the tick report was never added; it is now, sourced from the execution outcome, and a tick counts only when a member finished work. A test drives a hung dispatch for fifty beats and asserts the formation stays Cold.

Signing was required at install but not at load. Stored WASM rows whose signature columns were empty were grandfathered at every boot with a warning. They are now refused, naming the connector and telling the operator to reinstall it, with no migration and no override, because the project's own rule is that signatures are verified before load. A test in the tree asserted the old grandfathering; it is inverted rather than deleted.

Two more ways the gate could be bypassed. The auto-allow approval gate was a production export that any caller could hand to the sentinel, silently disabling the human gate; it is now test-only. POST /workspaces/onboard was mounted in the stream-ticket router, so a mutating route was authenticated by a single-use ticket outside the cross-site protection; it now takes the same bearer as every other mutating route, keeping its streaming response, and its client sends the bearer instead of minting a ticket. The premise that streaming forced it there did not hold: tickets exist for the browser event source, which is read-only, and this route always took a body.

Utterances did not reach their listeners. Server-side agent activity still came from the last two hundred events rather than the utterance ring, so the daemon and the browser could disagree about what an agent was doing. And what a peer heard was overwritten by the gossip step later in the same tick, so nothing acted on it. Both are fixed, and a heard failure now has a real consumer: it weighs into the morale that cascade detection reads.

Rally. It double-counted a failure the momentum step had already recorded, it rallied the first failing member rather than one who can still respond, and its recovered outcome was constructed nowhere. All three are fixed, with a shattered-morale floor so a token is never spent on a member who cannot answer.

Documents that no longer matched. The API and CLI references still described the retired passphrase-derived token, as did the architecture and security documents, the operations pages, and the project's own security rule. The API reference still listed the deleted template routes and an onboarding platform list that was never true. The quickstart taught an environment-variable passphrase while the compose file deliberately uses a secret file. The workspace manifest claimed a Matrix source tree that is not in the repository. The connector guideline still described a per-connector TOML manifest file, and did not mention the two action fields added since. All corrected against the code, and the intended-architecture directory left alone deliberately, since the current-architecture documents supersede it.

Verification: workspace clippy -D warnings clean, cargo fmt --check clean, 1013 cooperation, bot and runtime tests plus the daemon suite green, frontend typecheck, lint and build clean, and the served contract regenerated from the handlers so it matches the moved route.

🤖 Generated with Claude Code

https://claude.ai/code/session_018M415coMKAv5V2xJQsaSf8