Merge branch 'unstable' into area/client-reliability

docs/agents/CHECKIN-2026-10-26-1922-hourly.md

@@ -0,0 +1,12 @@
+# Hourly check-in 2026-10-26 19:22 UTC
+
+- Scope: fleet health, all WAITING text, landing results, daily notification deduplication, strikes and usage wind-down. No product changes or heavy validation.
+- Plan completed: read PROGRAM/WIND-DOWN/backlog/STRIKES and daily ledger; run doctor/queue/fleet status; inspect every area .task including inline WAITING; review retained adverse landing log; record new strike and owner decision; submit only this audit and STRIKES.
+- doctor --json, landq status, fleet status, landq status c20635bc, backlog list: exit0. Doctor: dispatch DIRTY21/WAITING, client ONE-DISK9, QA DIRTY10, storage behind22. Existing work retained.
+- All .task files read. Dispatch thermal WAITING since19:16Z and inline client WAITING since19:15:42Z are under2h. No overdue reminder. Storage .task still mentions its historical queued landing; durable result492557400c is landed, not a fresh blockage.
+- Fleet reports lander DOWN, queue0; workers unavailable/dead, storage stopped with1 unread, interpreter3 unread. No status says stalled; a dead/unknown window proves neither progress nor a live stall. Lander absence recorded in owner.md.
+- Retained log adds one new red c20635bc at19:15:32.782Z; durable result rejected. Existing client MCP notice19:16:19Z is in the daily ledger, so no duplicate send or ledger append. No additional conflict/withdrawal found in retained landing log. Session-only incident completeness unverified.
+- STRIKES records thermal interruption without claiming assertion failure. Two client reds within7days straddle configured Monday03:00 usage reset: current configured week1. Owner proposal conditional on rolling-week interpretation; no tier/config edit.
+- usage.enabled=false and modules.usageGovernor=false; no usage-hook query or PAUSED creation. Latest40 wake records contain no five-hour-nearly-gone warning; panes not scraped.
+- No lint/unit/build/browser rerun for Markdown-only audit during thermal hold. No product/main/live qualification, real session liveness, worker acknowledgement or hold-compliance verification.
+- Verification: git diff --check limited to audit files before commit; docs-only landing result and target ancestry checked separately after submission.

docs/agents/STRIKES.md

@@ -24,3 +24,17 @@ conflicts appear in the retained landing log; no additional confirmed reviewer,
 peer false-green, or owner-regression event was identified in the checked
 dispatch mailbox, PROGRAM, backlog and fleet log. This is not a complete audit
 of every session conversation.
+
+## 2026-10-26 additions
+
+| date | area | tier | strike | evidence (SHA, check, who caught it) |
+|---|---|---|---|---|
+| 2026-10-26 | client-reliability | standard (feature) | red landing | `c20635bc8539328ca1677f3cf63cbe870adeb9c2`, landq.log 19:15:32.782Z; durable rejected/red gate exit 1 after sustained thermal stop (275/438 starts, incomplete). Area notified through MCP at19:16:19Z (`20261026T191619-dispatch-c43452.md`); candidate retained, no automatic retry. See `test_logs/TEST_LOG_2026-10-26_19-16-00_dispatch-interrupted-gate.md`. |
+
+2026-10-26 hourly audit: client has two confirmed red landings in the last
+seven days (Oct23 and Oct26), both thermal interruptions. Owner-facing proposal:
+consider standard -> strong under a rolling-seven-day interpretation. The
+documented strike week starts at usage reset (`usage.resetCron`: Monday03:00);
+these events straddle that reset, so only one is in the current configured week.
+No automatic tier/config change; stronger models do not establish thermal
+clearance. Preserve the dispatch-owned resource hold and explicit fresh grant.