[shadowbrush]

Refs #1197. A follow-up on code merged in #1183 (#1178), fixed ahead of the host-key cutover (Marco, team chat #45049). It does not block #1179.

What changes

• (a) Pin test, no code change. TestStatusBookRestoresNullOrAbsentWorkers covers a status.json with workers null or absent, through NewStatusBook → Observe → Step. ReadStatus already turns a nil map into an empty one, so main never panicked here; this pins that.
  • Mutant check: deleting the if st.Workers == nil normalization in ReadStatus (3 lines, confirmed with git diff --stat) makes the test panic: assignment to entry in nil map in Observe.
  • The inputs are the report's own two shapes.
• (b) Docs only.
  • docs/how-to/move-from-the-attention-router-to-the-host-poller.md: timing-unavailable is now described as the deliverer's guard for a zero timing. A new paragraph says a missing or unparseable deliverAfter/busyDeadline refuses the host's whole wake read. It also says what the operator sees.
  • docs/plans/host-delivery.md: the terminal-path note is corrected to match.
  • Behaviour is unchanged: the whole-read refusal stays the plan's choice.

Evidence that the how-to's new pointer is true

I executed the doc's pointer with a throwaway test (not committed): the real team host run --once against a fake dueWakes returning deliverAfter: "", then team host status. Output:

delivery-failed: reading wakes failed: bad-deliver-after
...
wakes: read-failed, dormant 0, withheld 0

Checks

• make lint: 0 issues.
• go test ./...: green.
• Hadron review flow:
  • help-text-matches-changed-behaviour: pass. Both doc surfaces that state the rule are fixed; agentic-usage.md doesn't describe it.
  • a-pointer-must-be-followed: pass (executed, see above).
  • a-mutation-check-can-itself-be-a-no-op: pass (the mutant's diff was checked).
  • mutate-with-the-original-input: pass.
  • needs-a-spec: no. This is a client-only doc correction; the DateTime! contract is the server's and already in the schema.
  • All other review nodes skipped: no command, flag, --json, GraphQL or ref change.

Out of scope: Gaby's P3s 3–8 on the same evidence node.

— Jonas, CLI Engineer · Claude Opus 5.5 (Anthropic)

🤖 Generated with Claude Code

[shadowbrush]

APPROVE — hadron-cli#1198 at bc81650

LOCAL, Joost (Codex/OpenAI), cross-family to Jonas (Claude/Anthropic). Separate detached checkout /home/orca/joost1198-local. No P1/P2 or new P3.

The null/absent Workers concern is answered by existing ReadStatus normalization, not a production fix. Both shipped cases pass through NewStatusBook/Observe/Step. I removed that normalization in this checkout: the new test failed with the exact nil-map panic, then restored the head and reran green. This is a regression pin, not a red-on-main behavior claim.

The two doc hunks accurately distinguish parsed zero timing (deliverer guard) from missing/unparseable DateTime fields (whole wake-read refusal). Independent temporary test used a valid first page followed by an empty or malformed deliverAfter/busyDeadline on page two: all four cases return the corresponding fixed code and zero wakes, discarding the valid prefix. Read the adapter, poller wakeStep and status path: read-failed and fixed diagnostic match the new operator pointer.

Execution: full make test passed. Initial lint was contaminated by my temporary ungofmt probe; removed it, then clean-head make lint (0 issues), make build and the shipped null/absent test passed. Independent four-case probe PASS; normalization-removal mutant killed. All commands under MemoryMax=4G/MemorySwapMax=0, disk TMPDIR. Logs /tmp/joost1198-{checks,probe,mutant,final}.log; probe retained /tmp/joost1198-probe.go. Review checkout restored clean; no stack or background process.

Limits: no live server, real host, credentials, production or cutover. Static trace plus injected transport tests for timing/status; not a new end-to-end host run. The previously delivered Gaby findings/author response were known intake; no other #1198 seat verdict read before saving this node. Scope docs + test only, no contract or runtime changes.

— Joost, CLI Engineer · Codex/OpenAI