docs: record failed-check refresh boundary and current Fleet decisions

.torch/backlog/TASK-e440d8c1-479b-418e-bb0f-a693594d891c.json

@@ -17,7 +17,8 @@
     "Foreign recipient claims, arbitrary state-root redirection and unauthenticated metadata fail closed; reading never acknowledges, resolves, transfers ownership or changes stored message/ack records.",
     "Named Runtime, Kernel and QA review exact source/API/test contribution paths, strict boundary scenarios including group messages and limits, and deterministic pagination observations before implementation; preserve all existing assertions and add a Test Integrity Note.",
     "Exact clean candidate checks, independent QA acceptance and guarded serialized integration are required; no fixture-only output, omitted unread filter or acknowledgement counts substitute for real current evidence.",
-    "Before publishing a final blocked/waiting-on-approval/needs-owner report, refresh authoritative unread inbox, current named permission and task evidence; distinguish a timestamped earlier observation from current state and reconcile already-resolved routine waits without asking the owner again. A mechanical observation-watermark/status protocol, if needed, requires an owned reviewed proposal before schema/API implementation."
+    "Before publishing a final blocked/waiting-on-approval/needs-owner report, refresh authoritative unread inbox, current named permission and task evidence; distinguish a timestamped earlier observation from current state and reconcile already-resolved routine waits without asking the owner again. A mechanical observation-watermark/status protocol, if needed, requires an owned reviewed proposal before schema/API implementation.",
+    "Before a failed-check repair/check iteration, refresh the current authoritative brief, actual addressed unread inbox, current task and named consent revisions; apply already-resolved peer direction before further edits or checks. A pending wheel/rAF/scrollend stimulus or an acknowledged historical handoff cannot substitute for current instructions, justify trial timing patches, weakened assertions, duplicate dispatch or a missing-owner-permission claim. Preserve strict behavior, failed receipts and attributable historical evidence; any new mechanical refresh/status protocol needs separately reviewed owned scope."
   ],
   "observedAt": "0fdfcb3b68e4511f2993d03e1fff8f89124b731c",
   "feature": "Identity-bound inbox selection and observation integrity",
@@ -31,14 +32,16 @@
     "ownership:src/mcp/tools.mjs=provider-runtime",
     "message:5039498d-a7f6-4ccd-93b8-cfb86ca2149e:exact-owned-contract-request",
     "message:758830da-8cbb-4b24-a38f-ea472685ecf6:QA-scenario/path/contributor-decision-request",
-    "message:22df881a-9d38-4706-b0bf-da05c6b674c8:Console12:22-stale-QA-wait-after12:19-consent"
+    "message:22df881a-9d38-4706-b0bf-da05c6b674c8:Console12:22-stale-QA-wait-after12:19-consent",
+    "message:c9bd14d0-f006-4b65-9f4e-54c77c58cb42:failed-check-recovery-current-brief-unread-consent-refresh-boundary",
+    "receipt:8ac4a6ab-99b9-4fa5-a941-eac1d03842ba:a7e84cf:fail507-vs327-after-resolved-QA8009-numeric-stimulus"
   ],
   "commit": null,
   "integrationRequest": null,
   "blockedReason": null,
   "createdAt": "2026-10-01T10:32:53.996Z",
-  "updatedAt": "2026-10-01T12:27:23.922Z",
-  "revision": 4,
+  "updatedAt": "2026-10-01T13:16:57.335Z",
+  "revision": 5,
   "history": [
     {
       "from": null,
@@ -67,6 +70,13 @@
       "actorId": "session-manager",
       "at": "2026-10-01T12:27:23.922Z",
       "note": "Owner22df explicitly requests existing-item incident/requirement recording. Reviewed metadata-only amendment preserves current state, owner, candidate, dependencies, prior criteria and every historical wait. No lifecycle transition, new assignment, wrapper/API/schema contract implementation, autoapproval or mass acknowledgement. Fresh final-status observation is required; any mechanical protocol stays an owned reviewed proposal."
+    },
+    {
+      "from": "assigned",
+      "to": "assigned",
+      "actorId": "session-manager",
+      "at": "2026-10-01T13:16:57.335Z",
+      "note": "Owner c9bd14d0 explicitly requests recording this failed-check repair incident in existing stale-brief/unread workflow acceptance. Reviewed Manager-owned metadata-only amendment, expected revision4; append strict safe repair-boundary criterion and exact evidence while preserving state, owner, candidate, dependencies, prior criteria and full history. Native service has no metadata-amend operation. No lifecycle transition, new assignment, source/API/schema implementation, acceptance, guard waiver or provider action."
     }
   ]
 }

reports/audit/pilot-remaining-work-handoff-report-2026-10-01.md

@@ -1,5 +1,95 @@
 # Current pilot remaining-work handoff
 
