docs: distinguish current contributions and actual Fleet review outcomes

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

@@ -18,7 +18,8 @@
     "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 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."
+    "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.",
+    "Before classifying a same-task contribution as duplicate, completed or waiting, refresh the actual addressed unread inbox and compare the exact named current handoff, candidate and requested scope with superseded/completed contributions, even when the task revision is unchanged. Startup/resume UX must distinguish a stale orchestration hint from a pending current contribution and show its provenance; a reused followup flag or terminal old contribution cannot close a new handoff. Any mechanical handoff/version/status schema or activation change remains a separately reviewed owned proposal."
   ],
   "observedAt": "0fdfcb3b68e4511f2993d03e1fff8f89124b731c",
   "feature": "Identity-bound inbox selection and observation integrity",
@@ -34,14 +35,15 @@
     "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: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"
+    "receipt:8ac4a6ab-99b9-4fa5-a941-eac1d03842ba:a7e84cf:fail507-vs327-after-resolved-QA8009-numeric-stimulus",
+    "message:7a6eb8ca-bc61-4b1e-860b-d4f87f521855:reused-arbiter-followup-flag-obscured-new-Work2f8-Manager5ab-attempt-store-contribution"
   ],
   "commit": null,
   "integrationRequest": null,
   "blockedReason": null,
   "createdAt": "2026-10-01T10:32:53.996Z",
-  "updatedAt": "2026-10-01T13:16:57.335Z",
-  "revision": 5,
+  "updatedAt": "2026-10-01T13:28:26.706Z",
+  "revision": 6,
   "history": [
     {
       "from": null,
@@ -77,6 +79,13 @@
       "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."
+    },
+    {
+      "from": "assigned",
+      "to": "assigned",
+      "actorId": "session-manager",
+      "at": "2026-10-01T13:28:26.706Z",
+      "note": "Owner 7a6eb8ca explicitly requests existing stale-brief/task-startup UX recording of exact named current handoff versus superseded/completed/pending contribution, including shared arbiter orchestration incident. Reviewed metadata-only amendment, expected revision5. Preserve owner/state/candidate/dependencies, eight prior criteria and full history. Native service has no metadata-amend operation; no lifecycle transition, new task/assignment, API/status/schema implementation, provider launch or acceptance."
     }
   ]
 }

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

@@ -1,5 +1,103 @@
 # Current pilot remaining-work handoff
 
