TASK-6e4ff870: record source qualification proposal and named consent waits

.torch/backlog/TASK-6e4ff870-a386-4a11-a59c-444ebc23732e.json

@@ -0,0 +1,46 @@
+{
+  "schema": "torch.dev/backlog-item/v1alpha1",
+  "id": "TASK-6e4ff870-a386-4a11-a59c-444ebc23732e",
+  "title": "Separate candidate source qualification from live control-plane initialization",
+  "description": "Explicit owner a970326b-87a5-4292-8f22-e1bec0c15f11/92f7fd36 corrects the inventory: no explicit existing check-engine separation item exists. Add ONE proposed bounded item in the existing backlog. Incident observed on canonical cb145e56 and Kernel reservation candidate be1ae951: candidate CLI initialized production schema3 during qualification, installed/canonical schema2 writers relabel it, and native CONTROL_PLANE_SCHEMA_DOWNGRADE_DETECTED currentVersion2 requiredVersion3 then prevents qualification, causing activation/landing circularity. Design supported separation of exact candidate-source execution engine from a versioned, independently fingerprinted compatible receipt/control-plane adapter without migrating live production state merely to test candidate. Preserve actual authenticated native project/area/commit/definition/run/resource/guard/outcome evidence and immutable artifacts. Work owns src/checks, Kernel src/control-plane, Release CLI wiring and QA scenarios/acceptance; agree exact contract, owned paths and scenario consent before any implementation. No old-checker shortcut, fake isolated real-project receipts, gate waiver, install activation, production DB recovery, new identity or parallel queue. TASK-4dc metadata/candidate preparation remains completed; its retained deeper provenance roadmap was not an explicit task until this proposal.",
+  "priority": "high",
+  "affectedDomains": [
+    "work-integration",
+    "project-kernel",
+    "release-self-host",
+    "qa"
+  ],
+  "dependencies": [
+    "TASK-3909cbf6-10c6-44ce-b82e-5bfb62cf34c8"
+  ],
+  "acceptanceCriteria": [
+    "Work, Kernel, Release and QA review a precise versioned executor/receipt-adapter interface, primary-owned path map and named contribution/scenario consent before implementation or source qualification claims.",
+    "Candidate-source checks use an exact clean candidate execution engine without initializing or migrating production control-plane schema; boundary scenarios compare live schema/data/provenance before and after and preserve existing identities, tasks, messages, held reservations and resource guards.",
+    "Receipts independently bind actual execution-engine commit/content digest and actual loaded adapter identity/digest/interface/schema version under an explicitly reviewed compatibility contract, plus authenticated native project, area, candidate, definition, run and terminal outcome.",
+    "Unknown engine, incompatible adapter, forged compatibility evidence, digest mismatch, stale candidate or changed definition/input/artifact evidence fails closed; an installed older checker is never presumed candidate-equivalent.",
+    "Frozen inputs, resource/worktree protections, unknown/error/timeout outcomes and immutable external artifact names/bytes/hashes retain strict exact-commit gate integrity; zero exit or isolated fixture output alone cannot become a real-project PASS receipt.",
+    "Strict isolated migration/compatibility/self-host scenarios remain visibly distinct from full operational qualification and cannot be promoted or copied as native real-project receipts; no production-state recovery or activation follows from fixture success.",
+    "Preserve all prior schema guard refusals, old unqualified receipts, archives, assertions and Test Integrity Notes; eventual independent QA acceptance and fresh exact native checks plus serialized guarded integration are required without gate waivers."
+  ],
+  "observedAt": "cb145e56cb7d530f9563b98d4f9920ff0372a67a",
+  "feature": "Check execution provenance and state isolation",
+  "milestone": "Reviewed reliability dependencies",
+  "state": "proposed",
+  "owner": null,
+  "evidence": [],
+  "commit": null,
+  "integrationRequest": null,
+  "blockedReason": null,
+  "createdAt": "2026-10-01T10:14:01.401Z",
+  "updatedAt": "2026-10-01T10:14:01.401Z",
+  "revision": 1,
+  "history": [
+    {
+      "from": null,
+      "to": "proposed",
+      "actorId": "session-manager",
+      "at": "2026-10-01T10:14:01.401Z",
+      "note": "Task created."
+    }
+  ]
+}

