TASK-e440: record stale-wait evidence and reconcile same-task scope

.torch/backlog/TASK-console-attention-actions.json

@@ -23,7 +23,8 @@
     "Runtime/tool availability and actionable Fleet health are displayed separately; doctor healthy/status ok does not erase unresolved message, presence, timer or qualification findings.",
     "Presence rows show timestamped source/freshness/unknown evidence; a last idle heartbeat is never presented as verified current process absence.",
     "Unacknowledged message attention is classified by actual recipient, routine peer coordination versus genuine owner decision, and age; aggregate backlog counts do not make the owner responsible for every message, and no suppression or mass acknowledgement occurs.",
-    "Timer/process/presence disagreements link exact observed evidence, the existing task and responsible domain without silently resolving or activating services."
+    "Timer/process/presence disagreements link exact observed evidence, the existing task and responsible domain without silently resolving or activating services.",
+    "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."
   ],
   "observedAt": "0224abf2e08d",
   "feature": null,
@@ -56,14 +57,15 @@
     "message:eb5a356c-3c27-47cb-99d5-3c366179644e:QA-exact-code-hashes-accepted-only",
     "receipt:558d8598-0332-49eb-9296-9f68b5880604:correct-check-id-preserved;prior-revision7-transcription-49aa-is-not-a-receipt",
     "message:799d0275-c113-45cd-a0cb-06ca78f9c71f:land-code-retain-visual-blocker",
-    "message:25e645bf-db6a-4df8-9107-3b82f15e27d8:incident-backed-presence-health-message-classification-criteria"
+    "message:25e645bf-db6a-4df8-9107-3b82f15e27d8:incident-backed-presence-health-message-classification-criteria",
+    "message:22df881a-9d38-4706-b0bf-da05c6b674c8:Console12:22-stale-QA-wait-after12:19-consent"
   ],
   "commit": "cb145e56cb7d530f9563b98d4f9920ff0372a67a",
   "integrationRequest": "9b39e0f8-3ff9-44c5-8b03-9f7d7bdc524b",
   "blockedReason": "Source cb145e56 landed through guarded integration after four exact PASS receipts and independent QA f21b0c38/eb5a356c/all11 artifact hashes. Actual live desktop/mobile browser acceptance remains unavailable and required for full completion; generated artifacts are not visual PASS. Preserve old75afe INCOMPLETE/lost history and current owner/candidate/receipts.",
   "createdAt": "2026-09-30T22:56:50.255Z",
-  "updatedAt": "2026-10-01T12:08:24.703Z",
-  "revision": 9,
+  "updatedAt": "2026-10-01T12:27:23.922Z",
+  "revision": 10,
   "history": [
     {
       "from": null,
@@ -127,6 +129,13 @@
       "actorId": "session-manager",
       "at": "2026-10-01T12:08:24.703Z",
       "note": "Reviewed owned-ledger metadata-only amendment explicitly requested by owner25e645bf. Append strict incident-backed presence freshness, separate availability/health and recipient/age/actionability criteria as applicable. Preserve existing criteria, state, owner, candidate, integration request, dependencies and all history. Native service has no metadata-amend operation; no lifecycle transition, duplicate task, assignment, qualification, warning suppression, mass acknowledgement or host/provider authority inferred."
+    },
+    {
+      "from": "blocked",
+      "to": "blocked",
+      "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."
     }
   ]
 }

.torch/backlog/TASK-conversation-console-workflow.json

@@ -46,14 +46,23 @@
     "qa-title-mapping:d3e5a001-69dd-464d-ae54-c766c93fb153",
     "owner-decision:a8a0c5db-6c4f-4fbe-890a-987a1542b06f",
     "owner-diagnostics:eeb93c8f-22ac-45ad-a84e-9002344cf579",