+## Current diagnostic receipts and concrete design reviews at 13:31 UTC
+
+Canonical brief reread, digest **d7e6d69**; readonly default brief was retried only
+through approved exact-command escalation. CURRENT task read preceded explicit
+addressed unread100. Actual owner **7a6eb8ca**, Kernel **42e3108b**, owner
+**512dde54**, QA **9d94cd87**, Release **46a8bde7** and owner **c565e2c5** were
+understood, routed and individually acknowledged. Owner44512241 WAL mutant,
+eca7ded3 exact Overview title, Kernel b952 implementation/refusal and QA d29c
+narrow proof were separately reread in this identity's history, not used to infer
+unread completeness. Manager begins cleancaa9f2b; no memory hit was used.
+
+**Actual native receipts versus deterministic/operational acceptance.** Console
+**7ea65992db2424be1e8242d44b1dbb2b9c6012c2** has real exact test **27108947** and
+check **4d7ba790 PASS**, plus dashboard **8a47081d FAIL**. Manager read the exact
+062-to7ea delta: added global scrollTo wrapper/event tracing and extra async
+page.evaluate roundtrips in assertion-message construction; exact equality stays,
+but test still uses wheel+scrollend rather than QA8009's fixed numeric stimulus.
+Instrumentation can alter the known race timing; receipt PASS is preserved as
+an actual result, not fabricated/refused or independently accepted deterministic
+qualification. QA **1d9e7825** receives precise instrumentation/consent/necessity
+disposition and separate source-timing review; Console **f4291001** receives
+resolved numeric direction and fresh unread-before-repair boundary.
+
+Manager independently reads7ea dashboard output: measurementsExecuted true,
+locator timeout locating approval-decision-form in selectViewFor at driver301.
+Console advances to independently clean **cfb69b490037bca119eca53d6f07bf29130065ac**;
+exact driver delta selects the actual owning Flow Watch view before the unchanged
+capture instead of deriving it from a missing approval form. Native **0baefdd8
+test PASS**, **18de60d9 check PASS**, **078ff5da dashboard FAIL** remain exact results;
+no lint/four-PASS qualification or final acceptance is established. Owner c565
+attributes the newer failure to Review change at driver364 and identifies a
+specific hypothesis: unconditional summary click closes already-open protected
+priority details. Manager reads that actual source; browser-state proof remains
+required. QA **b93e36dd** receives the precise narrow contributor decision request:
+inspect disclosure.open, real summary click only if closed, retain every original
+Review/preview/token/revision assertion, no forced DOM opening/show-all fallback,
+skips/retries/sleeps/looser bounds or capture changes. Console **bbf0a82a** receives
+that pending request separately from already-approved numeric test stimulus.
+
+**New contribution within an unchanged task.** Owner7a reports a shared arbiter
+orchestration bug: reused followup flag highlighted the old completedf688 request,
+so a new Work2f8/Manager5ab attempt-store contribution was called duplicate.
+Arbiter corrected exact current handoff and resumed only the existing identity
+after terminal; Manager did not launch it. Kernel now returns NEW clean
+**6fdb88ea200f1680c9051144f59a87acc904e41e**. Manager reads its full exact two-doc
+delta: proposed AttemptStore/AttemptRecord/ResultRecord, owner-authorized future
+provisioner versus no-DDL adapter, missing-store refusal, artifact manifest/seal,
+exact tuple/guard/lease/process fence CAS, UNKNOWN retention versus proven failed
+cleanup, absolute fixture nonpromotion and legitimate reviewed prelanding source
+subject without circular operational prerequisite. Normative text/ADR024/025,
+source/schema/gates stay unchanged. Work **b3ddff09**, QA **bbd87258** and Release
+**e7f50a6a** receive this NEW exact contribution, not an old completion summary.
+
+Owner explicitly requests recording current named handoff versus superseded/
+completed/pending contribution in existing stale-brief/startup UX. Reviewed owned
+metadata appends one criterion/evidence/history entry to **e440 assigned6**;
+all eight prior criteria, state/owner/candidate/dependencies and histories remain.
+Runtime **0e9ce34e** receives the actual shared incident. Mechanical status/API/
+schema implementation remains separately reviewed scope. Validation proves
+append-only amendment,55 unique tasks, valid revisions/state/history, known
+acyclic dependencies and one active assignment per specialist. No duplicate task.
+
+**Actual named design reviews now exist.** QA9d94 supplies concrete no-DDL store,
+E/S/A, atomic result/eligible receipt, crash ambiguity, replay/artifact/drift,
+UNKNOWN/survivor, proven cleanup/nonpromotion and separate consumer scenarios.
+Release46a8 proposes candidate-plan/run dispatched before live initialization,
+derived authenticated subject, separate terminal/cleanup/receipt/operational JSON,
+stable refusals, trusted-parent-only result transport and exact guard/lease IDs
+plus fence generations. Release explicitly bounds its evidence to clean oldcb145
+source, not convergence/qualification. Generic missing QA/Release review is stale;
+exact final API, contributor paths, policy/compatibility/provisioner/fence/sealing/
+environment and isolation approvals remain open before code. Manager routes
+actual reviews to Work **7b0e583c**, Kernel **56b390c9**, Release **4ed11bb9** and
+QA **8eb68dc1**. Worker opaque transport cannot grant result-writer/finalizer
+authority; area/check may verify only authenticated allowed binding, never select
+foreign subject/authority. Cleanup adds no new lease-release authority. Candidate
+source, native receipt and operational acceptance stay separate; fixture results
+remain permanently nonpromotable and current native landing gates stand.
+
+**Fleet judgment and roadmap.** Check-in13:25 has the actual Kernel unread finding
+handled above and no named approval waits; idle presence timestamps prove neither
+process absence nor finished assignment. Evolution eight recurring domain sets,
+hierarchy nine sets+11 historical Manager requests, changes empty. Exact process,
+handoff and specialist contracts remain preferable to another identity/manager;
+no merge/split/retirement/activation proposal. Health37 stale-observed+2 resolved-
+dependency warnings remain observational, scan truncated, no automatic repair.
+CURRENT55 tasks retain38 proposed,8 blocked,6 completed,2 assigned,1 in_progress:
+Runtime e440 assigned6, Work6e4 assigned3 and Console in_progress13. Kernel inbox
+a4bba exists with narrow independent proof acceptance but genuine native3/2 refusal;
+old missing API/test-consent/QA-pending summaries cannot replace current evidence.
+Inventory1e688 blocked4, dormant Runtime2b4 proposed1 and Release persistent
+operations remain separately sequenced contract/qualified-API phases. Full roadmap
+and blocked histories survive. Canonical clean0fdf and Kernel clean6fdb were read.
+No final acceptance, dispatch, automatic wakes, installation switch, live schema
+recovery, host activation, extra identities or provider launches. Exact five-PNG
+consent remains completed Runtime recovery only, not pending75a8 activation.
+
+
 ## Last exact-source observation at 13:20 UTC
 
 After checkpoint914ce5a, CURRENT native tasks still Console in_progress13, Work