.torch/backlog/TASK-conversation-persistent-operations.json

@@ -20,7 +20,7 @@
   "observedAt": "ff0712534829",
   "feature": "Self-host development readiness",
   "milestone": "Owner-reviewed first development backlog",
-  "state": "in_progress",
+  "state": "blocked",
   "owner": "release-self-host",
   "evidence": [
     "message:94010b22-c6ce-4d34-9ed9-01b2330106db:sequence-real-next-Release-persistent-setup-owned-work",
@@ -31,14 +31,18 @@
     "message:703bb01b-6f7a-43f4-92c4-b86ca01b6153:Kernel-boundary-review",
     "message:87c3b0a7-bd6f-46dd-a4cc-b72e27ee55c5:isolated-qualification/future-Release-fence",
     "message:a10ce5dc-5f65-4ec6-8808-3a8ccbf6ec97:Runtime-design-review",
-    "message:c63ec499-fc6f-4246-9190-05d457d11de9:QA-strict-design-boundaries"
+    "message:c63ec499-fc6f-4246-9190-05d457d11de9:QA-strict-design-boundaries",
+    "message:e4dc7e71-1cc9-4326-a7e7-a7547a793043:actual-owned-source-peer-API/test-boundary-hold",
+    "message:efff7c90-4f2b-413b-a488-7e9c678ed0ae:explicit-named-test-implementer-disposition-required",
+    "message:cb0e71d4-28f5-49f7-ab79-42b8d23a98a1:named-QA-exact-contributor-decision-or-implementer-request",
+    "message:04554a2e-6e39-4399-a609-4337d37169a3:retain-real-peer-consent-holds"
   ],
   "commit": null,
   "integrationRequest": null,
-  "blockedReason": null,
+  "blockedReason": "Actual Release e4dc7e71 implementation hold: Kernel manifest/API and Runtime dormant launcher contracts remain pending; QA a4f58d03 scenario consent explicitly forbids contributor test/** edits. Await QA cb0e71d4 exact contribution permission or named QA test implementer/support contract, plus actual Kernel76cf/Runtime9cf decisions. No owner implementation-detail permission needed, no shared-path edits authorized by a scenario-only consent.",
   "createdAt": "2026-09-30T19:34:25.620Z",
-  "updatedAt": "2026-10-01T09:56:38.861Z",
-  "revision": 4,
+  "updatedAt": "2026-10-01T10:15:14.694Z",
+  "revision": 5,
   "history": [
     {
       "from": null,
@@ -67,6 +71,13 @@
       "actorId": "session-manager",
       "at": "2026-10-01T09:56:38.861Z",
       "note": "Current canonical brief reread and exact Release next resume SAME task. Owner99ee5 directs precise implementation contract/path map and actual named QA additive scenario consent, then reviewed Release-owned portable source work: combined digest-bound init/install preview and dormant schedule provisioning/reconciliation. Kernel config/manifest APIs and Runtime launcher/lifecycle remain peer-owned; exact consent required before edits there. Source paths begin Release src/cli.mjs/src/self-host/service.mjs/bin as individually named in returned plan; no package/global/provider/config/host changes inferred. Qualify strict isolated fixture state, distinguish from unavailable real-project schema3 gates; don't wait on live recovery to design/develop pure portable code once consent is sufficient. Return concrete enforceable future writer-fence proposal, not process absence/token alone. No host unit enable/linger/destination choice, service stop, production state relocation/live mutation, engine installation/activation or provider wake. Keep full criteria and independent final exact checks/QA/guarded integration requirements."
+    },
+    {
+      "from": "in_progress",
+      "to": "blocked",
+      "actorId": "session-manager",
+      "at": "2026-10-01T10:15:14.694Z",
+      "note": "Reconcile actual implementation blocker on SAME Release task, no parallel queue or false human hold. Previous portable source phase remains approved within owned exact paths after sufficient real peer API/test contribution decisions; a4 scenarios alone never override explicit test-edit prohibition. Resume same task after genuine peer gates clear; fullcriteria/owner/history preserved. No live host/state/activation/wake action."
     }
   ]
 }

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