-    "owner-deeplink-diagnostic:f5016dea-788c-47e8-83bf-81ffa91e7784"
+    "owner-deeplink-diagnostic:f5016dea-788c-47e8-83bf-81ffa91e7784",
+    "blocker:379ae2c1-5aa5-49a3-b925-ec6888c5a534",
+    "source-cli:test-dashboard:d983c1ca-dfed-4fd2-92da-2d76779b18f8:FAIL:candidate=6988fe3b1a1fe8e411e4e4968877ae6f22ea4200:artifact=/home/user/.local/share/torch/projects/3dc11932-6e3c-42aa-9a8a-ca7b8f818b54/checks/d983c1ca-dfed-4fd2-92da-2d76779b18f8/output.json",
+    "source-cli:test:e6b4bf22-de61-401d-804d-7bb98cfc3c97:PASS:candidate=6988fe3b1a1fe8e411e4e4968877ae6f22ea4200",
+    "source-cli:check:41e9b023-1862-463e-b87b-d0f234b28653:PASS:candidate=6988fe3b1a1fe8e411e4e4968877ae6f22ea4200",
+    "older-receipt:failed-test-dashboard-02a76db2-d8aa-40e9-ac93-03139ceca568:preserved",
+    "message:1b19a436-44d8-4e6c-8868-19f1e65591db:QA-exact-Fleet-markup-and-scenario-contribution-consent",
+    "message:1b2d96bc-ec77-4cb2-b5be-a1b9b6ef47ae:owner-explicit-same-task-scope",
+    "message:6a37283a-5baf-4b3f-b84c-1aa7cdecf223:actual-bounded-peer-request",
+    "message:22df881a-9d38-4706-b0bf-da05c6b674c8:stale-wait-evidence-refresh-required"
   ],
-  "commit": "a67a04d57f400782b01ba6087b9741fb0c54e21f",
+  "commit": "6870c3a61073b950710eb7720f63ccd21da58f38",
   "integrationRequest": null,
   "blockedReason": null,
   "createdAt": "2026-09-30T19:30:23.720Z",
-  "updatedAt": "2026-10-01T11:24:07.534Z",
-  "revision": 10,
+  "updatedAt": "2026-10-01T12:27:44.625Z",
+  "revision": 13,
   "history": [
     {
       "from": null,
@@ -124,6 +133,27 @@
       "actorId": "owner-console",
       "at": "2026-10-01T11:24:07.534Z",
       "note": "Resuming the same task at Manager-assigned revision 9. Implementing only QA-approved site/console.js behavior, additive console-view-navigation scenarios, script navigation/strict preview coverage preserving every existing assertion/capture/artifact safeguard, and additive Test Integrity Note. Keep prior receipts and visual-acceptance boundary."
+    },
+    {
+      "from": "in_progress",
+      "to": "blocked",
+      "actorId": "owner-console",
+      "at": "2026-10-01T12:22:42.223Z",
+      "note": null
+    },
+    {
+      "from": "blocked",
+      "to": "assigned",
+      "actorId": "session-manager",
+      "at": "2026-10-01T12:26:21.618Z",
+      "note": "Resume SAME Console workflow after fresh brief d7, CURRENT blocked11 and own unread100 prove exact scope/QA wait already resolved. Current native next idle/no active item; actual source clean6870 restored strict driver, old8ba fallback remains unaccepted. Owner1b2 + QA1b19 explicit site/console.html Operations Fleet secondary ownership, console.js ancestor-details/deep-link routing, additive console-view-navigation test, narrow strict dashboard driver and additive integrity note. Retain ten destinations; all operational panels hidden elsewhere; direct/history manager-wakes selects Fleet, opens details, focuses/scrolls target. No fallback/show-all, backend/shared helper/fixtures/goldens changes or original assertion/capture weakening. Read actual addressed QA b444 before test contribution. No new task or second Console assignment. Fresh exact final four native source gates and independent QA required; actual live desktop/mobile acceptance separate. Preserve6870/8ba/6988/d983 and all histories; refresh unread/permissions/task evidence before reporting approval waits. No provider/wake/install/schema/host action."
+    },
+    {
+      "from": "assigned",
+      "to": "in_progress",
+      "actorId": "owner-console",
+      "at": "2026-10-01T12:27:44.625Z",
+      "note": "Resuming the same workflow on clean HEAD 6870c3a under Manager reassignment revision 12. Actual QA b4449652 and owner 46cd85d9 authorize the exact second-Fleet-section layout/routing scenario and narrow driver scope; preserve strict ownership assertions and all existing coverage."
     }
   ]
 }

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

@@ -16,7 +16,8 @@
     "Explicit history and limited/truncated unread results expose sufficient reviewed selection, completeness/truncation and pending-unread metadata to distinguish a page from a complete unread check; metadata is produced through the existing bound read API with a consistent observation contract.",
     "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."
+    "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."
   ],
   "observedAt": "0fdfcb3b68e4511f2993d03e1fff8f89124b731c",
   "feature": "Identity-bound inbox selection and observation integrity",