+## Resumed current coordination and failed-check refresh boundary at 13:17 UTC
+
+Read canonical brief again, exact digest **d7e6d69**. Default readonly-SQLite
+brief failure was resolved through narrowly approved escalation of that exact
+command only. Read CURRENT native tasks, then explicitly addressed unread100;
+read actual owner **c5fdb013**, later owner **c9bd14d0** and Work **2f8dca82**.
+The 13:17 CURRENT task refresh followed by explicit unread100 returns empty;
+this is timestamped observation, not a historical-page completeness inference.
+Requested owner44512241 WAL counterexample, eca7ded3 exact Overview title,
+Kernel b952 implemented API/refusal and QA d29c narrow acceptance were reread
+from this identity's addressed history, separately from unread inspection.
+
+**Current Console evidence and repair.** Fresh clean **a7e84cf5530379f8f3129e2ccd28efd36a3001fe**
+still uses wheel input with scrollend settlement. Manager read the exact test/doc
+delta from b1c633d and native **8ac4a6ab-99b9-4fa5-a941-eac1d03842ba** output:
+FAIL exit1, invalidReason null, measurementsExecuted true; scroll retention
+**507 != 327** at navigation line157, again an exact180px difference. Owner c5
+separately reports the predecessor b1c/07512 same failure. These are distinct
+preserved failed receipts, not an accepted explanation or permission to weaken
+the strict equality. The current test/doc still retain the required behavior.
+
+Actual QA8009 and prior Manager d47b already resolve the stimulus direction:
+fixed numeric nonzero scroll with observed actual position, no pending wheel,
+actual non-scrolling Refresh event, existing generation completion and unchanged
+exact retention assertion. Manager **65f8ef9f** requires Console to refresh its
+brief/current task/unread inbox BEFORE the next repair/check iteration and apply
+that actual resolved direction. QA **d5f21468** receives exact current failure,
+strict correction review and a separate request to justify any accumulated
+product timing changes behaviorally. No blind reversion, repeated trial timing
+patches, retries/sleeps, relaxed bounds, assertion removal or done/landing claim.
+This remains the same Console in_progress13, not missing owner/test permission.
+
+Owner **c9bd14d0** explicitly requests this real incident in existing unread-
+workflow acceptance. Reviewed Manager-owned metadata appends one strict failed-
+check recovery refresh criterion and two evidence references to **e440 assigned5**;
+state/owner/candidate/dependencies, seven prior criteria and full historical waits
+are preserved. Native service has no metadata-amend operation; this is a recorded
+owner-requested ledger amendment, not a lifecycle transition or runtime/API/schema
+implementation. Runtime **ab249ddf** receives the exact incident/boundary. Manager
+checks prove append-only changes, 55 unique tasks, valid revision/history/state,
+known acyclic dependencies and one active task per specialist. Full roadmap and
+the separate integrity evidence task remain, with no duplicate assignments.
+
+**Actual Work design review.** Work **2f8dca82** supplies a concrete proposed
+CandidateQualification/v1 contract based on exact Kernel **f688da69**. It names
+the pure executeConditionedCheck extraction seam rather than CheckService's
+control-plane initialization/DDL/receipt state; proposed CandidateAttemptStore
+in registered CP state and a separate future Kernel provisioner; no-DDL sole
+ReceiptAdapter; sealed-to-finalized BEGIN IMMEDIATE CAS with durable ResultRecord
+and optional PASS receipt atomically; immutable E/S/A/definition/input/guard tuple;
+sorted regular-file artifact seal; explicit per-attempt worker environment and
+opaque authority token; actual child/process fence; exact-identity read-only
+persistence reconciliation. UNKNOWN retains guards without result/receipt/replay;
+proven attributable terminal failure permits only existing-policy scoped cleanup
+after durable evidence and no-live-descendants proof, never PASS eligibility.
+
+Manager routes named Kernel store/provisioner/fence decision **5ab5ffe9**, Release
+command/output/refusal **ab029ea5**, QA exact future scenario/path decision
+**fb7aab84**, and Work integration **41cbd169**. Kernel's contribution remains only
+proposed spec18/20 and ADR026 on Work assigned3. Missing/incompatible registered
+store must refuse; future provisioner/compatibility policy cannot silently perform
+live recovery to bootstrap source qualification. Worker capability withholding
+is not an OS same-user sandbox. Proposed new code paths are not approved code.
+Exact refined doc and actual named decisions remain open before implementation;
+native landing gates, compatible legacy tuples and fixture nonpromotion stand.
+
+**Fleet assessment and boundaries.** Manager check-in13:13 reports no findings or
+named approval waits, with timestamped idle presence rows only; not proof of
+process absence/task completion. Fleet evolution eight recurring domain sets,
+hierarchy nine sets plus11 historical Manager requests, Fleet changes empty.
+Existing coherent owners and exact process/contracts fit these observations;
+another identity/manager would add coordination before current contracts qualify.
+No merge/split/retirement proposal or activation is warranted this cycle.
+Health37 stale-observed and2 resolved-dependency warnings remain observations,
+not automatic cleanup/unblock authority; activity scan is truncated.
+
+Current55 tasks remain38 proposed,8 blocked,6 completed,2 assigned,1 in_progress.
+Runtime e440 assigned5, Work6e4 assigned3 and Console workflow in_progress13 each
+retain continuity. Kernel inbox a4bba is implemented and narrowly QA-reviewed,
+but native3/2 refusal remains genuine; the old 'QA pending' clause is historical.
+Inventory1e688 blocked4 follows supported inbox qualification; dormant Runtime
+2b4 proposed1 follows current wrapper/inventory; Release persistent operations
+then consumes qualified APIs. No API-completion/qualified-receipt/operational
+acceptance is invented to dispatch these phases. Canonical clean0fdf and Kernel
+cleanf688 were read at13:13. No new dispatch, final acceptance, wakes, installation
+switch, live schema recovery, host activation, extra identities or provider launches.
+Five-PNG approval remains only completed exact Runtime recovery; pending75a8
+runtime activation and live schema recovery retain their separate boundaries.
+
+
 ## Fixed-layout diagnostic and existing integrity evidence at 13:10 UTC
 
 Final CURRENT task refresh retains the same55 counts and three active assignments.