@@ -1,5 +1,60 @@
 # Current pilot remaining-work handoff
 
+## Current intake and genuine peer waits at 10:15 UTC
+
+Owner `a970326b` corrects the task inventory: the deeper check-engine roadmap
+had no explicit separation task. Manager reread the current canonical brief and
+created exactly one **proposed, high-priority** item in the existing backlog:
+`TASK-6e4ff870-a386-4a11-a59c-444ebc23732e`, "Separate candidate source
+qualification from live control-plane initialization." Its observed commit is
+`cb145e56`, description retains candidate `be1ae951` and native schema-downgrade
+refusal, and prerequisite task3909 is actually completed. Seven strict criteria
+cover separate engine/adapter identities and compatibility, no production
+schema initialization merely for source checks, authenticated real-project
+receipts, exact frozen inputs/guards/artifact provenance, incompatible/unknown/
+forged/stale negatives and distinct isolated versus full qualification.
+This supersedes the earlier assumption that retained roadmap prose implied an
+explicit queue item. No assignment or implementation occurred. Work and Kernel
+review requests `53fbc8d8`/`dbbb9b13` bind the actual new task; Release and QA
+remain required interface/CLI/scenario reviewers.
+
+Release persistent-operations is **blocked revision 5** on its actual peer
+boundaries, not an owner implementation-detail hold. Release `e4dc7e71` confirms
+Kernel manifest/API and Runtime dormant launcher contracts remain pending.
+Owner `efff7c90` clarifies that QA `a4f58d03` approved scenarios but explicitly
+forbade Release editing QA-owned tests. Manager request `cb0e71d4` asks named QA
+for an explicit decision: bounded contributor edits of only the new
+`test/fleet/persistent-operations.test.mjs` under all strict constraints and
+independent QA acceptance, or QA as the actual test implementer with a precise
+support contract for later scoped assignment. `04554a2e` retains the prohibition
+until that decision. QA is idle after actual task3909 completion; no second
+simultaneous QA item was created and no forbidden test edit is approved.
+The approved portable Release source phase can resume on the SAME task once
+actual contracts and contribution/implementer permission are sufficient.
+
+Owner `92f7fd36` reports an actual non-force rewrite push of exact `0fdfcb3`,
+verified remote `0fdfcb3` and unchanged default-main `a468`. These are explicitly
+arbiter-reported remote results; Manager performed only the previously recorded
+native guarded local landing. No installation or live Console activation follows.
+
+Manager checkpoint `51d9ddb` converged through TORCH's blocker-free guarded merge
+to **`bd6d39022ad8fa568f0fd80befa863f9659c6c6a`**, preserving all51 unique commits.
+Both accepted canonical `0fdfcb3` and the preceding reviewed checkpoint are
+ancestors; resulting worktree and full canonical-relative diff checks are clean.
+Manager has no configured feature checks; ledger integrity is validated without
+claiming this coordination merge is a separately qualified feature candidate.
+The supported Manager-publication restriction remains, so checkpoints are local.
+
+After intake, Fleet evolution was refreshed again: seven recurring domain sets
+remain advisory. Exact Work/Kernel/Release/QA interfaces address the new gap within
+existing owners; retain six specialists and no hierarchy/domain activation.
+All51 tasks remain:38 proposed, six blocked, six completed, one in progress
+(Console). Health now has37 stale-observation findings after canonical advanced
+and two resolved-dependency findings with real ownership/schema waits retained;
+no automatic fix, ACK flood or hidden risk. Automatic wakes and alpha.3 activation
+remain held as described below. End this coordination cycle on the actual named
+peer waits; no provider launch, poll loop or authority bypass.
+
 ## Guarded artifact delivery and current Fleet at 10:09 UTC
 
 Startup brief still matches `d7e6d69`; exact narrowly approved retry resolved