@@ -29,14 +30,15 @@
     "message:67926f0f-79db-487e-8066-0b09fbd4ba0e:actual12-unread-incident",
     "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: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"
   ],
   "commit": null,
   "integrationRequest": null,
   "blockedReason": null,
   "createdAt": "2026-10-01T10:32:53.996Z",
-  "updatedAt": "2026-10-01T10:38:12.349Z",
-  "revision": 3,
+  "updatedAt": "2026-10-01T12:27:23.922Z",
+  "revision": 4,
   "history": [
     {
       "from": null,
@@ -58,6 +60,13 @@
       "actorId": "session-manager",
       "at": "2026-10-01T10:38:12.349Z",
       "note": "Owner08 actual priority; fresh native next ready THIS item/no active Runtime item, clean Runtime exact0fdf verified. Assign bounded MCP inbox phase to Runtime on existing branch, preserving blocked starting-presence4/Kernel reservation5 and all their receipts/guards. First pin exact src/mcp/tools.mjs interface/spec and get real named QA scenario/path contributor consent; implement owned unread-default/explicit-history behavior only after that decision. Kernel-bound metadata API changes require exact peer contribution consent or separately assigned Kernel implementation, not guessed exports/direct DB/state roots. Return exact contract, QA decision and proposed dormant launcher component interface/implementer for later separately sequenced Release dependency. Full unread/count/truncation criteria stay open; no second Runtime active item, no tests before permission, no caller identity bypass/auto-ack/wake/host/schema/installation changes. Fresh exact four gates and independent QA/guarded integration required. Arbiter starts the actual provider turn; Manager launches none."
+    },
+    {
+      "from": "assigned",
+      "to": "assigned",
+      "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."
     }
   ]
 }

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

@@ -1,5 +1,115 @@
 # Current pilot remaining-work handoff
 
+## Current proposed amendment, resolved scope and protocol review at 12:30 UTC
+
+Actual Kernel **ce742a86** delivered clean **674d2418572026692e08307c5e9c71ae89c219d8**:
+Manager independently read the full exact two-path diff. Spec sections18/20 have
+only additive clearly PROPOSED nonnormative subsections; ADR026 is additive;
+current normative paragraphs and ADR024/025 are intact. This is a reviewable
+proposed design, not implemented source, native qualification or governing policy.
+Work design lead **170200de** received exact draft for concrete review. Actual QA
+1b19 design scenario review exists; future test-path/source/policy consent is
+separate. No document-only local check is substituted for native landing gates.
+
+Owner **7bc7227c** full-draft review identifies an actual precision gap: candidate
+PRODUCT storage version is independent of a pure source-check ENGINE/registered
+ADAPTER's required schema. Future product-schema3 source could be hermetically
+checked by a genuinely schema-agnostic pure engine and authenticated schema2-
+compatible adapter only under an explicitly reviewed tuple supporting that case.
+Current Kernel CLI/engine actually opens ControlPlane and requires3, so its real
+registered2-versus-required3 refusal remains unchanged. The proposed draft must
+not permanently preserve bootstrap circularity by conflating these requirements.
+
+Owner **d6b94081** settles initial CLI design: derive exact subject from the
+authenticated registered area/managed clean worktree; no caller commit/root/manifest/
+state-root/DB/schema/context/adapter selection flags or initial expected-commit.
+Release retains command names/presentation; any future expected-commit is a later
+reviewed rejection-only freshness assertion. This resolves the design choice, not
+code, current gate policy, adapter readiness, installation or live recovery.
+
+Manager routes a concrete integrated protocol review to Work/Kernel/Release/QA:
+create authenticated durable guarded attempt; execute; prove terminal outcome;
+seal bounded regular-file artifact manifest; atomically persist receipt AND
+consume attempt through a compatible trusted adapter transaction. Cancellation
+request alone is not proof the child stopped. Unknown/crashed/ambiguous attempts
+stay guarded, never successful/idle or automatically replayed. Seal/hash before
+transaction; persistence failure retains sealed evidence plus unconsumed guarded
+attempt. Commit uncertainty needs exact attempt/result/receipt read-only
+reconciliation, never duplicate emission. No consume-then-silent-loss design.
+This is a concrete proposal for peer review, not selected implemented enforcement.
+Remaining decisions are exact durable atomic store contract without DDL, worker
+confinement/environment exceptions, artifact sealing primitive, cancellation/
+process fence and replay/reconciliation rules. Kernel must revise only proposed
+paragraphs/ADR026 forward and return exact draft; Work must review exact interface
+and policy gaps before code. Current normative/ADR024 and receipt guards stand.
+
+Console **ac2684/581df/6a372** stale scope wait was reconciled after CURRENT
+blocked11, fresh brief, native next idle and unread100: actual owner1b2 and
+QA1b19/b444 scope already grant the same exact Fleet layout. Native transition
+blocked11→assigned12 at restored strict **6870c3a** retains all failures/history.
+Console then independently resumes **in_progress13**. Manager **b4365e44** confirms
+same task, five exact source/test/doc paths, no fallback/fixture/backend changes,
+and fresh final native source/independent QA/live visual gates. No new assignment
+or owner approval relay; old8ba fallback remains unaccepted.
+
+Owner **22df881a** concrete stale-wait incident is recorded in existing **inbox
+assigned4** and **attention blocked10** metadata/criteria/evidence, preserving
+states/owners/candidates and all prior histories. Final blocked/waiting/needs-owner
+reports require fresh authoritative unread inbox, named permissions and current
+task evidence; historical observations remain timestamped. A new mechanical
+watermark/status schema/API protocol requires an owned reviewed proposal, not
+unilateral implementation. Runtime **16be8f0b** receives exact revision update;
+Console/QA receive resolved permission and strict freshness requirement.
+
+Fresh native readback: Runtime inbox assigned4, Console workflow in_progress13,
+Work design assigned3, attention blocked10. Kernel inbox565 still blocked7 at a4:
+focused proof accepted, native3/2 qualification refusal retained. Ledger55 and one
+active item per specialist remain; full inventory/dormant/services/visual roadmap
+preserved. No final acceptance, automatic wakes, install/schema recovery, host
+activation, extra identities or provider launches.
+
+
+## Current strict route correction and CLI design decision at 12:24 UTC
+
+Owner **38089ba3** independent isolated exact6988 observation confirms Operations
+has no owning view while warning correction and Organization two-section visibility
+remain focused PASS. Owner **2a31aafd** identifies **8ba1af6** as the rejected driver
+fallback. Manager independently reads the exact8ba1 patch: it replaces the
+#manager-wakes selectViewFor owning-view boundary with selectView overview.
+Withhold acceptance/landing regardless of any green receipt. Correct forward,
+retain candidate/history/failures and restore owning-view truth; Manager edits
+no peer source or tests.
+
+Actual QA **1b19a436** now explicitly consents the narrow site/console.html layout
+plus existing console.js/navigation test/narrow driver/Test Integrity Note scope.
+Fleet owns a second appropriately identified Operations section, ten nav destinations
+remain, other views hide it, direct #manager-wakes selects Fleet/opens ancestor
+details/focuses and scrolls target. Manager **51468c2a/adbb5b06** routes exact
+consent and rejects fallback on the SAME workflow10. Original warning/draft/stale/
+mobile/deep-link/capture/artifact assertions remain mandatory; fresh final four
+native source gates and independent QA/live visual qualification are distinct.
+The Console branch is progressing; exact current HEAD must refresh before review.
+
+Owner **5e7cfbb8** confirms Kernel actual design-doc contributor turn began under
+25dca/28f authority, not a Manager provider launch. It also identifies a real
+CLI-interface disagreement: Release Work-addressed8da824 proposes caller --commit,
+Kernel rejects caller commit/root/schema/context authority. Manager **6964e85c**
+asks Release to agree initial internally derived registered clean subject/no commit
+override; any future expected-commit may only reject stale derived HEAD, never
+select arbitrary subject or grant receipt authority. Kernel **cb0b980e** and Work
+**67e0c13a** retain this pending decision honestly in proposed text. Three-axis
+agreement is not complete CLI-interface consensus, and no code authority follows.
+
+QA **1b19a436** supplies design-only tuple scenario plan: exact engine, authenticated
+adapter, subject identity, current schema, definition/input, opaque attempt/artifacts,
+guards and terminal evidence; nonconvertible source/operational receipts, fresh
+operational acceptance after landing, compatible legacy schema2 and genuine3/2
+refusal. Future QA test paths were sent to Work, not inferred as current edit consent.
+All four new messages were individually read and acknowledged; reviews remain open.
+Manager local checkpoint **b21cc60** holds the prior five reviewed coordination
+paths. No native landing, gate change, activation or recovery is claimed.
+
+
 ## Current design-document phase and Console route failure at 12:20 UTC
 
 Explicit own unread100 was reread after current tasks; owner **12360913/defac915**,