Complete strict SDK capacity-provider and agent acceptance bindings #387

Public Deployment inspection delivery checked — 2026-10-09

Deployment #866 ordinary merged staging a0ccbbf6f6644ef754336a7dd162616e99157b78; tree 6996d6294dd0b60fdb782c5a3350764a5ead5a90 matches tested merge 4f3bac209776d2dbb2c7d9e72de0b236cf068a95 and head 7e8f352c50c8b3df4ea633fe1f62cb17b62837be. Actions 38001126654: Node24.12.0, npm run verify:direct 1303/1303 assertions in195files, then fresh1303 before225 passed component steps; zero failed/skipped/todo. Source digest 9840fd38eac0fbff4d5b32c846989740ddf6b3edd20c01d73ab36c5dca1db1eb; report SHA256 92eee1f9e131aaa3472a5df292f60bb96bdaf84a5241f9e111129dfb7d4afdee. Scene artifact11649168797 ZIP 6a051254175626239f8094c8f1cfe39f85199dff4752d047ca89be24190fff53; candidate11649057960 ZIP 3ac011cf1a6d8004d18e9c61fc68f0d0aceb82f662c64798f75c73b0cdd178b6. All11 applicable checks passed: backup38001126759, Identity38001126650, native PostgreSQL transfer38001126645, faults38001126715. The real installed CLI→manager→supervisor case proves scoped present/absent native resources, exact host mount/directory observations and retained unrelated resources, without resource-starting inspection or privilege expansion. Normal SDK consumer remains unproven.

Historical failures37997943987 and38000247266, and moving-runtime pass37998634895, remain retained. Focused regressions preceded enumeration/identifier and runtime-custody repairs. 03787b45→942f3f85 pinnedNode; d955bd3a→7e8f352c preserves privileged descendant PATH and actual child Node read-back with safe failure-stage evidence. No watchdog changed, no failure reclassified as a pass, no managed SDK attempt or binding-count change.

Agent installed-asset delivery checked — 2026-10-09

Agent PR #387 ordinary merged to staging 6b3673b1f03501c141be31d091bdf20efaf88455; candidate tree 3d41ccfd1dab7c324a574844d75821a18dc498c8 matches tested merge d28ebef97d34458c2b2bf41555b5307911c8686b and head f9ba1ce430d50a967e9673fdd8b49d7c374ece54. Actions 37998854078: Node 24.12.0, 929/929 complete assertions, then fresh 929 before 653 component + 23 planning/recovery steps, zero failed/skipped/todo. Command: npm run verify:local; native prerequisite command uses whole original Vitest config. Source digest 5ca899c7c26266cacf0ad8b772439884f317fbbcba35389e9b5465144eaa8924; report SHA256 478afb2917e68e2c6f3e8748bda33ec321011ff873cea7cb55e875d859a8cf06. Scene artifact 11649200500 / ZIP 11610aa60338f091bd276a802e17fc5b8bc4974deb4a3937e5ad5c1edaa8745f; package 11649410381 / ZIP 40d77c3e41433e8e798e16bb29c53471f1322ed7403c54fb9e7a5ec48ba933cb. Submission 37998854115 passed. Source/runtime public exports and actual archives preserve existing helper implementation and bytes; no source fallback or development loader. Initial registry-SDK and native fixture failures remain retained above. Managed installed SDK proof still pending; 204/25/179/260 inventory unchanged.

Current execution custody — 2026-10-09

Deployment #866 retains successful run 37998634895: 1303 complete assertions and fresh 1303 before 225 component steps, zero skipped, merge candidate 1c5b9d38e24eafec742859b524273a20eb4b3f92, source digest eca5c8c23e412bdbebb4935376f22a0e7bc457ef3e5192891d1a6c35038c13c5, report SHA256 b62c45e3ab4fec24b1932dec19c0adfd0a2590d004d44b4f292e66240fd61330. Scene artifact 11648780466 / ZIP SHA256 dc9dbc26831986c6ca1eb5de5f2d759de9e9c5fbebc78a78a99d53aeca8b7647; candidate 11648128835 / ZIP 09d83ef382cbe1933e07ddf73f5d64156c8093dbf8b9d0116fd579ee6be5825e. The receipt exposed moving Node 24.21.0, so required 24.12.0 parity is unproven. Regression 03787b45 then replacement 942f3f85ed229b5f6cb0525faf30f89c863392b7 pin native verification workflows; focused regression/build pass, fresh Actions pending, no merge yet. Original failed run 37997943987 remains retained.

Agent #387 local release verification completed: 929/929 assertions, 117 files, zero failed/skipped/todo on f9ba1ce430d50a967e9673fdd8b49d7c374ece54 with pinned Node 24.12.0 and retained development authority. Actions 37998854078 remains pending.

TreeDX #86: regression-only commits 05185c1 and 37c72b46de3f5fa089f63780acaa34d7d7a9828a retain missing strict reporting and truncated-trace failures. Rust 1.99.0 was verified in native CI 37974155128; native JSON and report-time still require unstable options, which are prohibited. A TypeScript collector of ordinary native stdout/stderr and observed write intervals is under development; its three focused Rust parser cases pass locally, but strict typecheck, actual native integration, all-language reporting, full suites and scene evidence remain unproven. No acceptance gate, binding count, runtime selection or managed campaign changed.

Agent installed acceptance asset repair — 2026-10-09

Agent #368 now has regression-first source work for the shipped private-import blocker. Commit 38dec50 reproduces all unshipped source imports; 208735e adds a real archive/production-install consumer of existing shared contracts. Initial registry-SDK installation failure remains retained (/tmp/agent368-installed-public-contracts-red-20261009.json); installing the exact checked SDK archive then reproduces the missing public export (/tmp/agent368-installed-public-contracts-red-r2-20261009.json). No registry version substitutes for that checked SDK in the fixture.

The repair exports the existing owning implementations through the existing Agent root/provider-governance entrypoints and removes private-source imports from acceptance assets. No duplicate contract or new dispatch path. Native production installation uses actual Agent and checked SDK archives, omits development dependencies, disables scripts, checks unchanged asset/archive bytes, and exercises planning citation denial, clock validation, fair polling and provider configuration. Focused owning file: 22/22, zero failed/skipped/todo; strict declaration build, complete test typing and source shape pass. Two cases extend the existing component scene. Fresh complete verification and native Actions/scene custody are pending; this is not whole six-owner installed SDK execution or managed semantic acceptance. All 179 selected binding gaps remain open.

Deployment PR #866 initial Actions 37997943987 retained 1,300 passing/1 failing assertions before scenes. Same task identities appeared in a different native order; failed raw observations and cleanup remain preserved in Actions. Regression 6ae4e1ae precedes replacement 67bbd3873e2efb6bf0384af65256afbae06e42c8: exact unique-set comparison retains original raw streams, with whitespace/blank identities rejected. Focused 9/9 passes; replacement native CI is pending. No deadline, scope or assertion was relaxed.

Public owning-host inspection candidate — 2026-10-09

Deployment #834 implementation continues under this approved contract. Focused regressions were committed before the owning repair: 53ebd9a4 (missing complete inventory), 6bf31c23 (caller scope denial), 9b90619e (legitimate hardened namespace), and db54da4a (host inode/absence denial and installed CLI native proof). Original RED reports remain retained; the latest focused check is 7/7, zero failed/skipped/todo, in /tmp/deployment834-host-inspection-focused-r3-20261009.json. Strict build and source-shape pass. This is focused local component evidence only.

The existing fixed sandbox status operation now returns raw task/container inventories with a confirming read, host mount namespace/mountinfo, configured managed-directory presence/entries, observation times and completeness/errors. Caller paths/commands/scope are rejected. No runtime is constructed. Host and hardened supervisor filesystem inode custody must agree; unavailable or changing reads cannot prove absence. Unrelated resources remain visible. Eight cases join the existing component scene, with fresh whole-owner prerequisites required before that scene. Disposable native CI must prove actual installed CLI → manager → supervisor presence/absence and scoped teardown; this has not yet passed. No managed campaign or runtime selection started; all 179 selected binding gaps remain open.

SDK archive repair delivered to staging — 2026-10-09

PR #388 ordinary merged as 375575d4350ac22d43b8ca2869940c2548214721, parents95219537... and362c8049..., exact checked tree7966e97d606b4b550271238a34c31657f0b5e264. Fresh protected readback complete; clean primary staging safely fast-forwarded; only this delivery's temporary remote branch removed. Main unchanged. Unit and actual npm archive/public-contract integration regressions precede the public-import/package-identity repair; both selected in existing product-custody scene. The reserved SDK product defect is untouched.

Final component evidence: Actions https://github.com/treeseed-ai/sdk/actions/runs/37996033240 passed on exact proposed merge 85c996acc4eddb625c847d233d5438cd5af935f8: full565/565, then separate fresh565/565 prerequisite receipt before218component-boundary and16product-custody steps, zero failed/skipped/todo. SourceDigest42b637d034fb4a774ae178a2248f944e2678cf2621153d83e3dadbb8cc3d170d. Scene reportSHA256e2696e1ce351c982cf5eeeacf1496430768d81aa7b6c5b3171b66108f804721e; sceneartifact11647123312 ZIP SHA256d9f3cb02febfc10161eec7f7475da80956d23e15c96b8dc05d59d961dc0e3255. Candidatearchiveartifact11647362818 ZIP SHA2563d542507f23eafb5a196e4216c15b968cc607435426bfa838400be9a353ae4f6. Corrected submission-contract37996181007passed; earlier37996033162failure remains historical. Local fresh565/565 before16product-custody steps also passed, reportSHA256beb3c981fb3516c500d5a2ef36321b4f9f37ef794d18634051905aae874260a2. No managed SDK proof claimed.

Next Deployment physical-inspection checkpoint is based on freshly fetched cd1d098b...; regressions53ebd9a4,6bf31c23,9b90619e precede implementation. Missing inventory, caller-supplied scope and supervisor hardening are separate focused regressions. Native public-manager/host proof and full-suite/scene evidence remain required; no physical closure is claimed.

API runner restart repair delivered to staging — 2026-10-09

PR #865 ordinary merged as cd1d098b9ea9a354be32c00720d6bd7b49c59328, parents f10e85d0... and7a1ca1f9..., exact tree 884529de604077cff907d01bef3830bbe4f7f91a equal to tested merge baa9f5f7871a332d671ff83d0bab1c98c10187dc. Fresh protected readback and safe local staging fast-forward complete; only this delivery's temporary remote branch deleted. Main unchanged; no activation.
All nine applicable PR checks passed. Verify https://github.com/treeseed-ai/deployment/actions/runs/37995127566 passed complete1293tests and a separate fresh1293/1293 prerequisite suite before215passing scene steps, zero failed/skipped/todo. Prerequisite sourceDigest cb97015de7b0c7d744260de59c40ac9a189085c34e024a28bfc3a4a90532b8e0; reportSHA2564317d3924c73f82410aa139de9d4d9f79183ce49449929cc75497ad76dce6951. Sceneartifact11647366611 ZIP SHA256535f67cd45db9f1a7b8bd3381418fcc5a52e3ca1d94fd8c48650ff2b377138bb; candidateartifact11646734386 ZIP SHA256435d398fe0acbb18aa21396cb607fa31fbc85f6cd3dfbed66b163e6b12d53e73.
Backup37995127617, Identity37995127581(allfourjobs), faults37995127806, secret-custody and uninstall passed. All original failed Docker Hub500/429/504 observations remain retained below. Native backup acquisition preserves canonical PostgreSQL digest; production selection unchanged. Complete public physical inspection and managed SDK proof remain unresolved.

Installed execution repair delivered to staging — 2026-10-09

Reviewer #106 ordinary merged as 974ac78829675d2d32f11b8256d1dd968faf793c; fresh protected readback confirms parents c3771b44... and 354e571..., exact tested tree a64c6993553dad20fca2e3826926ca8c78004d1c. Only this delivery's remote codex/installed-owner-custody-98 branch was deleted; primary staging fast-forwarded safely. Main unchanged.
Actions https://github.com/treeseed-ai/reviewer/actions/runs/37994819128 passed on proposed merge 6e90b98a2af98f5b92311df9ddb40dcc40d16dc3: complete 183/183 and separate fresh 183/183 prerequisites before all 96 scene steps. Prerequisite receipt holds sourceDigest 5e529a11d6347949cc150ae15285784ad8eb15eaa43bdd23cecd2956dc9deddc, zero failed/skipped/todo. Scene report SHA256 02452c1fe5eae0f594417bc70cdf2f1c2e5179db477159cc2a3cb854a7d539ff. Existing Actions scene artifact 11646892272 ZIP SHA256 3285cae7ee3ccf10861461a8acf557c12210e0a45e51bfed5aff7c7bc40096e0; actual packaged candidate artifact 11646722879 ZIP SHA256 dd1dd61320a3682a5862903f332475dc5926d57ecc3eac7cceef34c90b4f5e84. These bounded infrastructure results do not establish six-owner installed SDK execution, complete bindings or managed golden acceptance.

Verified implementation progress — 2026-10-09

Reviewer native shell prerequisites delivered through PR #105, ordinary staging merge c3771b44c06faec78cfb45cdd94628e48809ffb3; exact merge tree matches tested candidate. Actions 37990070781: 178 full-suite tests, a fresh 178-test prerequisite suite and 91 scene steps, zero failures/skips/todos. Detailed behavior mapping, failed observations and artifact digests remain in Reviewer #98. This repairs declaration/execution of native shell prerequisites; actual TreeDX reporting and installed archive custody remain open.

API #528 and TreeDX #88 promotion custody reconciled and merged through their existing PRs, with exact candidate/tree read-back; no release or runtime activation performed. Deployment restart regression is being established against unchanged production code. No strict SDK campaign has run; all other readiness and semantic binding gaps remain open.

Implementation authorized directly by Adrian Webb on 2026-10-09. Continuation of #376, coordinated by treeseed-ai/platform#633. Historical failures and owner Issue bodies remain authoritative and retained.

Contract and exact starting custody

Complete the strict capacity-provider and agent-execution acceptance bindings without changing the specification, selection, proposal semantics, deadlines, capability caps, or SDK product implementation reserved for the genuine simulated Tester → independent Reviewer → Engineer chain.
Acceptance document docs/agent-acceptance.md SHA256 dfb012f90cbfcbf293d520008c752c1ef6f3617c2720e66717c07c8a187b89b3.
Retained/current strict plan SHA256 8b08d802d054bfedfaa2f1dfdd38626fd742b6ef180467e979afd164d26e24f2: 464 total, 204 selected, 25 existing bindings, 179 unbound, 260 deferred. No managed passing SDK receipt exists.
Fresh protected-head fetch on 2026-10-09 confirmed all 18 clean primary staging checkouts match the approved inventory. Platform 598d108cf3bf4ef1484d6b07d260e74a3b31f40c; Agent 2942a3b825508ff47a2ec3c692dc1da5825972ab; API 789a94e99cb18bea28017af4463f1fcea5695418; SDK 9521953; CLI 63c7928b2ab2456e495a0e55572b9a47d379315c; Deployment f10e85d008f5d217b1948e7615a273e375c044b4; Reviewer 1e3019fbf24163116222dc96a70c126bf3488389; TreeDX 367fec4237c6928969c969c05217bdb9832b41ac. Library binding healthy at dd0e5ac944761a719b96046724661783b465421c.

Delivery and ownership

0. Reconcile existing API #528 and TreeDX Add SDK agent discussion messaging contracts #88 promotion custody before new package implementation. Preserve old metadata as historical evidence. No mass history reconciliation.
1. Reviewer: include executing package in fresh prerequisite custody, explicitly selected CLI native boundary; support declared native verification beyond .exs; retain strict assertion-level fullSuitePassed contract. Add --installed-packages absolute directory to existing runner. Hold source Git candidates and execute matching installed archive assets; reject symlinks, source fallback, missing/altered helpers and mismatched definitions. Retain archive digest and installed bytes in existing run bundle. Product-neutral implementation.
   TreeDX: TypeScript collector around original native commands, all SDK languages retained, native identities/status/observed timing/terminal summary and exact count reconciliation. Truncated/ignored/filtered/duplicate/failing/interrupted output fails closed. No unstable compiler bypass or synthetic assertion timing.
   Deployment #834: reproduce operations-runner restart EEXIST first; use existing staged materialization, drain, replacement/readiness pattern, preserve copier duplicate denial and 5s/30s bounds. Extend fixed read-only manager→supervisor sandbox inspection with complete owning-host tasks/containers/mounts/managed-directory scope and completeness. No arbitrary paths/commands, privilege expansion or resource-starting inspection.
   Package owners ship selected definitions and minimum executable asset closure, using public exports/reads; actual archives installed with production dependencies and scripts disabled.
2. Agent Promote verified capacity-provider endpoint validation through staging #368: complete current freeze (seed, protected primary/library refs, builds, profiles, policy/offer/supply and draft/ready proposal bytes), 17 proposals/136 definitions via governed public reads; full external baseline; eight addressed in-discussion chats without graph edges; substantive role responsibilities and two predecessor-consuming cycles; genuine seven estimates and research request-changes/correction/independent approval. Complete public histories and independent producer inventories, validate each new assignment before continuing, scoped stop on violation. Existing campaign owns exact three failure classes, exact review report, unchanged reset, useful retries and three unexplained repetitions stop.
   API #515: real PostgreSQL independent-connection producer-to-public inventory completeness; atomic assignment/lease/reservation, immutable issuance, exactly-once settlement/failed history; proposal readiness/classed decisions/profile dependencies/six generated review pairs/reconciliation noop; actual first/final protected clock actions and clean schema.
   SDK / CLI feat(deployment): declare explicit PostgreSQL migration lifecycle #274: native Git/subprocess frozen BASE RED intended assertion, test-only Tester commit, independent review, Engineer ancestry and identical committed test blobs; actual Writer examples and independently resolved Researcher citations/corrections; exact public release commands npm run release:verify, npm pack, npm run standards:acceptance -- --archive , paired independent replay. Leave known non-enumerable retired-field product fix for simulated chain.
3. Integrator alone edits shared registries/manifests/SDK scene ordering/bindings. Criterion 51 is mapping-only; retain 20 adequate narrow input bindings and strengthen 11,12,170,184,192. Select normal-run cases only where their preconditions fit. Keep completed/failed and continuation cases separate. Require all 204 identities semantically covered, no binding diagnostics, 260 deferred retained, installed asset and selected runtime read-back.

Required verification

Regression first, then real owning integration and native coded scene. Every acceptance invocation first executes complete unit/integration suites for every participating owner freshly on held exact candidates; failed/skipped/todo/empty/filtered/missing/inconclusive reports block scenes.
Agent: node node_modules/vitest/vitest.mjs run --config ./vitest.config.ts; npm run verify:local; npm run release:verify; npm pack --json.
API: node node_modules/vitest/vitest.mjs run --config ./vitest.control-plane.config.ts; npm run verify:direct; existing native PostgreSQL/TreeDX supplements; npm pack --json.
SDK: node node_modules/vitest/vitest.mjs run --config ./vitest.contracts.config.ts; npm run release:verify; npm pack; npm run standards:acceptance -- --archive .
CLI: npm test; npm run verify:direct; npm pack --json.
Deployment: npm test; npm run verify:direct; existing disposable privileged native verification; npm pack --json.
Reviewer: npm test; npm run verify; npm pack --json.
TreeDX: ./scripts/verification/test-all.sh and ./scripts/verification/test-sdk-packages.sh; existing native release gate.
Use pinned Node 24.12.0; preserve TREESEED_DEVELOPMENT_WORKSPACE_ROOT=/tmp/sdk369-platform-authority-de2LzF exact e4c4cad1e526f53d3549c8fc27c3e60122b20ee4; native PostgreSQL, all native SDK toolchains, existing TLS trust and disposable native supervisor/Kata host required.
Evidence authority is Actions artifacts and this/owning Issue bodies, no routine comments or duplicate campaigns. Ordinary test-first commits and checked PRs → staging → composition/read-back → managed acceptance → checked main. Fresh protected heads before branch/merge. No tags/releases/publication/new environments/worktrees/automations; retain 34 unpublished-work leases, quarantines, encryption and all history.

Completion gates and current status

• Binding complete: 204 semantic assertions and selected wiring, strict zero diagnostics, actual installed assets, 260 deferred.
• SDK ready: complete fresh strict suites possible; native reporting, installed custody, restart and public inspection repaired; exact runtime/current 17-project/136-definition freeze, sufficient supply, full external baseline and durable reset.
• SDK golden: actual strict invocation passes all managed semantics including genuine revision and test-first product chain, native usage/clocks, exactly-once settlement, Reporter and durable physical closure.
• Full accepted: SDK → API → joint → remaining 15 individual → all 17 → controlled failures; full 464 gate.
  Current status: implementation started; no new tests, code changes, campaign, runtime mutation, branch or merge yet. All completion gates OPEN. Alternate authority, second runner/model, changed proposal semantics or relaxed deadline requires PLAN_REVIEW_REQUIRED with original evidence.

Criterion matrix

Class 1: narrow assertions adequate; mapping/revalidation. Class 2: partial semantic or wiring proof. Class 3: missing executable proof. Class 4: implementation/environment/current-authority blocked. These are audit classifications, not passing managed evidence. Full requirement text is held at the exact document digest above; line and section identify it unambiguously.

#	Line	Exact criterion SHA256	Class	Existing binding	Section
1	38	77c663e3ba07371f72cb574bdf4d3d2b5ccce397c21ae7a79a0e43ba97f7e1a1	2	no	Non-negotiable rules / Automated execution authority
2	44	6a572f1a5833a039bdc575588d8e6e272a0e71a29a5faaeeeb7b5c85d6544ee6	4	no	Non-negotiable rules / Automated execution authority
3	51	2451113fc3c00a8a2948a7afc52f9ca85ee86b3374e5fdcc25024ec1c946e2ad	2	no	Non-negotiable rules / Automated execution authority
4	59	64ffc06b0d268ad11fbf692ca201cd75423c0afae2a6be3e2ae7cd2eea7fb17f	2	no	Non-negotiable rules / Automated execution authority
5	60	6d34d659df17e81ab1b96cf86c9fb401b7dcaff4a59a49a41999fe38e65f9bd9	2	no	Non-negotiable rules / Automated execution authority
6	61	a5f8e4a6529f2fc535f1d7671be2af38c6e8411b9baaaf8753a9af9280dafa57	2	no	Non-negotiable rules / Automated execution authority
7	62	c7407ee19bbf004613f91447110cad5d16ea5f40eb04ee01d804d6e7366f07cf	2	no	Non-negotiable rules / Automated execution authority
8	63	4cb6912b46392b346b92819f5e95dcddf4ce3466802a81f79869dedd6c6734ab	2	no	Non-negotiable rules / Automated execution authority
9	64	73706b74d24775782c346f427a33f7ea9386e0038f7c50fa7cf317dfa30d1fd1	2	no	Non-negotiable rules / Automated execution authority
10	65	b26de9a0e03d3e89af32a7cc48b5f09b23498006423fc89dd62f990944e89d23	2	no	Non-negotiable rules / Automated execution authority
11	66	b635827ed7862d56b8764dfad30114b9ee18d02b4aa709a257841e18a1bd0f0d	2	yes	Non-negotiable rules / Automated execution authority
12	67	7eaf9fdc1c264e2d0b28d2fc751da33a2ffcf98ca0d6446ac6e8672503dfa533	2	yes	Non-negotiable rules / Automated execution authority
13	68	a571727bb7e1d74fcf9fda7ba50ecd003db8732cd1be6183c2f80ffa85d43691	2	no	Non-negotiable rules / Automated execution authority
14	69	2e5d3dfc2cd33fd0656866a59ce59153137c199b766309decab4f71ecbf4e8d7	2	no	Non-negotiable rules / Automated execution authority
15	73	4fec957beaa1692299741d8e2d5730027c2f1012f0ee8a4d17e89fadf3a1a524	2	no	Non-negotiable rules / Required contract correction
16	75	b24c4b3b916a142733dd2411f37acf37f8655ed1b3c57fdbc8e01a5276d236f2	2	no	Non-negotiable rules / Required contract correction
17	81	b3c05efaa7ca49ff50b801f9c90cc598383a93afb712a7da4ba125c6efce590a	2	no	Simulation custody and repeatability / Campaign freeze
18	83	5a286ca84dffc7ea229c2035a106c26aa0f8fe4e78da3cb035b1bc4859810e95	1	yes	Simulation custody and repeatability / Campaign freeze
19	84	ab2ac9ce3bbbf837b5c65b9b6246aa6850713b4d82fc15c52d590144dd265a0b	3	no	Simulation custody and repeatability / Campaign freeze
20	85	9780db98a89476091e8d49891f9fb48d34e70b652c3dfac1e5d112073005860b	4	no	Simulation custody and repeatability / Campaign freeze
21	86	7647173a0e973e700a4eb74b9ecfe960ef408dfb6c2e34339ac7a0afac8a89c2	4	no	Simulation custody and repeatability / Campaign freeze
22	87	d0d88543bffc985ae6a97d06ddc7437472347967b6797d3f797e11a20d2efae4	2	no	Simulation custody and repeatability / Campaign freeze
23	88	81543856c351d2d7f2599a17d9225b1d5d6785c88897775ff79ec4b2af482b65	2	no	Simulation custody and repeatability / Campaign freeze
24	89	2feaea9a8a706e1279affead3af5bacc467f12b285ba2570f183361c5d8203c7	2	no	Simulation custody and repeatability / Campaign freeze
25	90	3b1b0b3e69460a27e2e322fab6c989a2d9928a6229b3820ac174a557b21f0122	2	no	Simulation custody and repeatability / Campaign freeze
26	92	9221e8f7914ad1f24a94231c6e1ffed3e57f4831493f43ac9ed8bdcb01f228ae	2	no	Simulation custody and repeatability / Campaign freeze
27	96	7176aa4d3bf381690af4e016090cf096abf273cd5a4f15eae0286d0373827b5b	2	no	Simulation custody and repeatability / High-level allocation inputs
28	98	1dd6f762ce6507847246f790bf57d735bcefe27c21bf8338a179dddbe3d0f930	1	yes	Simulation custody and repeatability / High-level allocation inputs
29	100	ee31029693c8c8c0e9e1b8506a341cbb4ddbc15c585cf16de713dc540f68bf55	1	yes	Simulation custody and repeatability / High-level allocation inputs
30	101	70a2f58978eb3f6f32b214260bc87ac3ebfe11060c801f179bfc75da2d06e2ef	1	yes	Simulation custody and repeatability / High-level allocation inputs
31	102	a36454b4c07f4f736d412c1839e5cc095481697b65a27b757515fabd34172203	1	yes	Simulation custody and repeatability / High-level allocation inputs
32	103	c7a791cfb40d560a846fca80c0e59258b7793e0bd57499b43d9f61df3d2e9b41	1	yes	Simulation custody and repeatability / High-level allocation inputs
33	104	3b816289341ea3e179c9e4b75392cff59c7fb254580e63c92c87d96b8a5223db	1	yes	Simulation custody and repeatability / High-level allocation inputs
34	105	98984bf7e8b6f1b04e3e994888be21daf1d224eb367d95a0849cd5f6dd94f2a5	1	yes	Simulation custody and repeatability / High-level allocation inputs
35	106	b53c04085fa78d71c15f32d94f32b925c316f404a67328a466887cd3d9f34c95	1	yes	Simulation custody and repeatability / High-level allocation inputs
36	107	b1862b020ba7f70a9154abe27dc0a6466030dc0d6b3f63f34bdd0485e8a3feba	1	yes	Simulation custody and repeatability / High-level allocation inputs
37	108	7df1b6212ad765c7c8538b57df69150c60b7ac8fa19242111963da6f90b2c088	1	yes	Simulation custody and repeatability / High-level allocation inputs
38	109	673111d5d0ef3029b0b7bc57eccf0515b661cdaf615ffc0206aa3d085a80f1d5	1	yes	Simulation custody and repeatability / High-level allocation inputs
39	110	117e7a5900a48c54a4d536d71de49708dacf59fe52aa27a7ff8c67b4d17d5c16	1	yes	Simulation custody and repeatability / High-level allocation inputs
40	111	962cf6428dc2cdd1f720d29bbb68abf250cfbbfe128ac4c79d7f5aee7b6e661a	1	yes	Simulation custody and repeatability / High-level allocation inputs
41	112	f29da4387b40305b08caaf15b955526cd99c97df4117eec47d40257d48900157	1	yes	Simulation custody and repeatability / High-level allocation inputs
42	113	f86cab61d39ea7f46fb9171c3d75a5e547b256cedd6ec5ca6c480ae26822ef26	1	yes	Simulation custody and repeatability / High-level allocation inputs
43	114	67be60c1ce8993d62e20243cf53359ceaf58ab1d8866589af00cae11cb12e295	1	yes	Simulation custody and repeatability / High-level allocation inputs
44	115	772870fb89c0c04ea930fb424cc66a0a057131849b5ba8b59f9d1f0da8e48567	1	yes	Simulation custody and repeatability / High-level allocation inputs
45	116	bff803652752fed25c48491f7eb474367fd2c061801612238e24f29037db2424	1	yes	Simulation custody and repeatability / High-level allocation inputs
46	117	7f4f6bb99633197d6e94efa969cf8fa2da8f65e559aeb22da5707a8fb82c4265	1	yes	Simulation custody and repeatability / High-level allocation inputs
47	118	8ef82a4f4cb2b8e93d060e38cf8758944d2ba54baca44787811a1d76683f99d4	2	no	Simulation custody and repeatability / High-level allocation inputs
48	119	9ec106d2eaa261dbf0c21635f2a65828718495b8cfba5280b3f247d3e62269ad	2	no	Simulation custody and repeatability / High-level allocation inputs
49	121	3f838571e122c75bf4c846e686c91eea21ad02c783c919de2a5023b8efe8f6a9	2	no	Simulation custody and repeatability / High-level allocation inputs
50	123	6e48b90ae52851e7b8fd728de8bb32610a60fc7c93dd445a93d3354aa00b652e	2	no	Simulation custody and repeatability / High-level allocation inputs
51	125	b918b519ac545fdd61faab208687ccc64e1f3d03c9a84dfc57a5cfee6190f3f3	1	no	Simulation custody and repeatability / High-level allocation inputs
52	144	b6e92528f351cfe23f81ba0360fcbaa793a09901a631ea997c1753296a8600c0	2	no	Simulation custody and repeatability / High-level allocation inputs
53	146	fa413270938fc996715f2ea99a0ed694d46f63676cb473ef913f34dc54e0403a	2	no	Simulation custody and repeatability / High-level allocation inputs
54	148	10da9a698824f8f49781e29ea86f4e274753ea74e0425f81fff1b8ea9f44bddb	3	no	Simulation custody and repeatability / High-level allocation inputs
55	150	8fd81af8c5209c43333ee6c9b28f6519406970d59073c094cedc58a2a27c9cdc	2	no	Simulation custody and repeatability / High-level allocation inputs
56	152	989b8cc37ba2e8ad480798ea80477188c32bc7aaf78a946cd4371015d5d68e26	2	no	Simulation custody and repeatability / High-level allocation inputs
57	156	4320bd5f386db7ba558f1f0812ea60786b8712186c8a21f4d30dc8296ecb10c6	2	no	Simulation custody and repeatability / Local Git custody
58	158	3e359934ebccfb10c84a6bbc24ad108affd0ba0963bec997915b4a39ce6d3981	2	no	Simulation custody and repeatability / Local Git custody
59	165	6306a7155d10c1c3ee17e4f294227f814951d8db9fce0a5aafa359ab8d5ae1ad	2	no	Simulation custody and repeatability / Local Git custody
60	167	98fb608e424d3f9348923a05a9154fc9d18ca5ebb65d00ded5efb5936ce7ccee	2	no	Simulation custody and repeatability / Local Git custody
61	171	efe4022ae1e1a6d6f57f3d8d687153fa6b4281e5cc050bfd428b6a7ec91490b6	2	no	Simulation custody and repeatability / Reset between retries
62	173	728f2955091a0b8cdeda8328d73ebb9a5f4f61fa5e49a92b3a0cde5d2ea276f1	2	no	Simulation custody and repeatability / Reset between retries
63	174	48ea65200fd7a65a446e0b5cc6ac16768176ee2b6436710a6187ccc0f68fdc85	2	no	Simulation custody and repeatability / Reset between retries
64	175	ebcd281056bc72df2d0a0baac6d26307a88f07c18a8a61b4b7a7fb7aed54b044	2	no	Simulation custody and repeatability / Reset between retries
65	176	fadd4e810c113c26de4bb704d65a0b4f9897cfcf87657d5eaf4f87209318dc92	2	no	Simulation custody and repeatability / Reset between retries
66	177	6f5903c6fa5a5f2c38e24414b12d3ad252ebe1b95007bf9aa407af111c9d4e9e	4	no	Simulation custody and repeatability / Reset between retries
67	179	68a027c1f64abd3f14d91ed36c099ef8af10dfe1f9281b8a51359e7331f67d8e	2	no	Simulation custody and repeatability / Reset between retries
68	181	cf37579db701a4ed6cf19c137fa0bf4c136068d8862918ccb7f94e7f279ff924	4	no	Simulation custody and repeatability / Reset between retries
69	185	4acb64e64720d4134566ff0de32816c8321aac7e88728a87c11b01d8f88c769a	2	no	The canonical proposal lifecycle
70	187	2b8cb6c3b6c1014b10ea1263a4e5f0aea2a1b93ae71ec69a0abbb410b304fab1	2	no	The canonical proposal lifecycle
71	188	b06a86bd461d6b85f92908c972808a53bdd76d725af810911018c85577480e54	2	no	The canonical proposal lifecycle
72	189	81b30905093d840992af882b011c2432cc199883a09a948a0fe1c8aced8518b7	3	no	The canonical proposal lifecycle
73	190	be135a07e724c5b093c60bffec9e69304a89a6eca9d2cc89a6ae5f1f85d26d8a	2	no	The canonical proposal lifecycle
74	191	ca2e5e81f54794d251c8f59e64a7665ed274ae2bb382cedc38016e94096085a2	2	no	The canonical proposal lifecycle
75	192	fee988264ac2507890e8dd2e1afee3ff23c868917b174c97a532b2b6e6c02764	2	no	The canonical proposal lifecycle
76	193	c7bb1b569687ae6865ce03f335cf18c0b089e82561ef105f61ce3a188f3ca15d	2	no	The canonical proposal lifecycle
77	194	8e39bb80de13bd6cbad46f12bb890cc41bf1bac8ae8ec749259a0e94ac5faf99	2	no	The canonical proposal lifecycle
78	195	6a21fd98230155d81683582076386eca4605b18fa0981b925f29baffa178d3bc	2	no	The canonical proposal lifecycle
79	196	ff9a8a41b66f236fd3345aacbc30b33f05479553635243df81117d9ce8ae2ec8	2	no	The canonical proposal lifecycle
80	198	bbbc8fac66e2ba80b424233688eb421112ab33a1ef83b372362bc82f19970059	2	no	The canonical proposal lifecycle
81	200	1d78188569795d519ac4733226413a908e41f718f7477081d5d6bbd9949acc8f	2	no	The canonical proposal lifecycle
82	204	9ecbad0aa82dc3de124b485fac975631f088d182d4e04fcad881024fc8b5a611	2	no	Common activity-profile expectations
83	206	cd6c36f1adc3a851aab97b67d3d382b4a4127a0b10a818fc78990951eb5072c1	2	no	Common activity-profile expectations
84	208	d5b3bcb8ef18cbdc71fb2cad6fd4a5a4d38a4e203f841050918a824f8676e1bd	2	no	Common activity-profile expectations
85	209	3996bfa9b8c57f11de24d570adaca824fa5883d23c7d4bd4106f07086f8835ab	2	no	Common activity-profile expectations
86	210	4bd72f78ed7d783220d67472c98f6dcb88194bf040adfcab54ac6ad81144ad53	2	no	Common activity-profile expectations
87	211	14449c0ba65b7b7bc3915fb2ef87db4361db5b3c1a16eb5e3965b15787e0a633	2	no	Common activity-profile expectations
88	212	878d21214be322d60129356ce3bc779d71a2381e9fc49e05c5442a485da8fcbb	2	no	Common activity-profile expectations
89	213	ae850ba87f0c47a42f678d27bf772635c3cb02e9bf566bf0619fbcfaf9d049a1	2	no	Common activity-profile expectations
90	214	c17d021d5d00fe0107e65d92f53c9c67ce329fe404bf94686c83984c21b76111	2	no	Common activity-profile expectations
91	218	e4c9575d1d5cf25a9126daf0f310ae845655cb7e8cd3c8b9aa8c8795162338a6	3	no	Common activity-profile expectations / Expected planning contributions
92	219	bb05a70cfdd81bdcc2e73ed69a384ad59a73853e6486eea7f7d6a6e16246748b	3	no	Common activity-profile expectations / Expected planning contributions
93	220	083209aafcc48a67056774c616afa8791083099c36a795c136d813586591261a	3	no	Common activity-profile expectations / Expected planning contributions
94	221	bb44ac6ac02f3c0d403a695469a85f14954a9d240634b7d42c29dd35b83b4eb7	3	no	Common activity-profile expectations / Expected planning contributions
95	222	e63fc5f58d2970b868e085f465c0826fc997117cd49aae9cb8f66fa210809528	3	no	Common activity-profile expectations / Expected planning contributions
96	223	60ec8340f6722eee005de472246ad735d2c56c9b6bdf6b1d0762e94c34a2c6ed	3	no	Common activity-profile expectations / Expected planning contributions
97	224	d7ff939b45e0044002f1ef4db55f4e32a5de96a84f49e95336e459c63605f2b1	3	no	Common activity-profile expectations / Expected planning contributions
98	225	5b2986027c698df628ff679d24ad2ab99c8280a0f86293c8f3c7de8d47f6abd6	3	no	Common activity-profile expectations / Expected planning contributions
99	227	c0e7fba19350ffab6828e54f02109359dde1b7fccd76f0f15fe5b02b7c9407d1	2	no	Common activity-profile expectations / Expected planning contributions
100	231	0cb616106a09f5279323a975d315c59ebefb6e5e0db2ef52e153c0995038158f	2	no	Common proposal work-item contract
101	233	f02eb0d95e0572b52f73700b689cd584d9ae57a880ca5658546c1cae44b535e4	2	no	Common proposal work-item contract
102	248	e2bf7c70f63b2f4d1532a2d9c62fd7d5b4305151bcadc9c650a3a48bcd8649e7	2	no	Common proposal work-item contract
103	252	47b521b0831f30babf7664f8e12de9b9336a9c949de98473e1767212d7a76cd2	2	no	Common proposal work-item contract / Fixed work-item graph
104	254	95e989b76535f28f68527b4e3cf57ca49437695c9f97c57acdfca81d2f62055a	2	no	Common proposal work-item contract / Fixed work-item graph
105	255	96a6b0f3ae0587119f592e97fc93efdaae676674a34fb9e9511fd0a9a044fd6e	2	no	Common proposal work-item contract / Fixed work-item graph
106	256	11dc8f94be641ad4a78110ac48b1a33144ab46b5a4faac7b3eba1c3873360ec6	2	no	Common proposal work-item contract / Fixed work-item graph
107	257	9aa7395c3dc83d555538ad7b6ecfa3d307744044bab0de0574731218ca2e7710	2	no	Common proposal work-item contract / Fixed work-item graph
108	258	ae904659a63c9d7478fecc4ba97674ff617e9aee8e0d4e2c3aa96ce1eb16a7cd	2	no	Common proposal work-item contract / Fixed work-item graph
109	259	a36158a2e8f122136ece95b41cfd72c345beefa609df5ec27e296b56e77de930	2	no	Common proposal work-item contract / Fixed work-item graph
110	261	303fe1d790ea82e3eae083f6f477e2434ab44df60c2e7b2c799be1f6af61d27a	2	no	Common proposal work-item contract / Fixed work-item graph
111	263	a6f86094d3c2dc802a54319c3b55c1fb50fa3f1bdc5f9ee831088347c22732bb	2	no	Common proposal work-item contract / Fixed work-item graph
112	265	614467b937b7b271b37e1e7b484adba4d65cf486993d9273807130dcc351f69e	2	no	Common proposal work-item contract / Fixed work-item graph
113	269	5225ed550726fbcb844fa46c968221c6aa84e694f477dbec024a2c62604e6e5e	2	no	Common proposal work-item contract / Fixed permissions and assignment workspaces
114	270	bb1e425861ce6c4e6e61ed4f2eeaa39cbcb87cb621edc8e0d10dba4cf82ab681	2	no	Common proposal work-item contract / Fixed permissions and assignment workspaces
115	271	210c4c11e3c7150e04ba6c29bdab3ad6277418567fb0db8c6b7c342c13cdd897	2	no	Common proposal work-item contract / Fixed permissions and assignment workspaces
116	272	a213575995fddb824b0b28283bf4cd9532b73b573da57ac3c492aa9aea00bcdc	2	no	Common proposal work-item contract / Fixed permissions and assignment workspaces
117	273	dfb95035968dd59b213d812c3023894e30dec856700eaeb985f0556cd53d0088	2	no	Common proposal work-item contract / Fixed permissions and assignment workspaces
118	274	2bcb03ca47bbe9ffe324405ca36a2464dbe0d613a7777b6973d0b10bd6ea50dd	2	no	Common proposal work-item contract / Fixed permissions and assignment workspaces
119	275	1b8f85527f4b286aff075cfe1892180d1407c503fcebab5193560cb915699ea3	2	no	Common proposal work-item contract / Fixed permissions and assignment workspaces
120	279	2a1689154ac608a5cac8aafd0d02fe6117c4d2aa82906682a837af026adfce57	3	no	Common proposal work-item contract / Fixed product chain
121	280	c81d18f5f6f66b5225a960d07a6c46b1545da895a097ea075837175e1dfc614c	2	no	Common proposal work-item contract / Fixed product chain
122	281	f2a4ccdf8ff3c85e44b25f5cc4bf1597ef28e63f8217dd52416305c0d6dc345b	3	no	Common proposal work-item contract / Fixed product chain
123	282	f87dda27c2218e505d7a6723bf09ca896a84095f5b1aa9336c9afa05a920d153	3	no	Common proposal work-item contract / Fixed product chain
124	283	ee95f7eb3323545534ac708f6ef6ae9d6b9ae2ae40ad4268738084a25d293d86	3	no	Common proposal work-item contract / Fixed product chain
125	284	38beb78ee665869dfcd6d42a773f1b6440d4988fd9e5b0d06d3b992d3f297e5c	2	no	Common proposal work-item contract / Fixed product chain
126	285	d7d8607b258929b287d068c1c35fdebaafaf25f86ab71d0a0c65960039f3ac28	2	no	Common proposal work-item contract / Fixed product chain
127	289	9716662f4e9dc84f97a1c4bcad4b592672662aab328ad1b26c199ef61aee00d3	2	no	Common proposal work-item contract / Reporter selection
128	293	6e8f096457026f1992cb08a4e36f02a7c5b55b472e7019ff615866256fac85d2	2	no	Project golden proposals
129	297	15ec4b36db97a7cc1693de218c767b356e7294de3071297151a8847884a2999f	2	no	Project golden proposals / 1. SDK — decision-governed workday intent
130	298	4f295a5342aaf08b1ca056a5aa8bc00df27a07cf116b6721b6179d575c6b76df	3	no	Project golden proposals / 1. SDK — decision-governed workday intent
131	299	936013d37582fbedab56e17601be3581682b72565d8b7fdaedb75f6a3cd2e64f	2	no	Project golden proposals / 1. SDK — decision-governed workday intent
132	300	9a9b626b666f555139baf8aabcead659ca30e7f88ad8002f73f2b35ddf542ad4	2	no	Project golden proposals / 1. SDK — decision-governed workday intent
133	301	97bb37f205e9510f31ac55a03fc054f8be43b2994bd1eeef50cc9623f4c07b2f	4	no	Project golden proposals / 1. SDK — decision-governed workday intent
134	302	8fc0d803455b8e437a458732d5b6ba575f885eb35ba387e93e14230dd40d27b7	2	no	Project golden proposals / 1. SDK — decision-governed workday intent
135	304	fa61b457ce5888b2936d1da87154e777c287d910082920fe0d6ecd962243118a	2	no	Project golden proposals / 1. SDK — decision-governed workday intent
136	306	8cca846b891a94358f5b14d10ce2b347fc68e66d23fb7b9b4f6400495c2e29e4	3	no	Project golden proposals / 1. SDK — decision-governed workday intent
137	307	35809477bc36087b4180c1320bace5b4200cc15b3892a7ed0520a6af2c5474e2	2	no	Project golden proposals / 1. SDK — decision-governed workday intent
138	308	abbd97bffac95911d0c95f43ba66d842dcee51bd2cb8178e778d8f192b237ff6	3	no	Project golden proposals / 1. SDK — decision-governed workday intent
139	309	736512f0456c2e9355139858303c36bcc227e265bc5b1fef907031a131cef283	4	no	Project golden proposals / 1. SDK — decision-governed workday intent
140	310	34d5cfa43449a58580eb1375eec92c328a50e3ee50b03f1fb79703f935ebafa0	3	no	Project golden proposals / 1. SDK — decision-governed workday intent
141	311	a4199e48998233b28a6aa7480d4a386c32675970f2989ad2719240055fa91443	2	no	Project golden proposals / 1. SDK — decision-governed workday intent
142	313	deac3029750e7e979a78d53ff80fb97f07a9ba1023f79a70a13b5ba9f59154b0	2	no	Project golden proposals / 1. SDK — decision-governed workday intent
143	315	7592ca5bb190bdbb0076c2ece19a0b35f2697f32555557ada2255cfa40afb690	3	no	Project golden proposals / 1. SDK — decision-governed workday intent
144	317	9ac73476e2d988533827fbfefe5178fc4b83d2b6e6daafe0a14d76816ec643b7	4	no	Project golden proposals / 1. SDK — decision-governed workday intent
145	627	8de17d1016c64abb63c195d3e9a3ee9353c3fc98e2ac3b20e3393b33ebbd97cd	4	no	Execution order / Stage 0 — preflight
146	628	a91442785b2fb175d026abe733095093fd4fc975f2485d29ad17c7229c237e24	4	no	Execution order / Stage 0 — preflight
147	629	fc80e789a38eb6ae75fada867226ac0157844505619b12c90c55cbe317c6cc9d	4	no	Execution order / Stage 0 — preflight
148	630	fd24ba360296be2c7df07115ec42d421257978d34e9bb61d5605a0db9a4fec2e	4	no	Execution order / Stage 0 — preflight
149	631	5c18c71e191e10f5ef21f17bdef2340ce3bcbb748c466a504db12838d70b2000	4	no	Execution order / Stage 0 — preflight
150	632	7c8665a0748921f0950e6adecb9f3c1da60d25b5300ac95858d066db21491b24	4	no	Execution order / Stage 0 — preflight
151	633	d00910e63c8f4df319158d8a692499648dc88c7c01699fd6c175696de27fa41f	4	no	Execution order / Stage 0 — preflight
152	637	e13d75ef360f0ceff14f46453139f84cff1d4067b73145d0ded19282b2a9c6bd	2	no	Execution order / Stage 1 — SDK alone
153	638	4d5605b2536a3bae89a76684832ef5f028b1bb20acbcddac7ed72ffd01b9163c	2	no	Execution order / Stage 1 — SDK alone
154	639	1c9e7d2f0800a6c404e2acb9a05ac017a0ae91ffed3c542236eb1105f47390b9	2	no	Execution order / Stage 1 — SDK alone
155	715	a1277fc9200f8ac2647eedd1a85709ba644a72daf0f215d27917adbad525e14d	2	no	Mandatory live monitoring
156	719	ac2194c4af9c0662162065f4ba7873747c525e950a779faced3d576895528a98	2	no	Mandatory live monitoring
157	721	3a89aadec8aa532de1eda910051dd97f36f118145cc0922315e20d02a8d7d60b	2	no	Mandatory live monitoring
158	722	9e12c2ff2b78f2ad7f30476027cb34e5c34c9285b0d2b0324427c260fddb71bd	2	no	Mandatory live monitoring
159	723	c284ecb8b5cddbd8ef35e9d0796cae52cb1c750ff85f90e6801da9d5ac373dde	2	no	Mandatory live monitoring
160	724	4eed8913d17a59d22abba957017b7f7d41a39c9818da05081950ce169b8a52f4	2	no	Mandatory live monitoring
161	725	e711fb4ccc31f922ae1f28424d0f1de3d5c006ab923d19fbdc1e3a93ad8f4224	2	no	Mandatory live monitoring
162	726	e6c74fb3d597079d197097bedaef4f35935d23dcd9d62aef97369ce37d1f1fee	2	no	Mandatory live monitoring
163	727	243468aa577369bf6d9f6bd77eab448104b87a6ae24f1d88185f7cc1592ed916	2	no	Mandatory live monitoring
164	729	d4b37f62b1a5213c66ccfb1130237cf8f7e43e9b8732746afc4fd7a629f75ba2	3	no	Mandatory live monitoring
165	731	944addfb4474a6ab9b5b1babac782558fec827e6b9a501f849371f33d660fa76	2	no	Mandatory live monitoring
166	741	7eb2b6f1978907c248e94d9411b907cfa56ddc40dc7794ea4bb923369c3392a4	2	no	Pass criteria for one project
167	745	ce87c6c4895321258d1ff9d3f00d7e0db7f1adb6639696756208e784d546667a	2	no	Pass criteria for one project / Governance and graph
168	746	564ed8da26e57b92210bce4029cc53989257b48537049690106f2a4e3400e592	2	no	Pass criteria for one project / Governance and graph
169	747	4ff1e6e55ccb0038c0f79331029c2ad083409c36058b1e3335b1b44a263b2ce0	2	no	Pass criteria for one project / Governance and graph
170	748	6d6749cd8c2676c6c50c009b55025ec3b951589db602440f63b76ba021159f20	2	yes	Pass criteria for one project / Governance and graph
171	749	697358e950cb89fc5928569468cd955c25daa8fda7ff97fd1a4af35e2eb95fc6	2	no	Pass criteria for one project / Governance and graph
172	750	7db60618a6757d8741156428465e37c46211c1a8a5b2125cae87550534778751	2	no	Pass criteria for one project / Governance and graph
173	751	10e9a8f73402ff3c2bc8eba5f20d45e8a3cb81e45dca644f4ad3ff59acb01ee5	2	no	Pass criteria for one project / Governance and graph
174	755	ce8a386ea8718aa7bf61c8a5a4602520e62bc90d036ff71adf98cb583389973d	2	no	Pass criteria for one project / Profiles and collaboration
175	756	1915bbd110766af482d0e602362d4cf8cb23600946a3a118d773a3f9457c1304	2	no	Pass criteria for one project / Profiles and collaboration
176	757	948b5a226d7cc181a951a4492c9cd8e08d4f2526e2635d0d1c0f0df9c41c94bb	2	no	Pass criteria for one project / Profiles and collaboration
177	758	ae2b37b1d7dd6691de52c2ecacc0d17d9c0ee879889adcc18f580f3eaabb2176	2	no	Pass criteria for one project / Profiles and collaboration
178	759	9778c4caf01add1b3815fa1cd3fe27ef11073cc98dbdc4a5deeb54e2a441f1dc	2	no	Pass criteria for one project / Profiles and collaboration
179	763	22f329d858029233d66c747de963c8ac14c8655b0fe536ee1921ec39101ca1b8	2	no	Pass criteria for one project / Assignments and outputs
180	764	20c93954e2491ac9d2fb4c9a3632073f5e520ee4dda8fd5e3f114aff1076d750	2	no	Pass criteria for one project / Assignments and outputs
181	765	4d3a65d9ab4becd82cc9336051f6e069a26bfcd662eb52fe3f7a32f67c8530bf	2	no	Pass criteria for one project / Assignments and outputs
182	766	cf2bbda296d490d3bd5ba05de1f7e997a8e37d50b1cbdfc99667230b5d58fe4e	2	no	Pass criteria for one project / Assignments and outputs
183	767	8a44a09cbcc4fc65a34e37d7fde84c6a188a97316c052e565feec2b0e41c77e7	2	no	Pass criteria for one project / Assignments and outputs
184	768	80496650a6ed5888fbda21ddcb15047d221874adb709887306dede9e3e93ff55	2	yes	Pass criteria for one project / Assignments and outputs
185	769	f3bf718737305d7ef5d405762479bdc5f688a20e6e6ee1443c5e8a2ca11dd3a6	2	no	Pass criteria for one project / Assignments and outputs
186	770	5ac90e451b0365ff6c44bfbcde86252eb1b53adf6b97972d00a7d5f15b9bf0e9	2	no	Pass criteria for one project / Assignments and outputs
187	774	4d7e203710c6585ac30773f028ca00314712e415ed746ce3c5eda3075d616aa0	2	no	Pass criteria for one project / Workday, capacity, and cleanup
188	775	888a86bc48b9b3e86f8db79534cc7f49b849247800d4601b3dc9228f086bc071	2	no	Pass criteria for one project / Workday, capacity, and cleanup
189	776	a07716b1dea1d92f60e010366f4c9330d7543e1efd8c062af74ebcc3849c572d	2	no	Pass criteria for one project / Workday, capacity, and cleanup
190	777	349dabbf1022028ef2b7ec696036113837b636df4f164670f3c616b8a563d469	2	no	Pass criteria for one project / Workday, capacity, and cleanup
191	778	5634f9dcc95a38980f550bb87d3909c6ca3763509e3dd60ac946aaa0684098a7	2	no	Pass criteria for one project / Workday, capacity, and cleanup
192	779	3bf7f808c3baf5cc63fc5e8e8c065bc2cd87dea9e2df9aae4d1924565af6acd8	2	yes	Pass criteria for one project / Workday, capacity, and cleanup
193	780	c9023f97264910d1f1dd874dc89bec5402ec3aa39e86de4a3d19226f99471b8e	4	no	Pass criteria for one project / Workday, capacity, and cleanup
194	781	c0e45d2f867548b2d464dbda222e69f790b3af358c99a26fd899071024826adc	2	no	Pass criteria for one project / Workday, capacity, and cleanup
195	785	6c6e922d724fe9bf966e3f11456af2f176224cdff4792c9b7a73ce8047659e55	2	no	Pass criteria for one project / Clean architecture
196	786	a5094a4183f15fd851aaad5815d5f29a769c74781a5a145bd29bed10924dec20	2	no	Pass criteria for one project / Clean architecture
197	787	17b1ee84abc83b01bbd4e9279cb6aa364eebdf5b91cc0f4f877525b3a78408bd	2	no	Pass criteria for one project / Clean architecture
198	791	fcadf4b131012b7b83611df6eb6a1b56e107def698a04d759a191b85a022cabe	3	no	Failure classification and retry instruction
199	793	982816a8f5a3408297f35b8fa368c6c95389e1a29c93d54678a7584e284857bf	3	no	Failure classification and retry instruction
200	794	2a76c159c651ebd20f775f1793f1e86204b8fb26b1bca8e26cfb8d0ffdfcdfeb	3	no	Failure classification and retry instruction
201	795	b77726324e13ae28ced3183dede856d7b1656156b0ed52ab24fb5f3bc87f7186	3	no	Failure classification and retry instruction
202	797	7d48490c6689efd570c3e337f2320efde901d6469b8618f3f126d6ecdc3eec64	3	no	Failure classification and retry instruction
203	799	6d60760e803393ac8b34ab27a04de70ca629758febb90080fdeb1dca9d39b16a	3	no	Failure classification and retry instruction
204	810	1eea39987a60f616fd68b7a552cc6f5d25a0257eef54f08e22890a49ea2ae9f1	3	no	Failure classification and retry instruction

Installed execution repair in progress — 2026-10-09

PR treeseed-ai/reviewer#106 holds candidate 354e5710bbc25569b559a35b767fb54f352df9ea (regressions 65959f9, 7ac8fe5; implementation follows both). Source candidate/full-suite authority remains independent of installed execution; the executing Reviewer joins explicit participating owners. Actual native npm archive inventory and production-installed bytes/modes must match, with archives retained beside isolated node_modules. No source fallback, installed symlinks, missing helpers, extras or mutation are accepted. Existing run bundles retain SHA256/byte custody.
Behavior mapping: argument validation → guarantee-command unit; archive/member/byte/mode validation → installed-custody unit; missing custody/source-fallback denial, explicit Reviewer+owner whole suites without browser traversal, actual production-installed Reviewer binary/loader and failed-source/helper readback → installed-custody native integration. All five cases are selected by the existing prerequisite scene.
Commands on exact candidate: PATH=/tmp/sdk-native-node2412-PjB5qe/bin:/tmp/reviewer-native-elixir-tools-6AsRzR:$PATH npm run verify passed 183/183 in 29 files with typecheck/build/architecture checks; then node dist/verifiers/guarantees/command.js --workspace . --ids guarantee.reviewer.acceptance.prerequisites --run-id reviewer98-installed-custody-20261009 --environment local ran fresh 183/183 before 96 passing scene steps. Existing bundle .treeseed/guarantees/runs/reviewer98-installed-custody-20261009; stdout report SHA256 70c0404d6e43db4804358e709a100b6d1d3a1adf2520ce746aefd1ab1aba9101. Actions https://github.com/treeseed-ai/reviewer/actions/runs/37994819128 is pending on proposed merge 6e90b98a2af98f5b92311df9ddb40dcc40d16dc3.
Preserved failures: unsupported option RED; missing custody incorrectly ran source scene RED; initial native fixture hook timeout (moved installation into its owning existing-budget test); first full verify lacked retained Elixir PATH and failed. None counts as a pass. Actual six-owner installed SDK execution and owner packaging gaps, TreeDX reporting and all managed acceptance remain unproven. No SDK campaign launched.

Native root owner execution repair — 2026-10-09

Reviewer PR #107, held head 95761635d223a6c7d066f1ee0899cd31d865bae7, repairs root guarantee discovery beside companion packages and resolves a non-npm owner's existing declared package identity. Regression 6944c9b preceded implementation; native/NPM collisions, omitted identities and unrelated companions remain denied/excluded. The original real ExUnit shell integration proves failure retention and fresh retry through this native-root boundary. Node 24.12.0 npm run verify passed 184/184 assertions, then the original prerequisite guarantee freshly reran all 184 before 97 scene steps; zero failures/skips/todos. Local report SHA256 46c50b96746fc700492d4ae090e132f3e2e189f419717fb95272c28170ef1940. Actions 38003370349 is pending on tested merge 4cce6a868ed4fcde708c6438cf246c22d980a603. This is prerequisite execution support only; no SDK binding or managed pass is claimed.

Reviewer #107 delivery read-back: ordinary staging merge ea4ca6e016fa0ff53f5a3307df0ad3c4344263b8, tree 99c55b23355b0f83f8d373b8a08d4a0df28ad001, equals tested merge 4cce6a868ed4fcde708c6438cf246c22d980a603 exactly. Actions 38003370349 passed complete 184 assertions and fresh 184 before 97 scene steps; sourceDigest 7225910fc6d6cca6195942c703fdc2140dfae18ad31112afd7143865cab044c8; scene artifact 11650655839 ZIP df24c44df31f0e21fd60d85387051da1dac966a8e32ad3b64eece6d01dc05bcc, report 034478bb24f13f781bf3ad10073b79c4aaa2e63529ad873578f00ff37766419f; archive artifact 11650476145 ZIP ad06ad6fe654546c7a1baad39fbf29bf3829f1674ea534752c22ff6749867587. Primary checkout fast-forwarded clean staging; only this delivery's temporary remote branch deleted. No main promotion, package publication, runtime activation or SDK campaign occurred. Strict SDK counts remain 204 selected / 25 bound / 179 unbound / 260 deferred.

Native reporting failure retained and scoped repair — 2026-10-09

TreeDX PR #91 Actions 38003926328, tested merge ea496f749de5f2edc285315b13e7b4601330df56, failed complete prerequisites before every scene: the observer traced unrelated native file writes and expanded traces to 3.28GB/7.90GB. Independent SDK-language jobs and all focused reporter contracts passed, but the run remains failed. Original native stdout, failure and termination are retained in amd64 artifact 11650786260 ZIP e3e9f0cebca9a89bf07144591bbff84810634186a708c5f1b17e58d9d56cfac9, report 12b5aa20f643cf9bcf3052d20c62fd35ddb36ae4bd4cc688cd0595378d7edc3b, and arm64 11651005343 ZIP 580556a18f265036cb0ed119114c88bd6640b13b6cc18695642377dd5ddae781, report 88251de22a07ee296b5b45ef776ffb06cdb853a06ba5ee79421a3cbb46d9ee08. Focused regression e895e3f failed before repair 700bb170ac2d61943455a1c7d1b57269f913f9a1; the same native subprocess then passed with complete stdout timing writes and no unrelated file-data trace. Existing assertion, report and watchdog limits are unchanged. Actions 38004568399 is the current candidate; redundant push run 38004564076 was cancelled after its PR run started.

API installed asset closure candidate — 2026-10-09

Held detached source candidate a909054d54325f1f261d21b6111b25b94a956632 starts from freshly fetched staging 789a94e99cb18bea28017af4463f1fcea5695418; main remains 93563a71831659860bfd04fc4e366bae73b9c384. Regression f12df2fa reproduced omitted package metadata/definitions/native acceptance asset and all three private-source imports. The repair ships the existing guarantee definitions and single native acceptance file and imports the already published compiled runtime modules; no API product model, public export, permission or behavior was added. Native actual API+held SDK archives, production-only install with scripts disabled, sole SDK archive custody, installed-byte read-back, actual runtime configuration validation and absent encryption-custody denial passed 2/2 focused assertions. Source architecture and complete distribution build passed. The initial fixture incorrectly prohibited SDK's declared production TypeScript dependency and omitted the actual API archive from its consumer dependency manifest; those failed observations remain retained, corrected in ac8ff75b/0ce5cb25 while preserving denial of development-only Vitest/tsx and strict npm production-tree validity. The original component scene now selects these two exact existing test boundaries. Full native PostgreSQL/TreeDX prerequisites, full API suite, coded scene and actual installed Reviewer execution remain unproven on this candidate; no API acceptance run or PR was launched. Producer completeness work remains pending and will be batched before expensive native CI. SDK product code and all strict binding counts remain unchanged.

Implementation checkpoint — native resumed writes (2026-10-09): TreeDX #91 candidate 700bb170ac2d61943455a1c7d1b57269f913f9a1, tested merge 659d85fdc85bf73afd94d2f7fb6052970ba68432, failed amd64 and Fast PR Gate in Actions 38004568399. Complete paired strace unfinished/resumed Cargo build-script records were incorrectly rejected as incomplete; no amd64 scene launched. Failed amd64 report SHA256 95d5f2d4cbfca0e9d211a7071797c45c7dc7d79779cf9fc625582b37ac083324, artifact 11650966210 ZIP SHA256 dc2cffae44d18701b8016b8b206d00586f2a6e68dd25713130791a04ccbb00b2, remain failed. The same invocation's arm64 report independently passed all 539 native assertions before MVP smoke, report SHA256 6ffe91435f23ec087a06f7de8757fb41183a2b1bfbe92fa09edfde38a204d8f8, artifact 11651246079 ZIP SHA256 78b6524bb0bae877eaaaa36a88e6152f6aa57fee31dbce189f0c1b8fe94acd3b; optional federation was not configured and remains unproven. This does not make the overall invocation pass.

Focused regression commit 2e431c1 reproduces the parser failure and a real blocked native stdout syscall with concurrent output. Repair 26f2d4780132e7afda06697d87599de1aee5da00 reconciles exact PID, original timestamp, byte count and matching resume; missing/orphan/duplicate/conflicting halves, concurrent writes from one PID, reversed clocks and truncated streams still fail. Existing native suite and MVP discovery include both tests, no parallel wrapper. Local Node 24.12 focused parser/native regression passes; all 19 locally available reporting cases, strict TS and source architecture checks pass. Rust/ExUnit full native prerequisites require fresh CI on this candidate; historical reports are unchanged and cannot satisfy fresh invocation prerequisites. No timing, assertion, deadline, allowance or report-size limit was weakened. SDK gate remains 204 selected /25 bound /179 unbound /260 deferred; no managed workday.

TreeDX #91 native reporting verification complete, merge held by required head check (2026-10-09): source 26f2d4780132e7afda06697d87599de1aee5da00, tested merge 7bb2919188bfdf47b281d4eec81dfd9230181274, tree 1d286c0b3d942d21ae91b1ec89abbbc33d5a4aaa. PR Actions 38005408821 passed all 13 applicable jobs. Both architectures freshly passed 541/541 original complete native assertions (zero failed/skipped/todo, all per-assertion timing present) before MVP smoke. amd64 artifact 11651307759 ZIP SHA256 54b76b8fcf925eb6447d28b5c1173be0cbfcf4daf60ccab8697e7e88d5bbbf0c, report 5eb6113a274a497acc4e261bed8fc8c7b5dab779e2786a1cc6a3d77ef59c30f9; arm64 11651670774 ZIP a53daa1f20a0c8b3590004a355984ece46d7e6d6f9319ec3c6a8c6ff1fef9749, report d754e465f4c6b352356bac5a4cf5c2640b622282b70de148cceeec01ad1093ff. Original failed reports remain unchanged. Optional external federation remains unproven, not a pass.

Ordinary merge was correctly rejected (HTTP 405): cancelled duplicate push invocation left the source head's required Fast PR Gate cancelled, while PR merge-candidate checks passed. Fresh protected readback now exposes strict Fast PR Gate/app 15368, enforced for admins, zero human review approvals. No protection is bypassed or changed. Only cancelled head job 114072926165 in 38005405521 was requested for rerun; no complete native or acceptance campaign rerun. Staging/main remain held 367fec4237c6928969c969c05217bdb9832b41ac/1a3a456dc4f2b0beb68d7e212f2a64c82c80cd4b pending that exact required result. This supersedes earlier unavailable required-status configuration observations.

Current native inventory and installed-assets candidate — 2026-10-09

Held detached candidate 986a39d79cb3a83edbc1cdf744e28fa01dd5465b adds no API product model or runtime repair. Existing native PostgreSQL admission/settlement case now races independent connection pools and checks the exact winning graph node, immutable attempt and single reservation; public assignment/reservation/usage/ledger inventories reconcile against all owning SQL rows. Injected native ledger failure still rolls back completely; concurrent exact retry settles once, changed usage remains denied, original failed observation and issued authority survive. Existing original-DDL PGlite event-service integration reconciles all 51 actual stored events across its ascending pages; it is not presented as native PostgreSQL concurrency.

New minimum acceptance assertion tests/acceptance/execution-inventory.ts is necessary to share independent SQL-completeness proof among three unit cases, existing native integrations and the existing managed clean-schema verifier without duplicating policy or exceeding its file limit. Exact native IDs/creation clocks bound every public page and cursor, including genuine empty inventories. Missing/foreign/duplicate/reordered/truncated/malformed pages, premature termination, incorrect cursor, permission denial, cancellation and interruption fail without repairing observations. Managed clean-schema now reconciles all scoped assignments/events/usage/settlements through supported CLI reads and independently rereads owning native rows after completion. It resolves CLI through the actual installed package's public bin.trsd metadata, replacing both checkout CLI fallbacks. Actual managed execution and six-owner installed CLI custody remain unproven until the integrated readiness gates pass.

Archive closure still uses actual API plus held SDK archives, production dependencies only, scripts disabled, exact installed bytes and strict npm dependency tree. Both selected acceptance assets now ship. Behavior mapping: native inventory positive/negative/authority units → three existing component-scene refs; independent native PostgreSQL admission/accounting and original SQL event service → their existing native refs; complete actual managed readback → existing execution-schema.ts case. Five new component steps total (two packaging + three inventory); no new managed binding is claimed.

Regression-first history: a6860864 missing executable inventory proof, e9b06055 ascending event order, 86a6b93c checkout CLI fallback precede owning repair 986a39d7. Original packaging failures and a test-oracle failure comparing internal SQL ledger shape with public camel-case output remain retained; e1866119 checks the entire exact public shape against original measurements and durable canonical settlement instead. No product defect is inferred from that fixture mistake. Final focused command ran all four affected test files with Node 24.12.0 and disposable pinned PostgreSQL 17.11: 8/8 assertions, zero failed/skipped/todo, report SHA256 fa21c9cffdcb93ba1665ec21f34203e75079b67dece659cd2a6a7fda47cfd5c6. Strict acceptance TypeScript including unchecked-index checks, source architecture and owning strict declaration build passed. Disposable database readback showed zero retained test databases before only the exact owned container was removed; unrelated running resources retained.

Full API native prerequisites, complete suite, Actions and coded scenes remain pending on this exact candidate. Producer emission of every required runtime transition, complete actual leases/results and managed golden outcomes remain unresolved; matching inventories alone do not claim those semantics. No live SDK campaign, runtime activation, SDK product fix, tag or publication occurred. SDK counts remain 204 selected /25 bound /179 unbound /260 deferred. Current contract: #387.

TreeDX #91 staging delivery read-back — 2026-10-09: ordinary merge 0886de0b28b9c65abbd9cfe8c45013f4a09cd338 has tree 1d286c0b3d942d21ae91b1ec89abbbc33d5a4aaa, independently identical to tested merge 7bb2919188bfdf47b281d4eec81dfd9230181274 from passing PR Actions 38005408821 (both fresh 541/541 native suites before MVP). Required source-head Fast PR Gate job 114076546368 passed in the targeted rerun of 38005405521; that invocation's unrelated cancelled jobs remain cancelled and no whole passing invocation is claimed for it. The merge succeeded through ordinary protected GitHub merge after fresh protected-head verification; no checks/reviews/admin enforcement changed. Primary checkout safely fast-forwarded clean staging; exact source head is an ancestor, and only this delivery's temporary remote branch was deleted with an exact-ref lease and independently confirmed absent. Main remains 1a3a456dc4f2b0beb68d7e212f2a64c82c80cd4b. No tag, release, publication, runtime selection or managed SDK campaign. TreeDX prerequisite reporting repair is delivered at component scope; external federation, full installed multi-owner SDK execution, 179 unbound selected criteria and managed outcomes remain unproven.

CLI archive/public observation candidate — 2026-10-10 UTC

Base 63c7928b2ab2456e495a0e55572b9a47d379315c; focused regression-first commit 2f0d5a2 reproduces four missing installed assets, native archive ENOENT, and checkout source command execution. Repair 5a73cd434a42f237543d30c8b8c7bd5e912ab173 moves the two original native event/diagnostic cases intact to tests/acceptance/workday-events.test.ts, selects only the declared compiled public binary, removes speculative unbound command fallback, and ships existing metadata/guarantees/minimum asset closure. The existing synthetic credential fixture is now TypeScript; original complete-suite/CI references and exact registry paths changed together. It remains explicitly synthetic component evidence, not genuine systemd/model/API authorization proof.

Behavior mapping: archive inclusion/private-source denial/source-command denial → tests/contract/package/installed-assets.test.ts unit cases; actual CLI+held SDK+Identity archives installed with --omit=dev --ignore-scripts --package-lock=false --no-save, strict production dependency tree/exact bytes/archive integrities/public binary native subprocess → same file native integration; original real HTTP event/diagnostic cases → moved acceptance file; coded guarantee.cli.golden.component-boundaries retains both existing IDs and adds cli.golden.installed-assets-unit, .installed-assets-native, .installed-event-command. No duplicate native implementation or new runtime dependency.

Focused native command PATH=/tmp/sdk-native-node2412-PjB5qe/bin:$PATH node --import tsx --import ./tests/support/os-custody.ts --test tests/contract/package/installed-assets.test.ts tests/acceptance/workday-events.test.ts tests/unit/command-boundary/observation/workday-events.test.ts tests/unit/native-suite-reporting.test.ts tests/integration/native-suite-reporting.test.ts tests/contract/package/thin-package.test.ts passed 22/22 with zero failed/skipped/todo; original negative fixture outcomes remain independently asserted. Logs: /tmp/cli274-installed-assets-red-20261010.log, /tmp/cli274-source-command-red-20261010.log, /tmp/cli274-installed-assets-focused-green-20261010.log. Strict TS tsc --strict --noEmit --target ES2022 --module ESNext --moduleResolution Bundler --allowImportingTsExtensions --esModuleInterop --types node tests/acceptance/workday-events.test.ts tests/support/os-custody.ts tests/contract/package/installed-assets.test.ts passed, as did original file-length/architecture checks. No type/deadline/report checks relaxed.

Local npm run verify:direct stopped before any complete suite or scene at the existing strict SBOM gate: ESBOMPROBLEMS, missing development dependencies in the retained local dependency tree (first @adobe/css-tools/@arethetypeswrong/cli etc.). Original failure log retained /tmp/cli274-installed-assets-verify-direct-20261010.log; no claim of release verification. Source-only complete npm test on held repair candidate is running; independent clean Actions installation/release verification and fresh pre-scene complete suites remain required. Actual selected installed assets executing under the joined six-owner production archive environment and genuine managed CLI custody remain unproven. SDK strict gate remains 464/204/25/179/260; no managed campaign or runtime activation.

API #529 failed exact candidate retained — 2026-10-10 UTC

Actions https://github.com/treeseed-ai/api/actions/runs/38006819171, Verify job 114077393400, tested merge ebe45f650a2323da4dba6b7ea8250f6cd0cc465a, source head 986a39d79cb3a83edbc1cdf744e28fa01dd5465b: 374 files, 2016 passed / 1 failed / 2017 total; new native archive test exceeded the unchanged 30-second test deadline (32.751 seconds observed), so no component or managed scenes began. Its late installedRuntimeContracts:passed console line is not a passing test or receipt. Original full log /tmp/api529-verify-38006819171.log and artifact 11651524784 (native-prerequisite-evidence-ebe45f650a2323da4dba6b7ea8250f6cd0cc465a) retained. Existing native PostgreSQL producer, public cursor and asset assertions otherwise passed; these totals cannot certify acceptance. Add actual command stage/timing observations and reproduce with cheap focused cold-cache execution before any replacement full invocation. Do not increase the deadline or fabricate a retrospective timing diagnosis. Complete native prerequisite suites must be repeated before any future scene invocation on its exact replacement candidate.

CLI #294 delivered to staging — 2026-10-10 UTC

treeseed-ai/cli#294 ordinary merged as 22b6a27136a3583f4128cfd763917371e5572985. Fresh protected-head fetch, source ancestry and post-merge tree read-back verified tree 837b887bc913a554513f43e48df0eb437815b138 equals tested merge 8d0919a04c66e911e27a6521519f6c4381fda7c5; source head 5a73cd434a42f237543d30c8b8c7bd5e912ab173 retained. Actions https://github.com/treeseed-ai/cli/actions/runs/38007844944 passed 369 complete tests, then a fresh complete 369/369 prerequisite invocation with zero failures/skips/todos before all 168 component scene steps. Prerequisite source digest 723a1ba4a6c99bc3c116e9ed18aa5fd01b94f8cc82d4eb2c113364fb00335c08; report SHA256 60ff6ae6765c91999f808d73eaa1731880859e722f7dc8ca5173e45321f05865. Scene artifact 11652440908 ZIP SHA256 686ce582aa857b70aabb920c140077cb3e9f658018210c009c1e0b30b42fe3b9; package artifact 11651976465 ZIP SHA256 1f977558be3b4d7bf0a8d8f8eb0a71abea88daca1541b1143720edb406dd9dbf; read-back /tmp/cli294-ci-38007844944. Existing component reporting is not strict managed SDK prerequisite/acceptance proof. Local SBOM environment failure retained; clean Actions release verification passed without weakening it. Primary checkout safely fast-forwarded, clean staging; only this delivery's exact remote branch was deleted and absence verified; main d0d871ef166406bc479358204d4e59babe54767a unchanged. Joined actual six-owner installed execution, genuine host credential/model custody and SDK golden remain unproven; gate still 464 full/204 selected/25 bound/179 unbound/260 deferred. No releases, tags, runtime selection or campaign.

API replacement candidate after retained prerequisite failure — 2026-10-10 UTC

PR treeseed-ai/api#529 replacement source 3885ae9d496657516ee6fb0eeb07a564272fba84 retains ordinary lineage and original 38006819171 failure. No API product/schema behavior changed in this replacement. Regression efef542e reproduces ignored native cancellation (child/grandchild continued and the promise resolved after abort); 229f93d3 adds bounded process-group interruption and exact observed command stages. Regression b1d4bde0 reproduces split UTF8 corruption; 3885ae9d preserves decoded bytes/literal argv, original nonzero/ENOENT failures, pre-launch cancellation, and scoped cleanup before the final proof observation. Existing 30-second test deadline and original output bound remain; five seconds explicitly reserved for closeout. All original byte/dependency/integrity assertions retained; Buffer.equals compares exact bytes natively instead of slow JS deep traversal. Both actual archives are produced in one supported npm pack invocation, and npm may reuse valid cached dependencies while still fetching cache misses. Scoped native deletion was independently observed at ~0.1 seconds versus several seconds of synchronous fixture cleanup; no original CI timeout root cause is retroactively asserted.

Fresh focused cold-cache checks on the final replacement: 10/10 passed, zero failures/skips/todos, including independent native PostgreSQL producer/concurrent admission, all public-page negatives, owning workday event integration, actual production archive installation/public runtime contracts, interrupted descendants and UTF8/literal/nonzero/unavailable boundaries. Original native archive proof completed in 23.721 seconds, including cleanup, inside the unchanged deadline. Exact command: TREESEED_TEST_POSTGRES_URL=postgres://postgres:migration-test-only@127.0.0.1:32777/postgres TREESEED_DEVELOPMENT_WORKSPACE_ROOT=/tmp/sdk369-platform-authority-de2LzF node node_modules/vitest/vitest.mjs run --config vitest.control-plane.config.ts tests/unit/control-plane/capacity/execution/admission/postgres.test.ts tests/unit/control-plane/capacity/execution/architecture/native-inventory.test.ts tests/unit/control-plane/capacity/execution/graph/architecture/workday-observation-persistence.test.ts tests/unit/control-plane/release/installed-assets.test.ts --reporter=json --outputFile=/tmp/api515-producer-assets-replacement-final-focused-20261010.json, Node 24.12.0, isolated empty npm cache. JSON SHA256 3202a7b08f417d2f07b32e0961a6dbbb18a2380b66846e0c7959d2672b78bd1d; log /tmp/api515-producer-assets-replacement-final-focused-20261010.log. Strict TypeScript passed for assets/new tests; original file policies passed. Native PostgreSQL fixture cf074fdde6cdace56ef18054ead739ca344516dfd7514d93f7786f7f4fc001cb (pinned PostgreSQL 17.11) retained no test databases and only that owned container was removed, independently absent. New native helper cases are explicitly wired into the existing component guarantee; expected full count 2019 and component steps 830 are not receipts. Fresh full Actions and fresh complete suites before any scene still required; no source/installed managed campaign started.

API PR-body custody correction (2026-10-10 UTC): successful validate results previously mentioned belonged to a separate check; they did not clear the durable PR-template validator. Retained failed submission runs 38006819477 and 38009231106 exposed missing required headings/authority/checklist fields. No merge occurred. API #529 now contains the complete required template with all eight exact headings, full base/head commits and explicit pending full-verification state; independent gh pr view read-back /tmp/api529-required-template-readback-20261010.md confirms actual newlines/headings. Replacement source 3885ae9d496657516ee6fb0eeb07a564272fba84 is running in Actions https://github.com/treeseed-ai/api/actions/runs/38009232971; metadata validation and full native result still require confirmation. This corrects the earlier submission-status interpretation without relabeling any failed job.

Deployment installed acceptance asset closure — implementation started 2026-10-10

Held fresh protected staging a0ccbbf6f6644ef754336a7dd162616e99157b78 (main 88c5971910298c43617f1a7c760990ab6146aff6); clean primary checkout exclusively owned. Focused regression first: current archive omits metadata/selected definitions and managed assets; assets import private source and choose checkout CLI. Repair will ship the minimum existing selected asset closure, expose identical required owning functions through the current package root, and resolve the installed CLI's declared binary. Preserve existing completed/failed source-publication and warm-pool cases and deadlines; no managed invocation or runtime mutation. Unit, actual production archive/native public-root integration, and existing component-scene bindings required before delivery. Joined six-owner installed execution and normal SDK physical-absence consumption remain separate unproven gates.

Deployment installed acceptance asset candidate — 2026-10-10

Regression 515a6c46 reproduced two failures (omitted selected assets and missing identical public-root authorities) on held staging a0ccbbf6f6644ef754336a7dd162616e99157b78. Repair candidate fd85db7852ccf500c3462f3fc2adaec1afb9fdc7 ships the existing source-runtime definitions, source-publication guarantee/scene, metadata and minimum three TypeScript assets; those assets consume identical owning functions via the existing public root and the installed CLI's declared binary. Existing completed/failed/warm cases and original deadlines are retained. No managed run or runtime selection.

Unit/native-public mapping: tests/installed-acceptance-assets.test.ts four exact cases bound as deployment.golden.installed-assets-unit, .installed-runtime-authority-unit, .installed-cli-custody-unit, .installed-assets-native in the original component registry/scene. Actual Deployment + held SDK + Identity archives installed with production dependencies, scripts disabled, exact bytes/integrities, strict npm tree, no checkout source or development tsx/Vitest; independent native consumer performs private immutable materialization, receipt read-back and original duplicate/unsafe-input denial. CLI resolution fixture is unit evidence only; actual joined current six-owner CLI/Reviewer loader execution remains unproven.

Commands on Node 24.12.0: npm run build strict compiler passed; npm run check:source-shape passed; focused node node_modules/vitest/vitest.mjs run tests/installed-acceptance-assets.test.ts tests/development-runtime-public.test.ts tests/development-runtime-copy.test.ts tests/source-git-cache.test.ts --reporter=json --outputFile=/tmp/deployment834-installed-assets-unprivileged-focused-20261010.json: 28/28, zero failures/skips/todos, report SHA256 867d497681fa7a5b812c67d0e99c3dbc7dd757490cf227a5f2fa90f7288f036f. Broader five-file focused run retains 34 pass / 1 fail / 35: original native Kata warm case lacked disposable host namespace authority in this shell; report /tmp/deployment834-installed-assets-focused-final-20261010.json, SHA256 a8754bb4b59595030b87aca399570b89a2bbbdbe6aeea1ba224c86adcf42e2c7. No local scene launched. Full native CI plus fresh complete prerequisites before the existing component scene are required; no passing full delivery claim yet.

Retained API replacement prerequisite failure — 2026-10-10

Actions https://github.com/treeseed-ai/api/actions/runs/38009232971 failed on source 3885ae9d496657516ee6fb0eeb07a564272fba84, merge candidate 2a9f5eb70bbaaab970439122ce83590350fafe78: 374 files / 2018 passed / 1 failed / 2019 total, no skipped/todo; no scenes ran. Actual stages: pack SDK+API 3827.682ms, then production npm install still running when the unchanged fixture's 25-second work boundary sent SIGKILL after 21217.609ms installation; scoped cleanup succeeded in 5.337ms. Original 30-second deadline and five-second closeout reserve remain unchanged. Artifact 11652369023, ZIP SHA256 ce27849db063fa115c175388aa67dd6bac483c7fa9010be13c4855bf81bdf3cd, local read-back /tmp/api529-failed-ci-38009232971; detailed native job log /tmp/api529-replacement-verify-38009232971.log.

A cold-cache focused probe using supported shallow installation passed 4/4 but measured 19.043s install, comparable to the earlier hoisted 18.889s; this does not establish an optimization or CI root cause and is not adopted. Inspecting the owning package test found duplicate native API packing: its first case inventories with a dry run and the second produces the same candidate archive again. Next bounded regression will require production integration to reuse an unchanged actual archive produced by the immediately preceding owning packaging check, when present in the same process/invocation; standalone selected execution still produces its own fresh actual archives. This removes duplicate packaging work without extending a deadline, skipping a dependency, copying checkout dependencies, reusing a previous invocation receipt or changing production npm validation. No further full CI activation until focused evidence proves the replacement.

Deployment #867: fresh prerequisite failure retained; safe diagnostics replacement — 2026-10-10

https://github.com/treeseed-ai/deployment/actions/runs/38010360937 on fd85db7852ccf500c3462f3fc2adaec1afb9fdc7, merge cc0f2844cf2732326b78fff9ccafdc710aa10c33: original strict build/source shape/OpenTofu plus all 1307/1307 tests in 196 files passed. The required fresh complete suite then retained 1306 passed / 1 failed / 1307, zero skipped/todo; the existing native installed CLI→manager→supervisor host-inspection case failed. Zero component scenes executed. SourceDigest b6d6eecf82d26fb3df25bdd9e707684a01f64a6a6600436c95ff4462a744a534; artifact 11653435035, ZIP SHA256 c37e93961475619f51b319d4445ab501b056179cedd7d802c365dabbb848bb0b, report read-back /tmp/deployment867-failed-ci-38010360937. Independent uninstall and secret-custody jobs passed only their scopes.

The existing pinned Reviewer intentionally suppresses native failure prose; this failed receipt has a title and no safe cause/phase. Do not retroactively diagnose it as a timeout, concurrency issue, assertion mismatch or repaired physical behavior. Regression 1ee8fc60 runs the actual native host-inspection test in a denied disposable-host context and reproduces omission of its exact safe phase before resource startup. Diagnostic repair 69a2ecf1 records constant phase identifiers through the existing Vitest failure hook, preserves original failures and cleanup, and adds an early focused native reproduction to the existing Verify job before full suites. Original 1000ms commands and five-second test watchdog are unchanged. Exact case bound as deployment.golden.host-inspection-failure-phase-native in the existing component registry/scene. Focused red/green each select one assertion and leave 14 unselected cases; they are additional checks, never full prerequisites. Strict npm run build and source-shape pass. Native replacement CI still must prove the complete suite, fresh full prerequisites and all component steps. No physical fix or SDK golden pass claimed.

API #529 replacement archive reuse candidate — 2026-10-10

Regression e585280f failed 1/4 focused assertions because the preceding package check did not retain an actual same-invocation API archive. Repair 6f48e9608a8ba36761b2910474f1fb92ad2cf1ad upgrades that existing dry-run check to real packaging and reuses only its unchanged actual archive in the immediately following production integration case. Standalone native selection still creates fresh actual SDK and API archives. No archive, source dependencies or prerequisite receipt is reused across processes or invocations. Exact integrity, installed bytes, strict production npm tree, native public-module behavior, no development dependency/source fallback and durable scoped cleanup remain required. Original 30-second tests and 25-second work/five-second closeout split remain unchanged; the packaging check itself now also has the bounded interruption signal.

Cold empty-cache 4/4 focused check passed, zero failures/skips/todos, report SHA256 3824610581648236ac64535dbc72f68da415408cf283b4686c503a8c58b3c8fc: actual first API pack 2289.139ms, subsequent SDK pack 661.037ms, production installation 20558.120ms; original duplicate API pack removed from the integration interval. Final four-file owning focused run with native PostgreSQL 17.11 and pinned Node 24.12/Platform authority passed 10/10, zero failures/skips/todos, report /tmp/api515-producer-assets-reuse-final-focused-20261010.json, SHA256 0607e4226bac76b072410c9a936713e3132b023f7433c72f9e7e33847c696197, native archive interval 9660.782ms. Additional standalone native selection passed 1 case / 3 unselected cases in 11.49s; that filtered probe is not full prerequisites. Strict new-source TypeScript passed. Owned PostgreSQL fixture e7f4b57c3355213eccdafa202656602db30e869e2d6f25e00a584bbb81eac3ba had zero remaining test databases and was removed/absence verified; unrelated containers retained. Full native replacement Actions remains required before merge or any scene; previous two timeout/interruption failures stay failed.

Deployment archive closure #867 — final exact candidate evidence

Final replacement verification (2026-10-10): Actions 38011884094 passed all three exact-head jobs on source 69a2ecf1f2c67cf3f564a7711d3e36d3af886219, tested merge 6bac520f95c798071953b4420fe433ab2a2ec1cf, tree f6f7248180193b9a5a54734ebcd83e52040dac6d. Node 24.12.0 original full suite: 1,308/1,308 across 196 files; freshly repeated complete prerequisite suite: 1,308/1,308, zero failed/skipped/todo, then 230/230 component scene steps. Source digest da0633dc81dc72ba765cab7cd97f7ab3fec71663e71d9e4154d93d63bebc941b. Scene artifact 11655680116 ZIP SHA256 6ab140e16fcb0f4e9a94c285d9c0aceceb64cca007522b0a3c432c5dbe0871ed; candidate artifact 11655390334 ZIP SHA256 9365f7f62b2cc538db40f24b3c404c185063e1236433e2e1c35434288ca47d2e; report SHA256 649a4a0f7f460e3ff57248d215ddfebf85c150b9f4ade4d74d7c0d34cd6a21fe. Independent uninstall and secret-custody jobs passed. Previous failed run 38010360937 and its original failure remain historical evidence; its root cause was not retrospectively inferred. These are component and package-custody receipts, not all-six-owner installed SDK execution, a managed golden workday, or complete physical closure beyond the existing inspected sandbox root.

API #529 third candidate — acceptance remains blocked

Actions 38011997784 failed on source 6f48e9608a8ba36761b2910474f1fb92ad2cf1ad, tested merge 0d156fe83717deb064b99feadad26d844eaf70aa: 2,018 passed / 1 failed / 2,019 tests across 374 files; zero skipped/todo; zero scenes executed. The actual production archive install again reached the original 25-second work cancellation inside its unchanged 30-second test, retaining scoped child termination and teardown. Artifact 11655541876 ZIP SHA256 8abca30ae38eb5675bd8fc09d3850f9dad7a50b70e51f7745c1be5ac1dc58c8c. Prior failures 38006819171 and 38009232971 remain historical. The cold-cache focused pass does not substitute for this failed exact-candidate complete suite. No fourth full candidate campaign is authorized by partial evidence: obtain a cheap native reproduction and concrete installer diagnosis before another full run; no deadline, allowance, assertion, dependency-tree or acceptance reduction.

Resource cleanup — 2026-10-10

At the operator's request, stopped the interrupted local Reviewer test processes and the temporary treedx86-prerequisite-init-ZDKdtv, capacity-treedx-native-IZauDr, and capacity-agent-tests-4b46a638-1d88-4c4f-a28b-af9bf89de622 verification containers. Removed 819 disposable native test fixture directories, owned cold npm caches, and derived Rust target outputs. Preserved commits, all registered worktrees, raw failure logs, retained Actions artifacts, native source/toolchains, protected observations, keys and managed development resources. /tmp is RAM-backed: usage fell from about 30 GiB to 19 GiB; available memory rose from 38,286 MiB to 45,357 MiB and swap usage fell from 8,006 MiB to 2,438 MiB. No owned Reviewer test processes remain. Existing managed TreeDX remains running and independently consumes about 46.5 GiB. Interrupted local checks are not passing evidence. The source-runner custody repair and independent fixture migration remain uncommitted work after focused RED commits 0817329bd882ed9b104947937e673a6a869390ae and f6336d9; no subsequent scene, full API retry, runtime activation or campaign was launched.

RAM cleanup, checked TreeDX cache activation and remaining hard-cap custody — 2026-10-10

Operator confirmed the existing 4 GiB limit. TreeDX PR #92 ordinarily merged to staging 3336c7ba4be2b24fb404a8f25db065f4164ee312, tree 77328626600da06bfb03b60b4eaea776b27c8999, identical to tested merge 09797258ecc360a1fe82d1e16fe953ab8ab5efd6. Actions 38016417903 passed all 13 applicable jobs, both fresh complete native suites 548/548 zero failed/skipped/todo before MVP. Both architectures' original job logs prove actual 4 GiB cgroup limits and bounded cache gauges before/after MVP. Native report SHA256s: amd64 1d96f9110d58a671535688c03bfe482a25d18bb1baef90156974db49179a202b; arm64 df1d481777e04dc084090e5b22da8f98599686c1e1022ed6bfb03bc3defa3d8c. Only this delivery's temporary remote branch was deleted after protected ancestry/tree read-back.

Supported trsd dev rebuild treedx.service --session dev-5007e344-493 --json succeeded on the existing candidate selection (generation 1126), actual image sha256:984a14f66aae7e2b8b9c5941493342ef5982f582a944f0d7e5eb76d0dd9ccbe7, healthy start 2026-10-10T02:32:26.210602637Z. Docker usage fell from 46.48 GiB to about 223 MiB; public metrics report runtime budget 4,294,967,296 bytes, cache pool 939,524,096, native cache budget 93,952,409 and retention 81,598,933. Available host RAM rose to about 90,056 MiB. Temporary native containers and 2.2 GiB of this delivery's local disk build scratch were removed; original data, logs, toolchains, worktrees, keys and leases remain retained. No global cache flush.

Do not conflate this cache activation with full runtime custody: installed foundation Compose still reports Docker Memory=0, and the existing manager session repository record remains historical 03b3b0eaaaf36b52ee1ceb9141e8f0261750d1d3; full source-to-runtime freeze/read-back remains unproven. The checked new release component defines the 4 GiB hard cap, but no release/publication is authorized here. The existing development target already has resources.memoryBytes; Deployment currently ignores it when materializing managed component overrides. Regression-first Deployment commit 559e242f reproduces that omission. A bounded owner repair is wiring that existing target authority into Compose RAM/total memory+swap limits and actual owning Docker read-back, with unit/native/scene coverage before supported host activation. No new schema, caller command, resource authority or installed-file patch is proposed. Rebuild reports agent.provider as a manual dependent; it was not silently changed.

Reviewer PR #108 contains the source-runner/all-owner custody repair. First native CI 38017016043 FAILED 185/186 before scenes: the existing production-installed archive fixture exceeded its unchanged 30-second watchdog. Earlier local 185/186 failure and isolated 3/3 pass remain retained. A held SDK archive experiment also failed the same original watchdog and was reverted, with its patch/log preserved; no deadline or assertion change and no new full retry without a concrete repair. Agent live-assignment work remains local 6f2a8d9; strict SDK remains blocked and no managed workday was launched.

Managed TreeDX hard RAM cap — checked delivery pending (2026-10-10 UTC)

Cache repair #92 is active via supported trsd rebuild: actual service fell from 46.48 GiB to approximately 223 MiB, while public metrics retain a 4,294,967,296-byte runtime allowance, 939,524,096-byte aggregate cache pool and 93,952,409-byte native log cache budget. Host available RAM is now approximately 90 GiB after scoped worker/build-cache cleanup. Durable data, leases, keys and unrelated services are retained. Live Docker Memory remains zero: the hard cap is explicitly NOT yet proven.

Deployment PR treeseed-ai/deployment#868 holds test-first 559e242f -> ca818c9d31a720d818721e1a4e5f467d2fcc5570. It consumes existing manager-held target resources.memoryBytes, renders equal memory/swap ceilings and rejects missing/drifting owning Docker observations. Focused 36 unit assertions, real Docker/Compose cgroup drift-denial/unchanged-retry integration, strict types and source shape pass. Existing component scene has three new refs; fresh complete privileged Actions are required. TreeDX PR treeseed-ai/treedx#93 holds RED f0f5542 -> 48e5a3032dbd688260bf1f5d44f9ef7fbf8b9c0b, declaring the user-confirmed 4 GiB in its existing development target. Existing archive regression and actual native MVP read-back cover it; fresh full native CI on both architectures remains pending. Only after checks/ordinary staging merge/read-back will supported host activation and exact selection rebuild enforce the live cap. No SDK campaign or strict passing receipt exists.

Reviewer #108 production closure correction (2026-10-10 UTC)

First Actions 38017016043 retains 185/186 passed, with the original actual production-installed archive case exceeding its unchanged 30-second watchdog; no scenes ran. Follow-up test-first 1dd7cce reproduces an unused CLI present in the production Reviewer install. Source/build entrypoints have no CLI imports and execute their own command. Repair c091d19a6521edc177e211d5948cd898d779b547 removes only that unused runtime dependency and obsolete build external; UI/SDK contracts remain. Actual Reviewer/fixture archives now pass all three original integration cases in 17.66 seconds, including missing-helper/checkout denial, unchanged retry and cleanup. Types/build/source checks pass. Complete local first run retained 181/186, five ExUnit environment failures (missing wrapper PATH, exit 127/ENOENT), with installed archive proof passing. Corrected native environment passes 8/8; fresh full local and replacement CI are running on c091d19. Local native wrapper now bounds its disposable containers to 256 MiB/no extra swap/two CPUs; derived abandoned npm installations were removed, archives/logs/evidence retained. No assertion or deadline was relaxed. PR treeseed-ai/reviewer#108 remains unmerged pending full exact-candidate CI and existing prerequisite scenes. This still does not prove all six production archives or strict SDK readiness.

Checked RAM containment and host activation — completed bounded scope (2026-10-10 UTC)

Deployment #868 merged e7019b86c2f2089ae94541657f4de93ea2687100, tree 09939a393b405a94cb6a96b3b46a975b7bbdacad matches tested merge 3fb4085410a256ea7f9108a6cc8c3c8143a09daf. Actions 38018382481: 196 files / 1,311 complete tests, fresh 1,311/1,311 before 233 component steps, all required checks passed. Scene artifact 11657637260 ZIP 80231b8eb61130cb7fcf7d229c093c974819e12733d5e4af85d27f41c5fd7d13; report ee2061acbc9c3aed9381c85dd6eeaf3e7821ab12660750ced0cc83a2a3c7679d. TreeDX #93 merged 638a45e1e3b23ea498fa7e6d41243c592a3dc317, tree 6cc281259a5b020880495ece28e7c019dd7465c0 matches tested merge 2ad5f91bd5d9a3defece0787cf223e96460699f9. Actions 38018443568 passed all 13 applicable jobs, each architecture fresh strict 548/548 with zero failed/skipped/todo before actual before/after-MVP Docker/cgroup/cache read-back. AMD64 artifact 11657302615 ZIP 031b977807e6591387888a613a5763b84e3bd3a16fc9284202b8294040669c61/report e30930a4a13f9342199d7e63186d932bd7036d1c1328398061df7e5a1a77bfb3; ARM64 11657617342 ZIP bdd8f5709fde49ae3ec59aaa9ad21c23f9a9b803b5be52beaa1a732375be3550/report 25ded379bcbf49008c5954d4c00f6e2f61ef107ca31e0ac161df5dd1c2928ae2. Only these deliveries' temporary remote branches were deleted after read-back.

Supported trsd host activation holds generation dev-1791601495907-399d696d, manifest sha256:5fae5e7c65b9ce9f7e5bb1f5a85c9f6604363b5225041651c82c4e92df9aea4e, unchanged guest c5ca5a6a6b7b516fee2dd3aea3390736a20a5996792e4cd2dc9f18cd7f074ef2. Public host file custody matches compiled RAM boundary cb00031e70acd96c42d5acc8037a4f61957442eade24dd3b0ac093908a139f69. Supported dev use/refreshed target then explicit dev rebuild succeeded for the existing dev-5007e344-493 session; TreeDX target generation 1160 ready, manager-held memoryBytes 4294967296, actual image sha256:39495d53519761d60a7b434f4379e5ba71af4bebcbc995d6fc48b8068214b9e7. Docker Memory=MemorySwap=cgroup memory.max=4294967296, healthy/not OOM, approximately 241 MiB at read-back. Public private-TLS health/metrics and governed TreeDX library show/status succeed. Metrics SHA256 e2a0b74e7219da9f9e738c2509e53a5a80a94783889e95f42f0ea67ed49e49d3: runtime 4294967296, aggregate cache 939524096, native budget 93952409, native bytes 81598933. The deeper authenticated /ready read exceeded the 10-second read-back command timeout twice; those failures remain, and current full runtime/freeze readiness is NOT inferred from Docker health.

Additional cleanup found 49 stale interrupted Reviewer full/native fixture descendants (2,229 MiB RSS), stopped only those exact fixture descendants and verified none live. Raw logs/archive/evidence, all data/keys/leases/worktrees and unrelated services retained; no broad prune. Approximate host available RAM 92,870 MiB; earlier 46-GiB service retention is gone. Original failed observations remain in Actions and the Issue history. No SDK campaign was started and neither SDK golden nor binding completion is claimed.

2026-10-10 nested action source regression: Agent #388 (treeseed-ai/agent#388), head 1cb6814e7421189c654bb2f970709c4d94136721, Actions 38019956088 / job 114118535499 passed all 119 files / 938 tests but stopped before any scene. The Reviewer composite preparation validated 7845a9e159f74f6e7adb988b0a367580b77555b1; its nested actions/checkout evaluated github.action_ref as v4 and tried to fetch Reviewer v4. The missing run bundle is a consequence, not passing scene evidence. Focused Reviewer RED 37b76ab reproduces absent captured output and wrong checkout input; retain the failed run. Bounded repair captures the validated ref in the existing step output and uses that explicit output for checkout. Native integration runs the actual preparation shell and Git checkout, checks exact package bytes, denies malformed refs and occupied destinations. Existing prerequisite scene gains one ref. No deadline/assertion relaxation, new runner or SDK launch. Local installed-archive watchdog remains independently unresolved; no blind local full rerun.

Bounded nested-action source repair is treeseed-ai/reviewer#109 (RED 37b76ab, repair 499d64d25ffa4d75cc654ad17815d883be5f6889); required Actions 38020474222 pending. Focused native/contract 3/3, strict types/source checks pass; existing prerequisite plan has 100 selected refs with no diagnostics. No scene was launched locally; original Agent failed run and local archive watchdog remain retained.

Reviewer #109 checked closeout: merged c562ed560683c89f23a0e582df4db327f395a99e, tree 0855f8100a97d00aa66de9393a0b6101fc97ad49 equals tested merge 80cbe189dac2fa79294874ecac08054988866148. Actions 38020474222 / job 114120155116 passed 31 files / 187 tests, fresh187/187 with zero failures/skips/todos before100 existing prerequisite scene steps. Artifact11658755642 ZIP a44cec130d1d762bdeae73cb9cb15a1eb0c26fc1a04ddb2723891c3940b461c7 / report cd60892ed0791181c05727258e0390b0b703b37caa01293fd9d2a88ed2b00c9b. Protected staging read-back and ordinary local fast-forward passed; only this delivery remote branch removed with exact lease. Agent #388 will consume this checked commit and requires a fresh full invocation. Original nested-checkout failure and separate local installed-archive watchdog remain retained; no SDK launch or strict passing claim.

Fresh consumer preparation blocker found before another Agent CI candidate: Reviewer dist/ is absent from exact Git checkouts. Native regression b1d0d36 ran the actual checkout and npm pack --dry-run --ignore-scripts; the archive contained no dist/verifiers/guarantees/command.js or node-case.js. The existing composite must run its existing build:dist after dependency installation and before complete suites. The same native action-custody case now runs that build in a clean exact checkout, checks native npm inventory, loads the compiled public runner and verifies unchanged Git state. Source build uses development dependencies as normal; it is not claimed as six production archive installation. First repair-focused attempt retained a fixture-only untracked node_modules symlink failure; the test now explicitly unlinks its own fixture symlink before the unchanged empty Git-status assertion. Original failures, 30-second test watchdog and 20-minute suite deadline are retained. Agent #388 remains held at its failed pin until this bounded owning preparation repair is checked.

Fresh-source archive preparation repair: treeseed-ai/reviewer#110 (head9f0473c7f574f17d391b1e515058ce9561fe9ec5, basec562ed560683c89f23a0e582df4db327f395a99e). Native fresh-checkout build/inventory/public compiled-import and contract checks now3/3 pass, strict types/source checks pass; same100-step scene, required full CI pending. Agent remains on held failed head1cb6814e7421189c654bb2f970709c4d94136721 with one batched checked-pin update planned after this repair. No further Agent CI invocation, SDK campaign or RAM-heavy build started.

Cleanup regression reproduced a current owning runner defect, independently of the old recursive fixtures: tests/integration/guarantees/process-custody.test.ts starts one real unreferenced descendant in an otherwise complete3/3 suite. Current runLocalGuarantees returned ok=true and continued into scenes while that descendant remained live (focused RED /tmp/reviewer98-owned-descendant-red-20261010.log). The regression's finally block killed and verified that exact child; no owned fixture process remains. Bounded next repair will isolate each owning suite/selected verifier command in its own process group, reject descendant residue, close only that owned group, retain the failed observation and block later scenes. Original timeout/output limits remain authoritative; no generic host process cleanup or new runner. Reviewer #110 candidate remains immutable in CI; cleanup delivery will follow its fresh staging read-back.

Reviewer #110 first required run38021157374/job114122227075 FAILED: initial31files/187tests passed, but its fresh prerequisite suite passed185/187, failed2, skipped0/todo0, and blocked all100scenes before any scene began. Failed titles: copied nested owner must not borrow parent Git custody; actual production-installed Reviewer/owner archive proof. Tested merge36c43b959e436eadca03adfa2ef2363034d49d8b, source26d40cede940a7f6f6189fa36f54972aa6d71d50d8bc7bef231ac3ca59b9f78c. Artifact11658896560 ZIP03e4320aa444c65ea5d0caf52ea331b7277987617f81704f6e7b11bdb15f20c9, retained /tmp/reviewer110-failed-ci-38021157374. Initial installed case took29.51s under its unchanged30s watchdog. No blind full rerun or Agent pin advancement. Inspect/reproduce the exact cheap failing boundaries and batch concrete fixes, including the independently reproduced owned-descendant defect, before a replacement candidate.

Reviewer #110 replacement cleanup candidate4e857425a048010a800687f02aec4a3545a1edd7 batches the reproduced failures before another full CI. Test-first7d83f9d proves a complete3/3 suite could leave a live worker and still continue;558c4e8 proves selected process errors were recorded but ignored. Repair owns POSIX command groups, joins native termination and kills/rejects persistent residue within the unchanged original deadline, retains original failures, blocks later scenes and leaves an unrelated group live. Both full-suite configurations run all files serially (RED7560e10/a59759d); actual installed pack/install/execute and scoped cleanup share the unchanged30s boundary with5s reserved inside it. The normal native exit race observed in focused diagnostics is retained; waiting for bounded group termination repaired it without changing assertions or deadlines. Full local npm run verify on4e85742 passed33files/193tests, zero failed/skipped/todo,149.56s; logSHA2563399d36445ef7d34f97a791c165659be94024faa56cc215ddc4c83f424fbe5e9. Existing prerequisite plan106refs/zero diagnostics. No fixture workers remain. Required replacement Actions and checked staging read-back pending; Agent#388 stays held. Earlier copied-owner/installed CI failures and local archive watchdogs remain historical failures, not reclassified passes. No SDK campaign launched. Required replacement run: https://github.com/treeseed-ai/reviewer/actions/runs/38022626454.

Reviewer #110 checked closeout: ordinary staging merge47d25eb8360c26f8cdf5b017f4e1500969c25285, tree91c0461f922e1f682749a67936bb11185f6856fc equals tested mergee9ada54250a11b10ed6fbb07f2521412a5c0d626. Required Actions38022626454/job114126682197 passed initial33files/193tests and fresh193/193 with zero failed/skipped/todo before106 prerequisite scene checks. Artifact11658624602 ZIP76c687c0373872e5c0e2cf9a71a9d042ac36f5f281ea29d75d6eb845821869e3/report89a2098124648c7c416f4c4a101f3d93c8b986a3f477daf46fdac2db41bc39c7; sourceDigesta9833edae3bd4033be503c3be0686c188734558ebbe538953c6f8ea0a3e7a95c. Protected staging and clean local fast-forward read-back passed; only this delivery branch was removed with exact lease. Agent#388 will consume the checked staging commit in one replacement candidate; its original failed invocation remains retained. Fresh strict SDK plan inspection through this source still has464 identities,204selected,260deferred and178missing bindings on the held Agent mapping candidate (planSHA256d7f27d9ceecb26b71d61558bfebd9024eacf6f589e1b5827064e4f28d73afa7e, specSHA256dfb012f90cbfcbf293d520008c752c1ef6f3617c2720e66717c07c8a187b89b3). Binding completion, six-owner installed proof and managed SDK acceptance remain incomplete; no campaign launched.

Agent#388 replacement Actions38023222177/job114128498623 FAILED before scenes: initial119files/938tests and fresh938/938 passed, but executing Reviewer47d25eb exited1 after collecting only169/169 assertions, zero assertion failures/skips/todos. Both guarantees/all685steps blocked. Artifact11659025969 ZIPc10dec3ab4f390232ab0f3a498c158b254c8f0f3b8c7ed086757e86a080c9ea9 retained; see SDK#387. Native diagnostic separately proved scripts-disabled Git SDK77a6908 installation lacks dist and its public import fails ERR_MODULE_NOT_FOUND. Hold Agent535902c; repair owning Reviewer dependency preparation and preserve failed collection evidence before another invocation.
The exact failed Reviewer sourceDigesta9833edae3bd4033be503c3be0686c188734558ebbe538953c6f8ea0a3e7a95c equals its checked own-source invocation, but dependency preparation differs: its own workflow installs the existing verified exact SDK artifact after scripts-disabled npm ci; the composite only runs npm ci. Diagnostic /tmp/reviewer111-native-git-sdk-diagnostic-20261010.log used actual native npm Git file transport against SDK77a6908, observed native install0 in5573.98ms with dist=false and public import1/ERR_MODULE_NOT_FOUND, and verified scoped cleanup inside30s. This is a concrete missing dependency preparation blocker; the consumer's omitted collection identities remain unproven until improved safe collection evidence and focused reproduction. No SDK product code changes, source fallback or new runner are proposed.

2026-10-10 — prerequisite repair and normal SDK readback integration checkpoint

Reviewer #111 holds regression aa04bf3 then repair 89564c894f4a03ed056a30165d12fb45e4afe44b. It reuses the pinned SDK artifact installer for the nested executing Reviewer, and retains safe failed collection file identities in existing prerequisite receipts. Complete local checks: 35 files / 196 tests, strict types/source/build, no remaining owned fixture workers. Required Actions 38024840189 is pending. Agent #388 run 38023222177 remains failed before all 685 steps (938 fresh Agent assertions passed, Reviewer exit 1 with only 169 collected assertions); no reduced suite is accepted. A separate actual pinned SDK Git installation with scripts disabled reproduced missing compiled public exports.

API #529 has locally committed focused regression c02c5794 and repair b145c816bf48cd523ac160f94873d27e464556a8: exclusive archive-first native Vitest ownership, then both original parallel database workers. All 376 files remain discovered exactly once, original bounds unchanged, six focused native/archive/resource checks pass, component plan 832 refs with zero diagnostics. Details and all three historical failed runs stay in API #515. No fourth expensive invocation has started; final checked Reviewer preparation will be included before replacement.

Agent #388 also now holds wiring regression 096063f: reuse the existing normal SDK post-campaign governed-profile, canonical-assignment, exact TreeDX context, SDK Core Book/Knowledge, complete graph-history and canonical terminal-record cases. Their reviewed preconditions fit a normal completed SDK workday and do not demand a failed attempt, controlled fault or continuation. Unit wiring checks pass after selection; actual managed execution remains blocked. This adds selected proof boundaries, not additional criterion bindings or a managed passing receipt. Criterion 164 and all substantive incomplete criteria remain unbound; the strict count remains 26/204 on held candidate, 260 deferred retained.

Live RAM readback remains Docker/cgroup hard limit 4 GiB with equal MemorySwap, healthy/no OOM, about 212 MiB actual usage; cache pool is 896 MiB within that cap. Platform public library show/status/paths are healthy at exact dd0e5ac944761a719b96046724661783b465421c; this is not current 17-proposal/136-definition campaign authority. No SDK campaign, release or production promotion has begun.

Reviewer #111 merged cleanly at 9dc625e2186e6d618cea30a17afd79fe64a95998; fresh required Actions passed 196/196 before all 110 steps, exact tested-tree read-back confirmed, delivery branch removed with exact lease. Final Agent #388 head 095db7982f0aa68eefd50b58d113ee8daaef2d68 passed complete local 939/119 plus packed-install checks and selects 15 normal SDK runtime refs; fresh Actions 38025596280 is running (663+23 component refs). Final API #529 head 6ebbebe9ede0f3cccb6e61e3c33f8dba85d47700 batches archive resource ownership and checked Reviewer preparation; fresh Actions 38025646915 is running. Neither consumer is merged or accepted yet. No duplicate local campaign or prerequisite receipt reuse. Exact artifacts and all historical failed observations remain in owner Issues/Actions.

Joined installed-owner audit and CLI repair candidate (2026-10-10)

Actual six-owner archive diagnostic held Agent095db7982f0aa68eefd50b58d113ee8daaef2d68, API6ebbebe9ede0f3cccb6e61e3c33f8dba85d47700, SDK375575d4350ac22d43b8ca2869940c2548214721, CLI22b6a27136a3583f4128cfd763917371e5572985, Deploymente7019b86c2f2089ae94541657f4de93ea2687100 and Reviewer9dc625e2186e6d618cea30a17afd79fe64a95998. Production install succeeded with scripts disabled and exact direct-archive overrides; original Reviewer byte-custody implementation passed Agent/API/SDK then rejected CLI. Native archive comparison found exactly one changed file: dist/.treeseed-build-complete.json, whose timestamp was refreshed by the supported development watcher. Installed dependency trees were removed after both diagnostic attempts, retaining actual archives and audit files on disk. First diagnostic attempted an unshipped internal helper module; the compiled public Reviewer command was present, and that audit error was corrected without package changes. Neither diagnostic is a managed acceptance receipt.

CLI #274 owns bounded IMPLEMENTATION_DEFECT repair: exclude only development readiness marker and atomic sibling through existing files selection, preserve executable asset custody and development lifetime. Regression543e6bb failed on original files selection and old Reviewer pin; repair82af902 passes focused12/12 including actual production CLI installation and unchanged repack integrity after marker writes under original30-second native case deadline (15.66s). Existing unit/native component refs are strengthened, not replaced. Required workflow pins checked Reviewer9dc to run fresh complete prerequisites before component scenes. Local verify:direct stopped before suite execution at original strict SBOM due to missing transitive development dependencies in existing node_modules; no bypass or passing release receipt. Declared npm test complete suite and required clean Actions remain to be verified. Six-owner installed asset execution remains incomplete; strict SDK launch remains blocked. No campaign started.

Held prerequisite failures and next bounded repairs (2026-10-10)

Agent third run38025596280/source095db7982f0aa68eefd50b58d113ee8daaef2d68/tested merge84c60172896c7c30fa12a66275b734ff6a5fbf34: initial939/939 passed, but nested SDK installer received TREESEED_SDK_COMMIT=9dc625e2186e6d618cea30a17afd79fe64a95998 (the executing Reviewer action ref), rather than declared SDK77a6908d4e7580716e9e2ab92de80150b02cdb06. Original120attempt/10second artifact wait ended with no sdk-9dc artifact. No fresh prerequisites or scenes ran, no scene artifact exists. Original completed job114135659738 log retained /tmp/agent388-third-failed-ci-38025596280.log SHA256c7e9c88755821885ff886b816448341ab2759970789136c02635f079ed3b6c4d. Classification IMPLEMENTATION_DEFECT in nested execution input custody, not a reason to extend deadlines or rerun blindly.

API fourth run38025646915/source6ebbebe9ede0f3cccb6e61e3c33f8dba85d47700/tested merge47e7513522306bf6736983af09fee9822283874e: native TreeDX all prerequisites, complete API376files2021/2021 and native PostgreSQL supplements3+17+28passed. The exclusive archive phase repaired the prior complete-suite resource failure. Then nested Reviewer setup-beam tried to replace the already-running same OTP27.3.4.18 binary used by native TreeDX, causing ETXTBSY at .setup-beam/otp/erts-15.2.7.13/bin. This was not a mirror outage; the summary message obscured the actual error. No fresh scene prerequisites/scenes ran. Job114135808132 log /tmp/api529-fourth-failed-ci-38025646915.log SHA256dae55e1a9f86c19e548328727640cdf3653698fd40ac42cba7a680cfb2184a2f; original native artifact11659329876 ZIP SHA2564a11353db822f0bdc664cf0432cddbc2ca82646b2a0a221e6d15dc8f278d825d retained/extracted safely. Classification IMPLEMENTATION_DEFECT in shared native toolchain setup. Keep the exact healthy pinned tools instead of overwriting live binaries; absent tools may use the original setup action, and mismatching/unhealthy existing tools must fail closed.

CLI #295 run38027013056 canceled intentionally after inspecting the deterministic nested SDK ref failure, preserving it as canceled/inconclusive rather than wasting another twenty-minute wait. No automatic rerun. API was already completed when cancellation was attempted and was not canceled. Batch known fixes before replacing downstream candidates.

SDK owning action needs one explicit exact artifact-commit input for nested callers: current github.action_ref is the outer Reviewer ref, as the completed native Actions failure proves. Preserve direct exact-ref callers and the original single download/install path, validation, complete-artifact success check, scripts-disabled install and deadlines. This bounded execution input is necessary; no SDK intent/product implementation or the reserved own-field defect changes. Regression first, unit/native integration/component cases and fresh complete source suites before scene evidence. Reviewer consumes its already-declared SDK manifest Git commit as the single artifact identity and must preserve/reuse a positively measured matching native toolchain. Required downstream Actions are rerun only after the replacement contracts converge.

Joined archive audit with CLI82af902 passed production install and Agent/API/SDK byte custody, then correctly denied a redirected CLI bundled-dependency asset. Original failed audit retained /home/adrian/.cache/treeseed-native-verification/sdk387-installed-owner-audit-QTHtSG/audit.json; installed tree removed. Cheap actual-install link inventory is running before any custody rule change. Reject workspace/source symlinks and altered/unarchived executable assets; do not waive these checks to make packaging pass.

Reviewer #112 replacement and actual joined archive observations (2026-10-10)

Reviewer#112 initial983351c passed native Actions38028655215:199/38 initial plus fresh199/38, zero failed/skipped/todo, before113 component steps; artifact11661480495 ZIP79f51eb3006d70b25a86de643f1e1ea4bc222502e7aa9673a9947bf24cb3893b/report9dd3dba8d250524df0178852369fbda1a6a5014333d0059d78fbc81d372cb818 retained. Actual joined installation then exposed CLI's declared unbundled Identity dependency nested beside bundled payload:39 extra Identity files, zero missing among5242 held CLI files. Native failing-first b9b8731 → f1044ef recognizes separately installed direct dependencies only from held manifest declarations and canonical regular manifest identity, without calling those bytes CLI archive bytes. Additional focused f72e207 reproduced original no-bundle node_modules redirect shortcut; repair0901ee7657e7ee9512dcd7330e836a0b47fd2299 checks symlink/type before exclusion. Final candidate native Actions38029391897 pending; initial receipt is not reused. Two strengthened original unit/native refs retain113steps. No source fallback or arbitrary directory waiver.

Joined archive diagnostic r6 installed actual Agent095db7982f0aa68eefd50b58d113ee8daaef2d68, API6ebbebe9ede0f3cccb6e61e3c33f8dba85d47700, SDKbc6499c6ebc5963bbf03ff2d80d51c837b6e451e, CLI82af9026faf709a8d2a48d49165e0d6848503b41, Deploymente7019b86c2f2089ae94541657f4de93ea2687100, Reviewer0901ee7 archives with production dependencies/scripts disabled. All six original package inventories and installed-byte/archive custody checks passed:261/1658/440/5242/812/17files. Later npm ls --all --omit=dev --json failed ELSPROBLEMS; retain failed overall disposition. Root sdk387-installed-owner-audit-yAoRS7 contains archives/audit.json; installed dependency tree removed. Cheap follow-up exact-archive installation AR5pfv retained dependency-graph.json/stderr and was cleaned. Some reported invalid versions equal declared ranges/exact values; cause is not established and no version pin changes or npm-check waiver is authorized by this observation. Public installed imports, CLI executable and installed Reviewer plan are being probed independently as diagnostics; no managed/scene acceptance, full installed proof or launch readiness claim.

Read-only supported SDK library show/status/read resolved current repo_a3c347e2abcd09af at f3146757b664cfb74c6c376c12f3b7efa43b6ae4; exact Researcher YAML contains acting/chat/estimating/planning profiles. Paths page100 hasMore true; it is not a complete current17-project/136-definition inventory. Original flags failure (library commands do not accept --server/--team) retained, corrected to supported public library syntax. No proposal publication, authority refreeze or campaign started.

RAM scope remains delivered/live: TreeDX Docker memory and memory+swap both4294967296, healthy/noOOM, observed222MiB; cache pool939524096bytes within service budget. Host availableRAM92,862MiB. Owned diagnostic installs are removed in finally; protected unpublished work, keys, retained failures and existing selections remain preserved.

Checked Reviewer delivery and replacement owner candidates — 2026-10-10 06:25 UTC

Reviewer #112 is merged to staging 77f8f0003ccdc477cf90801fd7b0a23b1a1bb82f with ordinary lineage, exact tested-tree read-back and its own branch deleted by exact lease. Required 38029391897 passed 199 initial and fresh assertions before 113 component steps. Artifact 11662056582 ZIP SHA256 94365307c75b2ee4df71fb7beb2cc22c092824902b53e98a9845fdf45531d22c; report SHA256 a989c374359192ea7725340f54f1463839231591347b2de5e85752c0b6aad5b4. No failed historical receipt is reused.

Final consumer workflow pin regressions failed first, then focused cases passed: Agent 6/6, API 6/6, CLI 9/9, SDK 12/12. Replacement heads/runs: Agent #388 b6a5fd9f98e0d4b74f8c2a60c485dd80588e6d15 / 38030369452; API #529 62ec595abe690c133aa732071ea7bf08358cfa28 / 38030377567; CLI #295 ee555a7501468c697f49c0b4ed618dbb4f269857 / 38030387337. All are unmerged, required verification pending. Earlier Agent nested-artifact failure, API ETXTBSY and CLI deliberate cancellation remain failed/inconclusive as recorded in their PRs.

SDK #389 now holds b66101bed7f73ccf6e535196772bf82c324a7b45. Final npm run release:verify on Node 24.12.0 and unchanged pinned Platform authority passed source/types/build/standards plus 74 files / 567 tests, zero failed/skipped/todo. Log SHA256 248d50c53479d6802aebdc75ee9f406b6524c0a90fe7fda289fc5e863c84fd9d. Source plan selects 220 component-boundary + 16 product-custody refs, zero diagnostics; SHA256 d473c32318c359c092e394580fead244aa14996e7281c19e9e4a71d79fde6cc9. No SDK product intent defect was externally repaired.

Corrected same-held-six-archive probe cN01Im passed public installed imports, manifest-declared CLI binary help and installed Reviewer structural plan (15 runtime refs, zero structural diagnostics). All six original archive-byte custody checks also passed. The joined dependency graph still fails npm ls --all --omit=dev; this is not an overall installed-execution pass. Read-only pinned npm source inspection suggests incompatible hoisted override ancestry; that cause is not established yet. A bounded nested-install diagnostic is running against the same archives, with original command bounds and automatic owned-tree cleanup. No managed verifier or workday has run.

RAM/read-back: TreeDX live service remains under the configured 4 GiB hard memory/swap/cgroup ceiling and 896 MiB aggregate cache budget. Host available memory is 92,847 MiB. Temporary diagnostic node_modules trees and completed owned workers are removed; archives and original failed observations remain on disk, protected leases/history/keys remain preserved. Full strict SDK binding, ready-to-launch and managed acceptance gates remain incomplete.

Current checked read-back and explicit remaining gates — 2026-10-10 06:45 UTC

CLI #295 is delivered at staging d443ddce30edd92e98a1313280f673d5bd31b691, exact tree 3c03d77cd510db7195abed48b9dbab28cfe82548 matching tested merge abfbecf91b7589d9bde7f2a169b889d30a6a8b76. Required verify38030387337 passed initial369 then freshCLI369+Reviewer199 before168steps. Submission-contract metadata failures are retained; corrected validate38031420066 passed before ordinary merge. Branch deleted by exact lease; clean primary staging fast-forwarded, main preserved. Artifact11662113561 ZIP 31a61078b949b394324d25bc387a701e982415d44bd99a6bc90ac927c9427d2f, report 5c2ddaba41bd0fe39a22e9cb6b826f47aec22f40ece01284c0ee8867b1bba334.

Fresh six-owner nested-install diagnostic cg8REv passed all archive-byte custody, npm ls --all --omit=dev, public imports, actual declared CLI binary help and installed Reviewer structural plan15refs/zero diagnostics. Log a82ff86c920aff40ae3608f7e65f609f1c8b24359edeb6c21cda559d1c76fc46; audit 2710e5f37444fc2720851f1854cd79f06dbbda7f8ade262fc15878db09b833fc. Held heads: Agentb6a5fd9/API62ec595/SDKb66101be/CLIee555a7/Deploymente7019b8/Reviewer77f8. All exact archive SHA256s are retained in the audit; isolated installed tree removed. This is a successful local custody/structural diagnostic, not selected managed verifier execution, native complete-suite authority or source-to-runtime launch readiness. Earlier hoisted dependency graph and stale-held diagnostic failures remain retained.

Agent38030369452 passed fresh939, then Reviewer198/199 failed ACCEPTANCE_INSTALLED_EXECUTE; all686steps blocked. SDK38030761178 passed fresh567, then Reviewer198/199 failed ACCEPTANCE_INSTALLED_INSTALL; all236steps blocked. These remain failed. Reviewer #113 supplies bounded native error-code diagnostics after an actual25ms subprocess timeout reproduced the lost-code defect. REDff2bb03 precedes repaircc1de4540ab2f08d2fff7ae31806e3d6332e51fc. Focused22/22 and strict source/types pass; native Actions38031721532 is pending. No consumer blind rerun, changed deadline or claimed underlying repair.

Current full strict plan remains blocked:464total/204selected/26bound/178unbound/260deferred, exactly the unchanged acceptance digest. Plan SHA256 b62c449f6eb883679c1ccbb54a27ba2fd0722f37ed62c467f38e07ab8096a3be; all178 diagnostics remain uncovered criteria. Six normal public read-back selections do not themselves justify new semantic bindings. Criteria11/12/170/184/192 remain partial, and the reserved SDK own-field product defect remains unchanged. No managed campaign has started.

Latest live RAM read-back: TreeDX container357c6e549e42… healthy/noOOM, Docker memory=swap=4294967296bytes, observed220.1MiB/4GiB. Aggregate cache budget remains896MiB. Host available92860MiB (~90.7GiB). All completed owned diagnostic installations/workers are cleaned, retained archives/logs remain on disk, and protected work/keys/history are preserved.

Integration read-back — 2026-10-10 07:08 UTC

SDK PR #389 delivered staging 64f25a0a162e0a30735dd07ca0a9ef16174914b8 by ordinary merge. Required 38032481310 passed initial SDK567, then fresh SDK567 + executing Reviewer199 before all236 component steps, zero failed/skipped/todo/diagnostics. Tested merge 1dfd7063477af37d922f47ebfb0871079836ddf1, tree 248151c81b0fdc20a05cae9e66e9092cb50e4c9c equals merged tree. Artifact11662527307 ZIP SHA256 aaa16f70077fa978780bb9ec9793e0179009307eae86a6a85d2728d186ba700d, report 5807cd9cd71d5cf1a1379279fc26101476f9567f2162092f4fe40b9d2ccddbda. Current verify+validate passed; clean primary staging fast-forwarded and only this delivery's remote branch deleted under exact lease. SDK product own-field defect remains reserved for the genuine managed test-first chain.

Reviewer #113 delivered staging c8bfadc036029f37ecc197884faf63df3f6d59a2, exact tested-tree read-back after required38031721532 passed199 initial+fresh199 before113 component steps. CLI #295 is already delivered at d443ddce30edd92e98a1313280f673d5bd31b691. All prior failed observations remain failed.

Agent replacement 38032480341, source c930689895a08890be5355a0b80c0348cbdaff9c, tested merge f117bec1f675d10c1dbe18779695e078e09d1377, passed initial and fresh Agent939 assertions. Fresh executing Reviewer198/199 failed its actual production-installed fixture at ACCEPTANCE_INSTALLED_INSTALL_VERIFIER_SUBPROCESS_CLOSURE_UNPROVEN; all686 component steps remained blocked. Artifact11662692386 ZIP SHA256 557873708d4ba343017e77af53a7e2ac005e0069e49f0f6d0ed7bcb293881c0e, report da3e54e2154b0b602308103ac2169505f31dad5153f12352c40f338335c5cca5. No blind retry. Focused Reviewer regression afd715e independently reproduces cleanup overwriting an original native ETIMEDOUT with closure-unproven; RED log SHA256 c5821b5a942c1105d9ed3c40f8119480129fdcbad59e7a658547eb87a294107b. Repair must preserve original and cleanup failures, all deadlines and failed disposition. This observation does not yet establish the original cause of Agent's install failure.

Current strict selection remains464 full /204 selected /26 bound /178 unbound /260 deferred. No managed campaign launched. Healthy exact-ref library inventories show missing current campaign proposal authority in several libraries (empty proposal directories or .gitkeep only); historical SDK v3 draft differs from the fixed current request. These reads are prerequisites, not fabricated campaign authority. Live TreeDX retains enforced4GiB memory/swap ceiling and896MiB aggregate cache budget; owned temporary installation trees and obsolete test processes were removed while existing selections, leases, keys and history were preserved.

Integration, authority and cleanup read-back — 2026-10-10 07:32 UTC

API529 delivered staging a5451539929c33d00bbdf2b42337a34425555be0. Required38030377567 passed native TreeDX server/all SDK language prerequisites, API376files/2021initial, PostgreSQL3+17+28 supplements, then freshAPI2021+Reviewer199 before832steps, zero failed/skipped/todo/diagnostics. Testedmerge800ed5dd/treec7df450c equals merged tree; artifact11663287889 ZIP SHA256 426f862d24e4a38c2e4d8ccc7fd92fabc3ffd28733908d15feafabc8180fc93c, report a23170effdd3436275e0332130c06f42bf0762e38891fab8f09055da826c1e80, joblog 6afe388e66e77f261adbb60a14c71e3b1ef31848a97d2596b450f845e54dab5a. Reviewer114 delivered staging 879c7406582b0d7da4dcdcd5356ec21daa286662, required38033504127 passed199initial+fresh199 before113steps. Testedmerge65cda8e0/treec04721ad equals merged tree; artifact11662749078 ZIP 846a3a1513758ced11e1ccc0c993b2fd7ce24f87dff957abe6b38a798bc3a215, report 777ed44e3248ebf4975afbfdeded7603401298d6f71359e0bcc721fe9185acdc, joblog 4ed1c85cd1081e6f5fb17dff43aa2f1e1ec9bd9537bf4b918122859c6b051ab8. Both ordinary merges preserve regression history, exact-tree read-back, clean staging fast-forward and exact-lease branch deletion.

Agent388 candidate 391dd8722eec5ed3d5eb51c7562d4ed451fac773 consumes checked Reviewer114 after focused RED1fe74c6; fresh required38034320880 remains active. Previous c930689 invocation remains failed. CLI296 candidate 90488e13994ec8be4741ab3b488059210052690f independently reproduces and repairs moved-invocation-symlink empty successful output. RED6c4bd5e precedes repair90488e1; unit/real installed-archive focused12/12 and committed full369/369 passed, strict real compiler/source checks passed. Existing369 assertions/168steps unchanged. Required38034466158 remains active. No local acceptance scene, campaign, tag or release launched.

All17 exact public library path inventories are complete, contain136 definition files, and fresh protected staging read-back matches17/17 held library commits (read-back SHA256 baf16ef50e66c7cb6491744eb091ec11631fce9e96f4a16d3bc0ce36d46896c4). Fourteen libraries have no proposal content beyond empty directories/.gitkeep; API and Market each retain one proposal; SDK has85 proposal files requiring exact-current-request review. Existing SDKv3 base draft differs from the fixed request. Definition-content traversal retained six Platform reads, then stopped at empty exit-zero CLI output for technical-writer; those136 contents are not certified. Earlier eight SDK definition reads remain scoped to their held revision. No missing current campaign authority is manufactured from history, paths or incomplete reads.

RAM read-back: live TreeDX healthy/noOOM,250.4MiB/4GiB; Docker memory and memorySwap both4294967296. Aggregate cache896MiB remains enforced inside that ceiling. Host available91967MiB. Owned temporary installation trees and obsolete processes were cleaned previously. Ten owned retained Actions evidence directories (20947024bytes) moved off RAM-backed /tmp onto disk; every regular-file SHA verified unchanged, existing paths retained as links. Existing selections, unrelated resources, all34 leases/keys/history and historical worktrees preserved. Other old /tmp checkouts/toolkits are not assumed disposable.

Strict SDK selection remains464full/204selected/26bound/178unbound/260deferred on the held Agent candidate. Binding completion, exact current runtime/campaign freeze, supply, public physical closure and managed golden proof remain outstanding.

CLI #296 delivered — 2026-10-10

CLI #296 merged ordinarily to staging 6a1f8fc3892c069c1efab72c05baa0f0dfa48964. Source 90488e13994ec8be4741ab3b488059210052690f; tested merge a05a4858d25fbfe9332c673f5d719c8c6edfd11f, tree 58b65ead88a25ba879ffe8e8d36faf8d4855f9ed equals merged tree. Required 38034466158 passed initial369, fresh complete CLI369 plus executing Reviewer199 before168 component steps; zero failed/skipped/todo/diagnostics. Artifact11663920084 ZIP SHA256 ea5c932a2c75a7f4296a29bdfcf482275e10bb6c4d50a57e07867b29be8d06da; report b1926cba397604de76d9323f9883fb8c036ff42d228fee08619dc71b53be6eb0.

The sole executable now always delegates to its existing command runtime. The actual installed archive regression proves completion after its invocation symlink moves during dependency loading, with exact binary bytes retained. Existing public commands, package engine support, selection lifetime, denial and teardown coverage remain intact. Local primary staging was safely fast-forwarded and is clean; only this delivery's remote branch was deleted under its exact source lease. No live CLI selection was switched by this delivery. Earlier empty reads and failed observations remain preserved; this controlled regression does not establish every historical empty response's cause. Current campaign authority, complete governed contents and strict SDK managed acceptance remain unproven.

Agent #388 sixth retained failure and native CLI ownership repair — 2026-10-10

38034320880, source 391dd8722eec5ed3d5eb51c7562d4ed451fac773, tested merge b010f73a68ba253c5f1cf3db156f1d926c54e699, passed initial Agent939 and fresh complete Agent939 plus executing Reviewer199. The selected native synthesis case agent.golden.synthesis-cli-invalid then returned a passing assertion but failed VERIFIER_SUBPROCESS_RESIDUE: an owned subprocess remained after exit zero. All663 later component steps stayed blocked. Artifact11663775343 ZIP SHA256 110d653461d4f002097895f24dffb7939b2fb6983a7ab50391456cdb6541ca66; report 5d86e6585ce2b27310cd36e5a4deb9f2514f8128483ec930b2d4ab66ca3f9a63. Original failed receipt and raw native observations remain retained.

Regression d815e79 strengthens the original real pinned CLI/loopback SSE case with transparent native spawn observation, requiring an independently owned POSIX process group and its actual absence before return. RED reproduced the missing group ownership; log SHA256 f770d695759d728f8aa710103b6db8e840c719083db5e36b52922e172db58308. Repair c414bdc63fc873a72727c7e319dd89b3d21cfe64 replaces the fixture's ad-hoc leader-only timer with the existing production process runner, retaining its original15s command bound and fatal launch/timeout/cleanup errors. Only actual positive CLI rejection codes satisfy the existing malformed-schema negative case. All three real native fixture assertions passed; focused log c248e3ff7a864142b4091d91727fae9486bd1262d8e40753707549825e45c318; strict compiler and source architecture checks passed. Fresh complete local suite and replacement required Actions remain pending; this is not a passing managed receipt.

Deployment #869 pending public inspection scope — 2026-10-10

Deployment #869 holds source 7b9707f3a01e8e9b31460d92220478dfa1b0dc88 on protected base e7019b86c2f2089ae94541657f4de93ea2687100. Regression-first unit/native installed-boundary changes add only the supervisor-owned broker socket to the existing inventory scope; existing outer runtime identity remains authoritative. Focused9/9, strict build and source checks passed. Required privileged 38036035237 is in progress. Normal SDK physical-absence consumption is not implemented or proved by this source change.

Latest strict prerequisite custody and governed content read-back — 2026-10-10

Agent 38036193866, source c414bdc63fc873a72727c7e319dd89b3d21cfe64, tested merge 11d71370a20d8656add936c78838b807b16faddd, passed initial and fresh Agent939. Executing Reviewer198/199 then failed ACCEPTANCE_INSTALLED_INSTALL_ETIMEDOUT; all686 steps remained blocked, no scene was executed. Artifact11663418765 ZIP SHA256 2953735886a6fc258cd12563a963f15418f65a6a85b22030bbe292a91f37714b; report 6750f19c9d7e02b769ea229d7e4e35f6e44d361a85c9f05a1746d2e65d3eac8d; raw job log c05c3d0670e3ff80738b140f529d86b6d45e9a0c41d9eb79b8d11bfb93cdda82. The native schema process-group repair remains locally proved; this invocation did not reach it. No blind rerun or merged Agent delivery is claimed.

Deployment 38036035237 passed native196files/1311assertions and fresh1311 before233component steps, including actual installed CLI/manager/supervisor scope. Tested merge c381a445efaba949d77cb0335936ae762da4b3ba, tree f613af8476ae43fd1586e579709f2e064e5c00d4. Artifact11663817055 ZIP b564113ea768aa2941238f1089f98d9227244323c9f74eb5098fab03dd99a2fe; report 80dcdd109f3212f4d8162fb23eeb06dedfd7dc9a0b4e0ecc031085befb96986a; raw job log 73a7382f13f2492a395a6e380fb6dc5fc1c0000bc719e7d4f2780e6e9f2d371d. Audit found its workflow still executes old Reviewer 1e3019fbf24163116222dc96a70c126bf3488389 and retains only the Deployment prerequisite. Executing Reviewer's complete suite is missing. PR869 stays unmerged; successful native component evidence does not satisfy that launch prerequisite or the full current contract.

All136governed agent definition files across17held library refs now read successfully through the selected CLI's fixed real generation2 entrypoint, pinned Node24.12.0 and existing TLS trust. YAML frontmatter schema/id uniqueness and nonempty activity-profile maps were checked; observed configured activities total527. Readback SHA256 863471aeabdef00050542527ca3ee25e2bf66afd20eb88dfb8fa730bfdb60994; command log 8bdf0ecdc83ccdb0aebf9e5f01cb7e7855a644f434813fc07556ce341141cadf. All17 protected library staging heads were rechecked unchanged; protected-readback SHA remains baf16ef50e66c7cb6491744eb091ec11631fce9e96f4a16d3bc0ce36d46896c4. Earlier empty reads remain preserved. This establishes current held content read-back, not current ready proposal authority, handler execution or SDK acceptance. The immutable operator campaign manifest and SDK freeze paths remain missing and have been requested; no campaign can launch on substituted historical authority.

Cache override allocation repair — 2026-10-10

TreeDX #94 holds source b3ec3dded28a7c9c4bbd111b6e778db1ec393a57 over protected staging 638a45e1e3b23ea498fa7e6d41243c592a3dc317. The actual owning native regression 0aabbeb reproduced one retained repository entry despite zero global cache allocation when an override requested4GiB; e2ef923 retains the existing managed metrics case RED for missing repository/graph overflow denial. Repair b3ec3dd gives both existing caches one shared strict byte-limit helper: overrides can lower allocations, including zero, and cannot enlarge them. No new resource authority or configuration field is added. Existing MVP metrics now require each managed cache within its share as well as native cache, actual Docker and actual cgroup4GiB.

Focused native8/8 (actual NIF, original native engines) and metrics2/2 passed, zero failed/skipped/todo. Clean native RED SHA256 e0cd8984c0a09cd6cce0d1247ad5d175f470110a9483243b2447304a22c8b249; final native f4463df2dd97f03515614414b7ac2349277e81a03f18792ceae00922dcbadb59; metrics RED d10755d51f5e23f4271020f2252efe2c40f9a113af938d2b321f34129cf0f78d; final metrics 9b0868721608668a0eba9df63f17f00e40710fe9effb376667930498779c6093. The first native RED's read-only Mix metadata failure remains retained separately; its clean repetition used a bounded disposable metadata mount, now removed. Strict reporting TypeScript and source checks passed. Required 38037472529, fresh native full suites before MVP, staging read-back and supported activation remain pending.

Live service continues on its previously checked image with Docker memory/swap and actual cgroup limits4294967296bytes, healthy/noOOM, latest observed263MiB. Shared cache pool939524096bytes, native93952409. No data, keys,34leases, historical worktrees or unrelated processes were removed. New override repair is not yet selected live.

RAM delivery and prerequisite follow-up — 2026-10-10

TreeDX #94 is delivered at staging ba464cc2e276aaa4ad0f948b938984ad7263586e (tested tree6716991ebd0529e86d6a6b575d83f107055bb38b). Required38037472529 passed all13applicable jobs and fresh550/550 strict assertions on each architecture before MVP, retaining all four SDK languages. Actual cache overrides now clamp to allocated shares, including zero. Supported existing-session rebuild succeeded (generation1468); actual Docker RAM/swap and cgroup4GiB, healthy/noOOM,171.2MiB observed, all three cache measurements inside shares. Ready passed all six original checks within180seconds; shorter diagnostic request timeouts retained. Actual image22800cba3f8977b6ddd13f292111bb553a658f8a5ca3ccfc10e34bb3e4b5a2b6. Complete RAM/evidence readback in TreeDX86/PR94, no broad cleanup or data/key/lease removal. This does not establish the full campaign runtime freeze.

Reviewer #115 retains a real cold-install/public SDK-export regression e67afae and actual built SDK archive repair. First native38038773997 at a3499df failed198/199 at original SDK-export subprocess deadline, no scenes; job log SHA256 dae118cdfe23cd5b80bb03e948c73b86a6c1a7b70c95b502d53e515dca5cd3cb. Replacementdc1836ee835b1f19f42d8f2d8b655b538c1bd6cc batches three exact archive packs into one npm process, verifies unique identities and every installed SDK byte, restores standard npm content caching while keeping fresh isolated production installation and scripts disabled. Focused3/3 now13.56seconds rather than23seconds; SHA256 d246fb9dbfdb077977ae9c95cb414c8f10efb846a2cd7ab7262028b8d1b4152f. No deadline/closeout reserve/negative assertion changed. Required replacement38039331968 is in progress. Local full198/199 native-toolchain environment failure retained. Agent388 remains draft/unmerged with seventh failure and686blocked components; no blind rerun.

Deployment869 retains first green1311/233 component evidence but remains unmerged because executing Reviewer full-suite custody was missing. Regressionbf9b81b3 proves absent prerequisite bootstrap (logb867701dc95c9d90cde399df0be3eb9b504046f0fcc7e69e34f6a658f686ebb1). Working repair uses the existing Reviewer dependency/toolchain/exact SDK build bootstrap and existing outer production CLI; fixture failure/redaction/retry proof uses the original exported runner API with its complete two-case owner suite, preventing recursive full production self-suites inside each10-second fixture subprocess. Native CLI plan proof and all negative/retained-byte assertions remain; focused3/3 passed. Await checked Reviewer115 delivery before final pin/new required native candidate. No privileged local scene launched.

Normal SDK public physical-absence assertions are now in local implementation: complete owning scope/broker/runtime, post-teardown observation times, task/container confirmation, mounts and managed-directory inventory with unrelated resources retained. A separate normal completed case consumes fixed public host status; existing completed-and-failed/private-host case remains unchanged. New unit negatives and selected wiring are being verified. This is not complete VM/NBD/source/session closure or independent producer completeness; criterion193 and the strict178missing bindings remain unproven. No managed scene or campaign launched. Current immutable campaign manifest/SDK freeze and17fixed governed proposals remain required inputs.

2026-10-10 — checked RAM selection, delivered Reviewer closure, and repaired consumer candidates

TreeDX #94 is merged at ba464cc2e276aaa4ad0f948b938984ad7263586e. Both native architectures passed550/550 fresh assertions before MVP checks in Actions38037472529; the merged tree matches the tested tree. The supported trsd dev rebuild treedx.service --session dev-5007e344-493 --json selected generation1468, actual image22800cba3f8977b6ddd13f292111bb553a658f8a5ca3ccfc10e34bb3e4b5a2b6, healthy container3231ebf55b11ff2341b8a173f04cff1ad3d1f39e19a50903505d6bdeb5165a61. Docker/cgroup memory and memory+swap are each4294967296bytes, the user-chosen4GiB limit. Public metrics retain total cache939524096bytes, repository469762048, graph281857228, native93952409; actual measured native81598933/repository0/graph0 are within their limits. Per-cache overrides clamp to their allocation, including zero, instead of increasing the total budget. Rebuild log SHA256410ee8c89c44240fb7e28b26d028cb0bd241e173dc630a024d1ca29a79869cff; metrics1cb270bdf8840a5545725529f6429b592ddd9242ca8c6ab4cb31a6807fc2cb78. The original180s readiness bound passed; earlier short diagnostic timeouts remain failed observations. Library binding stays healthy at dd0e5ac944761a719b96046724661783b465421c. Persistent development selections, data, leases, quarantines and keys remain retained.

Reviewer #115 is merged at 62d261910f8bd157ba6575b185a586263dff8e44, tested tree32d9682c47e7b2b68bd52850c22759ebc8a5d06f. Replacement Actions38039331968 passed199/199 initial and fresh199/199 before113/113component steps, zero failed/skipped/todo. Final ZIP SHA256f572e5c4683bee870ac86b65b06ed05305d5d584320c1588e1ee2aef446d409a; reportd0bddbe757acef56c6d86e052380b123caab497eded19d946dd290ba556c1280; loga89ccacbe744b7637906c98353bdc41cb244e299db2ae99983825d73edc99125. Fresh isolated scripts-disabled production installation now includes the actual held built SDK archive; all shipped SDK bytes and its public import are verified. Actual archive packing is batched and standard npm download caching retained; the original30s/5s closeout bounds remain unchanged. Failed run38038773997 and earlier failures remain historical failures. PR and owner Issue read-backs match their updated delivered bodies.

Agent #388 eighth run38040311752 stopped before complete verification/scenes: eleven direct executable support files exceeded the unchanged ten-file architecture ceiling. Raw log SHA25600942dc80939c4657439049915eaa5d8777e2aa786589efd4e9ca967accb1723 is retained in Actions and disk evidence. Current candidate 3adb3cc0a1da3ee908b4d6003f18db1a52d8120b places the new physical helper under functional physical support and selects existing cli.golden.execution-diagnostics-read-native once before the SDK campaign, after focused RED8fea622. Independent Agent tests do not import a CLI checkout. Focused10/10, strict types and source checks pass; exact complete local120files943/943 passed94.36s, SHA2565712faa042d4866bf7bde2dead7665e85eb949b92c3877cf316035190087e3a8. Ninth native run 38041183552 is pending. The CLI definition resolves to its actual owning packaged native read/denial/retry case. Existing composition discovery requires Agent, CLI, SDK, API, Deployment, TreeDX and UI; UI is a declared CLI package dependency actually imported by the compiled CLI runtime, not an unrelated browser companion inferred as a verifier owner. Executing Reviewer remains an additional prerequisite owner.

Deployment #869 second run38040233775 failed2/1311 complete-suite assertions before scenes. Two old contracts treated all SDK installers as root-owner installers and rejected separately scoped executing Reviewer custody. Raw log SHA256417e38dd39cd757a5aab1f75b0aa25ccb13b41e1fe88bfb7bc8ba5a6d70f6577 is retained. Current candidate 464a4018a83c304bf129d05f2b434c25819e2fbe keeps exact root dependency/lock/helper/production-mode checks and additionally requires the separate Reviewer's measured commit, pinned helper and nested installation path. Other native workflows still prohibit scoped overrides. Focused3/3 additional checks, strict types and source shape pass; these filtered checks are not complete prerequisites. Third privileged native run 38041076055 is pending. No local privileged scene or managed campaign was started.

Latest strict plan SHA256b06d505ca2293519df1a59902050d1ee1174af5f633ee6cc67f15a8e05b42b42 retains464total/204selected/26bound/178unbound/260deferred and17selected scene refs. All178diagnostics are missing semantic bindings; no stale/missing verifier diagnostics. Initial source-plan invocation from Platform could not resolve tsx and executed nothing; corrected source invocation from Reviewer produced the retained blocked plan. Normal SDK public absence still covers represented sandbox task/container/mount/directory closure only; it does not establish VM/NBD/source/session absence or producer completeness, and criterion193 remains unbound. Current fixed17proposals/operator manifest/freeze, full live semantic monitoring, failure taxonomy/retry controls and substantive SDK test-first/research/documentation/release proof remain unresolved. No strict SDK passing receipt or launch readiness is claimed.

2026-10-10 — Deployment privileged prerequisite environment repair

Deployment #869 third candidate464a4018 Actions38041076055 passed initial1311 and fresh1311/1311 own assertions. The newly included executing Reviewer suite failed198/199 with ACCEPTANCE_INSTALLED_INSTALL_ETIMEDOUT; all233component steps stayed blocked. No acceptance step ran. Artifact11666521274 ZIP SHA256328cbb5f424e812b9fdcc3f2473db179709c320293cee146c1bc216c4899c5e1 and raw log9cca4f840db8d2c2a666b8291504838111c0184804cc9ee88cdcfc10476f7b9d are retained. Classification for the bounded repair is ENVIRONMENT_DEFECT: npm dependency installation ran as the runner user, while sudo prerequisites did not preserve the content-cache location. Different cache custody is observed in the workflow; redundant cold downloads are a plausible bottleneck, not a proven timeout cause. Current replacement ddb167e868f2912e8c0609f0af09bf6da31d3ab2 preserves one job-scoped standard npm cache through privileged steps after regressionfc632a41. Original isolated production installation, scripts-disabled archives, thirty-second/five-second closeout bounds, permissions and assertions are unchanged. Meaningful RED SHA256a901ede34c25a5012bad0e220864ebd3139f3006df916809692d9fd910b96ae8; initial unguarded TypeError is retained separately. The complete focused contract file passed15/15, zero skipped/todo, SHA256763f924e16379d856a8b754d91bcda0a8b552770219fb30fd526d40a874bbadf. Source-shape passed. Fresh fourth native CI is pending; Deployment remains unmerged and no managed campaign is authorized by these component results.

Selection audit also identified that API's existing clean-schema live case requires actual nonzero governed priority and historical calibration. Those preconditions must not be imposed on the unchanged normal SDK proposal, nor silently removed from the existing later-stage case. A distinct normal SDK reuse path is still necessary; API protected-clock live read-back has normal-workday preconditions and is suitable for the next integrator binding change. These are unresolved wiring findings, not additional passing bindings.

2026-10-10 — cache workflow context correction and resource closeout

The first shared-cache candidate ddb167e8 was rejected as invalid workflow in 38042035589, before jobs/tests. Classification: IMPLEMENTATION_DEFECT. The job-level environment incorrectly referenced runner.temp, which GitHub does not expose at jobs.<job_id>.env; the official context reference is https://docs.github.com/en/actions/reference/workflows-and-actions/contexts#context-availability. Regression078e30a1 requires the supported github.workspace context (RED SHA25615fcebc7c25fcb691f397e3afbba42d5db06e5dfb81163271dd22c58a1a1b3dd). Current Deployment #869 source b4660d65f5bdc61c8ae27736f98567ff35dccc7e uses one standard npm cache at the disposable ignored .treeseed/npm-cache path and preserves it through the same sudo operations. Complete focused contract file15/15 passed, zero skipped/todo, SHA25677401e972c9d7ed51fd430475191b4f88d341a182f66e5c815d4b6b3e1da1cda; source policy passed. Fresh native 38042262884 is running. No successful receipt is attributed to the invalid workflow or the preceding blocked runs.

All new local complete/focused test and npm-install processes have exited. Current read-only memory inventory reports87935MiB available; unrelated user applications and persistent services are retained. No active local scene, owned test subprocess, package installation, campaign, tag, release or scheduled task remains from this checkpoint. TreeDX's supported4GiB selection and cache shares remain unchanged. Agent #388 native38041183552 remains in progress; its component-scene outcome and final prerequisite receipts are pending. Deployment and Agent deliveries remain unmerged until exact required native checks pass.

Agent388 delivered — 2026-10-10

Agent388 merged ordinarily to staging f61c42464141ce17987247e37b46c75ab32c1264 after required38041183552/job114181581224 and submission validation passed. Tested merge bce6d1c2113eee981e85bec312255f6c983c69d2 and delivered merge share tree5f36b916d1c93ba9ea556886bc7785dbe6ff9ceb. Fresh Agent943/943 and executing Reviewer199/199 complete prerequisites preceded667+23=690 passing component steps; zero failed/skipped/todo/blocked, zero diagnostics. Source3adb3cc0a1da3ee908b4d6003f18db1a52d8120b. Artifact11665594090 ZIPcf05042f676a77a87c7d1595ac67a51682a10f113ab9dd802711fbcbd72bc727; reportc75dffe2dfddc6c05c9f6979b1f848ea3be9808577e974f5ee071f28cc7bc8c5; rawe94e9485ebfee1a355e193c95bbebfa396f5ceabe9338567465df1739ead54d7. Failed earlier runs remain failed.

Assignment observer, existing normal profile/context/Book/graph/record read-backs, explicit packaged CLI native diagnostic case and separate normal public sandbox inventory are delivered. Full producer completeness, actual model/runtime authority, all VM/NBD/source/session closure and criteria164/193 remain unproven. Strict selection remains464/204/26bound/178unbound/260deferred. Clean primary staging safely fast-forwarded, stale local main preserved, only leased delivery remote branch deleted. No managed campaign/acceptance launched. Deployment869 remains pending its fresh native required verification; host activation remains gated.

Protected native clock binding continuation — 2026-10-10

On freshly held Agent staging f61c42464141ce17987247e37b46c75ab32c1264, regression21a9425/e641de8 requires existing API-owned normal protected-observation case after Agent clocks and retains unfinished-handoff preconditions separately. RED log535d78b0d60be54c199e0a166b9ce83e2ba017e5e0722abfe34f6e2c072fb32a. Repair bd9348b selects api.golden.execution-protected-observation-live-1 once and adds it to existing criterion11 alongside Agent clock read-back. Native database assignments/events, encrypted executor actions, first/final/intervening original clocks, actual mandatory replay and immutable public read-back remain implemented by API's existing case; no duplicated verifier or new identity. Agent independent suite validates foreign binding selection; workspace Reviewer resolves the actual API definition. No API source/SDK product change.

Local complete Agent120files943/943 passed with zero failed/skipped/todo (97.47s; SHA428e94e3417cda6b54814adb98e1300a0cde30416e0847b5ccb26d4688f6fac9), strict TypeScript/source passed. Strict plan SHAe94b59038142a6abcb0b6bceddbb2f00f12b07e3e29f31ae0906c48a4e4805b0 retains464total/204selected/26bound/178unbound/260deferred,18SDKscene references; all diagnostics are the178 existing uncovered identities. Required Actions and merge remain pending. This strengthens prospective wiring; actual managed clock proof remains pending launch readiness.

Additional cleanup found six orphaned Reviewer proof subprocesses whose temporary fixtures were absent. Exact UID, argument, parent and process-start identity were checked; SIGTERM through pidfd stopped all six,512MiB RSS, none remained. Evidence SHAd4f9f0bc8987ac5bf8d5c80f734bffe51b9d19d0167231db92fa54fd4b321ecc. No unrelated resources or retained work modified.

Deployment869 native prerequisite progress and packaging failure

Currentsourceed14ea0143f8e885127ceaede371f7d8354f9634. Failed38042262884/job114184689320 actually passed initial1311, freshDeployment1311/1311 and executingReviewer199/199 before233/233components,0fail/skip/todo/blocked/diagnostics. Native packaging then failed EACCES because privileged verification created root-owned entries in its exact shared disposable workspace npm cache. Failure retained (rawcb8407fdf5f15505ffa6321923ec480d3bfb5efdbe1f34fe01ed285c1ef405b8;artifact11666074176ZIP6d24aded84fb0a310433d6f3d72bd140bc50a61ba88a0d6dc937ff25142331ce). Distinct IMPLEMENTATION_DEFECT, not another unexplained timeout or passing required job.

Focused regression4abfa281 RED18cb3594aeb90405f306f47047dfec5c11fc49d6ab29b357d1dcb32fb9637da4; repaireded14ea01 returns only guarded GITHUB_WORKSPACE/.treeseed/npm-cache ownership to ordinary packaging UID/GID after scenes, without dereferencing symlinks. Fifteen contract tests passed13.62s,SHA867b8820c89a0c1b4f92130561a1ab807d32db6dc347b8d309036dcd8f0bbe7e;sourcepolicy514passed. Original deadlines/privileges/installation/coverage unchanged. New exact candidate CI pending, merge/hostactivation blocked until complete required job passes. Agent389 is the separate protected native clock binding PR atbd9348b, not yet delivered.

Public inspection nsfs regression and current RAM read-back

Read-only host inspection before activation (SHA2a43042c398c6505706739b87a6f4446dbb8813c20bab0f4354f74e611c45793) retained77mount rows/14valid nsfs namespace roots, but complete:false/owning_mount_inventory_unavailable. Existing parser incorrectly required every filesystem root begin with slash. This is a concrete IMPLEMENTATION_DEFECT; unrelated namespace mounts must remain visible. RegressionDeployment631868e3 reproduces native-shaped net/mnt roots (REDb42fd06ad2d23c144dbcc34a2fbfbbc6e666a9177bcb584c31a989582a2b5de7), and strengthens existing native CLI→manager→supervisor fixture with a held existing host network namespace bind, retained through sandbox-only teardown and explicitly unmounted in owned cleanup. No namespace creation, privilege expansion, caller path/command or new verifier model.

Repaird16db0c910e89ba0734ad7de6cf62980dfb4c86e accepts typed numeric namespace roots only on nsfs; malformed roots/wrong filesystem still fail with raw observations retained. Unit7/7 (SHAdecdc16f78178e12d130f1a060a35ae351ab6786f20ed60b591757e1db529090), strict types/source514 passed; original bounds unchanged. Existing unit/native/component IDs reused. Known-obsolete ed14ea01 CI38043283096 cancellation requested before pushing replacement; it is not reusable passing evidence. New exact native CI required before merge/hostactivation.

TreeDX current public metrics SHA801b4baf7b8dab803d14266cfeefc21df8e3b3c97b63ea6a14b6b4ea53eaf146: actualDocker RAM/memory+swap4294967296 each, healthy,noOOM,169.3MiB observed;runtimebudget4294967296/cachepool939524096/nativecache83390877 of93952409. Cache budget and native use remain inside selected4GiB service budget. Read-only provider status is healthy (SHAb4a971b2e544f49511045bd7956cb0556b578679f2c76546a0b8f598915b08a2); current selected lease observation4725 had0reserved/borrowedworkers, but full current supply and no-active-work gates must be refreshed immediately before any eventual activation. Generic capacity status first page is not a complete lease inventory and is not claimed as such.

Agent389 delivered — protected native model clock wiring

Agent389 sourcebd9348bcd3b36b906f801e23697999810724dac4 ordinary merged to staging18103737cf240e993048a60b79676743ad5de721. Tested36716b055791dbb62da36220bfe7572f79bd14a0 and delivered merge share treef63bbe1b7be72741ce7fd2202ab0927fb96ead12. Required38043125453/job114187184874 and submission validation passed. Fresh Agent943/943 and executingReviewer199/199 preceded667+23=690passingcomponents,0failed/skipped/todo/blocked/diagnostics. Artifact11666716254ZIP28fee6c3b339104bdcf2ef10ede4e00953c93074a194daf2b28c00f636971925;reportec6610bb4d2f3006468781a543380065b9413aeadfd49aa027c4675c93058201;raw603ee2211e8d2665cd5fdc0ef00e52e29be61204c0259e1cccaf27271a3c1472. Clean primary staging FF, old main preserved, only leased delivery remote branch deleted. Existing API native protected observation case now selected once and bound beside Agent clocks for criterion11; actual managed clock proof still pending. Counts remain464/204/26bound/178unbound/260deferred;18SDKscene refs. No managed campaign launched.

PLAN_REVIEW_REQUIRED — repeated installed prerequisite timeout; no launch

Project: SDK execution acceptance, with Reviewer owning installed-package prerequisite proof and Deployment owning the blocked native delivery. Proposal ID/digest: current governed SDK proposal and immutable campaign/freeze authority have not been established; no proposal authority is fabricated. Workday: not started.

Failed expectation: every participating owner must complete all unit/integration assertions on the exact candidate before any scene. On Deployment source d16db0c910e89ba0734ad7de6cf62980dfb4c86e, run38043893278/job114189456667 passed the initial1311 tests, the focused native installed CLI→manager→supervisor namespace-mount inspection, and fresh Deployment1311/1311, but executing Reviewer62d261910f8bd157ba6575b185a586263dff8e44 passed198/199: actual production-installed archive proof failed ACCEPTANCE_INSTALLED_INSTALL_ETIMEDOUT. All233 component scenes were blocked; none launched. Required delivery is failed, not a passing native receipt.

Observed original refs/facts: repeated same installed-install timeout also occurred on38041076055; earlier installed export timeout38038773997 and intervening passing Reviewer199/199 runs remain historical facts. Shared npm cache and scoped ownership handoff have not reliably resolved the timeout. This is at least the third retained unexplained installed-prerequisite timeout across the delivery chain. Original30-second test boundary and5-second closeout remain unchanged. The retained strict artifact contains summary assertion failure but no measured-phase stderr; no exact network/cache/root cause is inferred from that incomplete observation.

Current failed artifact11667061882: ZIP SHA2563b0151b876c9ddc5c8937de4f4c0b0c3e6e1813b548ca1530c44cec0a2158da8; raw job log0099ad13d62ab580fe6659f05acfa97bfb21fe7d9792c092063a371438ac9228. Original artifact and log retained unchanged. Superseded ed14ea01 run38043283096 was explicitly cancelled to conserve verification resources; fresh1311+199 had passed but no terminal scene report existed. Cancelled artifact11667090976 ZIPd8e90e1c5860de3986df6b08da19269010ac5b7443181912e478c30a61a2323c and raw loge04d2f4c4e667cba2f81771a6afca1a1645689c34cc3fc3588257bec6646ee03 are retained, never relabelled passing.

Why another implementation repair is insufficient: no focused observation establishes the next owning defect; repeating the unchanged candidate or speculating about cache flags would not provide useful new evidence. Smallest proposed correction, not applied: preserve safe per-phase timing and original npm failure evidence through the existing prerequisite artifact contract, then reproduce a concrete owning defect without changing archive identity, production dependency closure, watchdogs or acceptance meaning. No alternate runner/model/authority, deadline extension, test skip or host activation is authorized by this status. Stop retries here until that concrete evidence or the missing current campaign authority is supplied.

Deployment869 remains unmerged and unactivated. TreeDX94 and Agent388/389 are delivered separately; their passing receipts do not replace this failed prerequisite. Strict SDK remains464 total /204 selected /26 bound /178 unbound /260 deferred. No managed campaign or later stage was launched.

RAM/cleanup read-back: TreeDX container3231ebf55b11ff2341b8a173f04cff1ad3d1f39e19a50903505d6bdeb5165a61 remains healthy, no OOM, actual RAM and total RAM+swap each4294967296 bytes. Cache pool939524096 bytes is inside that cap; measured cache83390877 bytes retained in current metrics SHA801b4baf7b8dab803d14266cfeefc21df8e3b3c97b63ea6a14b6b4ea53eaf146. Six identified orphan Reviewer proof processes were stopped with scoped process identity checks, freeing approximately512MiB; cleanup SHA d4f9f0bc8987ac5bf8d5c80f734bffe51b9d19d0167231db92fa54fd4b321ecc. No unrelated process, retained lease, quarantine, encrypted data/key or historical worktree was removed. Latest host MemAvailable87553MiB; swap already in use2181MiB is not attributed to TreeDX.

Implementation resumed — Reviewer diagnostic custody first

Human instruction to continue on2026-10-10 resumes bounded prerequisite diagnostics work, without a blind Deployment869 retry. Reviewer116 source1c1119450fe020edacc087a7647c67d7fb7864bf retains actual installed-phase numeric measurements in the existing redacted failed prerequisite receipt. Focused native/unit regression reproduces lost timings;52/52 focused passed. Full local193/199 failed6 native Elixir/OTP cases because this shell lacks that toolchain; source/types/build passed, zero skipped/todo, no local acceptance. Required native CI pending. Original watchdogs, assertions, package custody, TreeDX RAM/cache limits and all failed observations remain. No installation-timeout root cause is claimed from the successful local probe; no Deployment merge/activation or managed campaign launched. Current strict inventory remains464/204/26bound/178unbound/260deferred.

Deployment869 continuation contract: once Reviewer116 is checked and delivered, consume that exact source and place the existing focused actual installed-archive regression before expensive privileged complete suites. It uses the same root user, preserved npm cache and original30s/5s fixture boundary as the later strict prerequisite invocation. A focused failure must stop early; a focused pass cannot substitute for fresh complete Deployment and Reviewer suites before scenes. Strengthen the existing owning workflow contract/scene case first, retain RED, then change the existing workflow and held Reviewer pin. Native public inspection, cache ownership handoff, all full suites,233 scene steps and packaging checks remain required.

Prepared Deployment regression438ded67 and repair (held locally pending checked Reviewer116 delivery): existing workflow contract15/15 passes, strict TypeScript and source policy514 pass. REDc65a2e8e445ae87000c16e245c298c7b07ba0cbeaedd252270a4c6042dc59fa9; passing focus23b2353a70cc7da1054408d7eab0f3e335d49450b6986a8a3fd680a10ec4f361. The focused native package regression runs from the held Reviewer directory before host installation/full verification, retains the existing cache environment, and cannot substitute for complete prerequisites. No native rerun/merge/activation yet. Local command-name mistakes (nonexistent Deployment typecheck/check:source scripts) are retained; corrected direct strict tsc and existing check:source-shape passed. No assertion, native layer or source allowance changed.

Reviewer116 checked delivery

Reviewer116 source1c1119450fe020edacc087a7647c67d7fb7864bf ordinary merged to staging7cef601bc9c8307e57ae6adc974eb82c4008c02b. Required38077281753/job114286793653: initial199 and fresh199/199 preceded113passingcomponents,0fail/skip/todo/blocked/diagnostics. Tested017dc2919b01b4404c779f297f7f9e34c4023e52 and delivered7cef601 share treed63f95097d9775447e28c948f82ec8db0658b7ad. Artifact11679478348 ZIP8d788b8d97c10921c14ae5b048f25d0c40d1a92bf819d740252d9dc231d48911;report4151ea8c5f28692b5fe806acbe9a99b711c8a36037eacf8d2ef79c4e849678ac;raw3ed0d21d44dca41547c6fbd50d59566bc78dab226717e14f10064b1eb85fff55. Clean primary staging FF, old main preserved, only leased delivery remote branch deleted. Diagnostic custody repaired, install-timeout root cause still unproven. Deployment may now consume this exact checked revision and the prepared cheap reproduction; all its fresh native gates remain required. Focused local prefer-offline environment experiment passed actual archive proof in12.37s (a5817c24d74d12fcd102efe2cdab399b084014290b7d36f9e8fc644e24f510b2); not a fresh full suite or CI causal proof, and no product/dependency option was changed.

Replacement Deployment869 sourcea1816e3d4a308152968067ead2d6784f14d304d8 now holds checked Reviewer7cef601 and the early installed-archive regression. Required native run38078447742 is in progress; no duplicate campaign or host activation. Current held source contract15/15 passes (013b0af2ee40f97ae715aba0b288ecc22116e02c84905f2df8a0c984e915264b); earlier3 stale local tooling exact-ref failures retained (293873c6bbc6d0cdd7d2e1bfe60e384f2ce792a4187416c12fcee30877e7cb40), tooling safely advanced/rebuilt without source fallback or assertion changes. Fresh strict plan through delivered Reviewer: SHAfc67066411ca508f9d4479c9380992b7ceaa970ab99734935b712216951a0be5; acceptance document digest unchanged dfb012f90cbfcbf293d520008c752c1ef6f3617c2720e66717c07c8a187b89b3; exact464/204/26bound/178unbound/260deferred identities retained. This is a blocked plan inspection, not a managed acceptance receipt.

Current Deployment attempt stopped cheaply; owning failure now diagnosed

Replacement native38078447742/job114290220635 on a1816e3d failed the early installed-archive reproduction before host preparation, complete owner suites or component scenes. Raw log854b22bd50b1ed2be7d500952f3b10cbc91a6c9883392c10eea36cc87e559b95. Exact observed phases: PACK1463.273ms; INSTALL21818.122ms; dependency export137.553ms; PLAN1353.121ms left142.507ms; EXECUTE145.074ms then ACCEPTANCE_INSTALLED_EXECUTE_ETIMEDOUT. Original work/closeout boundaries unchanged. No fresh full-suite receipt exists for this attempt; all scene stages were never reached. Separate uninstall/secret jobs passed but cannot replace verify.

Classification: IMPLEMENTATION_DEFECT in the owning Reviewer installed-execution fixture: redundant registry metadata revalidation consumes its original verification budget. This is neither an SDK product repair nor permission to relax time/identity constraints. Reviewer98 owns focused regressione29e014: real loopback npm installation of a genuine integrity-addressed archive shows a fresh cached installation still makes1metadata request; RED0cbaa855eca63a60e634e76e48939cfe3f3aa099623516da66dd812a892166db. Repair in progress shares existing test-fixture install flags and uses prefer-offline, with actual production archives/public SDK import, installed byte denials and new native cache scene retained. This supplies a concrete implementation repair after the earlier unexplained-failure stop. No Deployment retry until that exact candidate is checked. Still178unbound; no coded failure-taxonomy or managed acceptance proof claimed.

Reviewer117 candidate5444e64f28c2b999deba76c6416b1b41f1d695c8 now contains the diagnosed cache-revalidation repair. Focused6/6 passed, strict types/source passed; existing unit asset/archive denials and actual installed archive/export proof remain, new native cache case is selected in the existing prerequisite scene. Native complete200 and114components pending; no allowance/TTL/resource/dependency manifest changed. No Deployment retry or managed campaign until checked delivery. Native cache proof cold-fetches a genuine SHA512-addressed archive, then compares exact bytes and identity from a fresh independent cached install with zero metadata/archive requests. It does not mock npm, claim producer/model outcomes or reuse previous prerequisite passes.

Current implementation checkpoint — addressed SDK chat probes, 2026-10-10

Reviewer117 delivered108f153 after required38079091824: initial200, fresh200/200 before114 component results; tested tree unchanged. Deployment869 candidate de47298443bc206080084dc177b3bd92c5673b53 holds that source; native38080201978 has passed the cheap installed-archive reproduction, secret-custody and uninstall-vm, and is running complete native verification. It is not yet merged or activated.

Agent work holds freshly fetched staging18103737cf240e993048a60b79676743ad5de721. The existing campaign opens one all-agent discussion but does not issue eight explicit addressed probes. Scope: focused regression first, then extend the existing admission step using current public communication request/CLI/SDK boundaries; exact proposal/workday/idempotency custody; failures stop the scoped simulation before approval/progress; native HTTP transport and existing component scene coverage. This does not by itself prove model replies, communication accounting, graph-edge invariance or all current governed proposals. Preserve those unbound obligations and every failed observation. No new runner, product role dispatch, allowance or deadline change; no managed campaign launch.

Agent390 candidate442e0d0b8ab0b0dbbe15cf1c5d99186715f50ed7 (base18103737) preserves regression1478a0a before repair. Required native38080784495 is running; fresh complete suites/components are pending. Focused42/42 log0e98b5ac603fcf1c8d4296c6e7c55b8418941ed914efe67bf965a0610d414c02; REDbc6d9f86e1907797b96334b363e0f301d0140b5e0b5f1373454be9d064922629; strict types2742ac3a56066351c2b9e86d5dcce0b6fc55a5c252d22d3f8f4eae87667c49f0; source048aae67935d545ab63ca09288f1a3cf8d627465519f029ccde4fe95953beae4; builddf11e3c3b9c2687f667474606273cf2bdbb53ccc6198d406ad9940bf0ed2c953. The zero-selection initial focused invocation is retained as inconclusive77bec8a2d5162d4b84947555135dd9fbc77892c8aa069f54f2b5d4792697acf4. No managed run or new semantic binding is claimed.

Checked Deployment inspection delivery and selected host read-back — 2026-10-10

Checked native candidate de47298443bc206080084dc177b3bd92c5673b53 passed required38080201978/job114295361233, plus secret-custody114295361220 and uninstall-vm114295361103. Fresh Deployment1311/1311 (prerequisiteff6295cdb95d355906bdf3b764364f211bceabfde63a79c2f5314d92d7b35273) and executing Reviewer200/200 (23ca8fcf6762718b4fdecb2a18c7aa84953828341616f4e16fca603d545779fc) completed before233/233 component steps; zero failed/skipped/todo/blocked/diagnostics. Native installed CLI→manager→supervisor inspection passed with the legitimate nsfs fixture and unrelated resources retained. Original installed-archive reproduction, complete owner verification and verify:deb also passed. Artifact11680128538 ZIP83df6041e76d65087d51787c08784e84f49080361e3897a1761d46089d093a96; report42416a5f7d691da3774f8102c8e67571e8babd30b7186ee9e3a7268de67949eb; raw job38457bf10e0968c0b828fb5e934e6184b4096508bcefe44cca8b1ee712f9406a. Tested merge924f522c5bf36a2816cd149051f5ce96105c4d52 and source candidate share tree79ce0cf65e5a2e190d3c6e7f3aa33e2373d7c88c. Fresh staging remainede7019b86c2f2089ae94541657f4de93ea2687100 and main88c5971910298c43617f1a7c760990ab6146aff6. Checked staging merge and supported current-host activation/read-back remain next; this is no managed SDK physical-absence receipt.

Deployment869 delivered staging52a93abd6bebed0a323bb07785791dc1d9f2a51c with tested tree79ce0cf65e5a2e190d3c6e7f3aa33e2373d7c88c unchanged. Clean primary staging fast-forwarded; local main88c5971910298c43617f1a7c760990ab6146aff6 retained. Only its exact-head temporary remote branch was deleted. Before supported activation, complete created/leased/running assignment pages were empty, provider healthy, independent scoped tasks/containers empty;21 existing managed directories retained. trsd dev host activate /home/adrian/Projects/platform/packages/deployment --json succeeded through the existing manager/supervisor readiness path. Active generationdev-1791661810931-e6d119da, manifestsha256:ee89e32f014168c5186dea9db3d964062d9266b04896c6de7466c631058cd70a. Guestsha256:c5ca5a6a6b7b516fee2dd3aea3390736a20a5996792e4cd2dc9f18cd7f074ef2 unchanged. Public selected-generation status independently scanned1360 actual installed files; every size/digest matched current held source-build bytes. Public sandbox inventory changed from complete:false/owning_mount_inventory_unavailable to complete:true/noerrors, with78mounts and the exact configuration-owned brokerSocket; all21 managed directory entries unchanged and unrelated resources retained. Activation resultSHAfebec06b173bf43e7a5996b881a83ff4315afab9d777e091d7631e171af2edc8; before-inspection661132c9340ebe0c89d9581fd6fc25b15b1cd5262c055d7e1ca3da4e7cdf04a3; after-inspectiond39863dcaaf79a76f2c35d89db70a2d20373e6e8e1173e845480e872ab47da89; installed-byte status38cd28b44e90f4b66e8f2330caea115566d403dcd6fa5ba6eaa0cb8bdd1ca577. TreeDX container unchanged/healthy, RAM and RAM+swap4294967296each,171.3MiB usage/noOOM. No SDK workday was launched; these native/public host observations are not an exact-workday managed physical-absence receipt.

Current strict plan (owning Reviewer working directory) SHA65640b84961fb898074ecee1e53076afcedbb058708c8ce1b1cbd7943970cc4e retains464total/204selected/26bound/178unbound/260deferred; exact selected/deferred identities equal the previous held plan. An initial Platform-root source invocation could not resolve its undeclared tsx loader and produced no plan; the corrected owning-package invocation returned the expected blocked plan, never a passing acceptance. Agent390 native38080784495 remains in progress on442e0d0; no managed campaign started.

Next API owning change — normal SDK clean-schema applicability, 2026-10-10

Fresh API staginga5451539929c33d00bbdf2b42337a34425555be0 is held; main93563a71831659860bfd04fc4e366bae73b9c384 unchanged. The existing managed clean-schema case additionally requires actual nonzero governed priority and historical calibration samples. Those advanced native control requirements must remain intact in their original architecture case, but do not fit the fixed normal cold-start/default-zero SDK proposal. Scope: move their existing sample assertions intact into the existing owning helper; reproduce the normal zero-sample denial; add a separate normal SDK named case sharing all canonical SQL/public inventory, migration, schema, admission replay and immutability assertions. Only the original architecture case requires the additional nonzero sample minima. Validate malformed counts/modes, unchanged retry and independent native PostgreSQL reads; preserve original120s/500line bounds, original case/IDs and advanced native coverage. No proposal priority/estimate changes, alternate authority, SDK product repair or premature semantic binding. Required native owner suites remain mandatory; missing local PostgreSQL is unproven, not a skip/pass.

Checked addressed-probe driver delivery — 2026-10-10

Agent390 exact source442e0d0b8ab0b0dbbe15cf1c5d99186715f50ed7 passed required38080784495/job114297074663 and submission validate on that head. Fresh Agent946/946 (e7e6d7809ce99606906f2c1a39d3c59d6259f934128507dcc6a19a62d364f4b7) and executing Reviewer200/200 (28df9591eeb1325e56883446d6cda4721f8ed3ea9d7d20c21f04153d3bb8174e) completed before693/693 component steps; zero failed/skipped/todo/blocked/diagnostics. Artifact11681285667 ZIP42d036908136b21c915110d3a4d11b0143b33075109ceb647fbd832347e812a2; reportf4db6642b988b337feba7942a17506b2356a9a3aa205304064a3afe1e2d5ffe1; raw job25406ef9757e3af9089bd93a03802a9a2289530c56dd4cede3c69729bbb67de9. Actual packed Agent artifact11680454775 ZIP8fe13ca940f3073e70226012de5f6b7e4e57fd7717a13454de7ab28ef4dc0cd6 contains treeseed-agent-0.13.0-rc.57.tgz SHAf7f1a13e360f159a33d106a6d5441147e882650df60d79ee1f0b9e6c7ed2aa1c. Tested mergef6d6620160036d187a24ccbc77b92b0d004c99c2 and source share tree7fe3b2625344a89250f98d43696f32449f1e62ac. Fresh staging18103737cf240e993048a60b79676743ad5de721 and remote main5d276fe10183a893fed6f6079c68cd14d5a240d8 verified. These bounded driver/native component proofs do not establish managed model replies, producer completeness or graph-edge invariance;178 selected criteria remain unbound.

Agent390 delivered staging6dc791fffed3f160471f02c4b59d3c64eb45b5ad with tested tree7fe3b2625344a89250f98d43696f32449f1e62ac unchanged. Primary staging clean/fast-forwarded; old local main92394bb526714f02db6b092614f95768ea45a846 retained. Only exact-head codex/sdk-addressed-chat-probes-368 remote branch deleted. This is checked acceptance-driver delivery, not a managed SDK chat/model/graph pass. No runtime campaign or SDK product change was made.

API normal-schema work holds basea5451539. Behavior-preserving extraction5d08f878 retains the original sample assertions; regression86128530 reproduces ACCEPTANCE_PRIORITY_EMPTY for normal zero-sample context. Repair is in progress; no API candidate push, native integration pass or managed clean-schema binding is claimed yet. The original architecture case/sample minima remain retained.

API normal SDK schema applicability — PR #530, 2026-10-10

API treeseed-ai/api#530 holds source faa50c8257822047fa1292e822b3694832653d98 on freshly fetched staging a5451539929c33d00bbdf2b42337a34425555be0. Behavior-preserving extraction 5d08f878, RED regression 86128530, then repair faa50c82. Separate normal SDK case reuses the complete original migration/native-public inventory/independent replay/immutability/retired-CLI proof; original architecture case retains both required nonzero priority and historical calibration minima. Two registered unit cases cover scope/count denial and preserve original minima; existing two-connection native PostgreSQL case now verifies actual cold-start allocation and immutable concurrent public rereads. New managed case registered but not selected or newly bound yet. Reviewer action pinned at checked 108f153b.

Local Node24.12: focused 11/11, strict declaration build, source-length/architecture and diff checks pass. Native PostgreSQL unavailable locally; required native CI pending, no skipped substitute. Additional default test-inclusive TypeScript check fails with identical 96 baseline/candidate diagnostics; no new diagnostics and no suppression. Full PR body holds exact commands and SHA256 evidence. Expected fresh CI API2023 + Reviewer200 before834 components and all original native TreeDX/PG prerequisites; actual checked artifacts must establish totals. Strict SDK remains464/204selected/26bound/178unbound/260deferred; no readiness/campaign/pass claim. No new worktree/local feature branch, product fix, release, tag or runtime activation.

Next bounded Agent monitor regression — original lifecycle clock ordering

Classify as IMPLEMENTATION_DEFECT in acceptance observation: live canonical records currently check admission/deadline and retain previously supplied clocks, but do not reject a newly supplied start before creation or finish before creation/start. Candidate will first reproduce this missing clock-order rejection, then strengthen the existing configured Kernel/Git/public SDK transport case and selected component wiring before repairing the owning live monitor. Scope is original observed interval and immutable terminal clock custody, not producer completeness or model/graph authority. Late failed closeout observations remain retained without extending the original execution deadline. Base held at freshly fetched Agent staging 6dc791fffed3f160471f02c4b59d3c64eb45b5ad; API530 native CI runs independently. No campaign/runtime mutation.

Agent treeseed-ai/agent#391 now holds regression add0d7191de24226d799c4e297c03f4a51361e8c and repair 31aa2d86918b404007090faa128801ecad4d50f1 on 6dc791fffed3f160471f02c4b59d3c64eb45b5ad. Unit RED and original native Kernel/Git/SDK transport RED both retained; after repair focused7/7 and related composition43/43 pass with zero failed/skipped/todo. Types/source/build/diff pass. Existing native component case strengthened, two unit cases registered; fresh full Agent/Reviewer prerequisites and all component checks pending required Actions. Exact evidence hashes/commands/limits in PR body. This proves observer clock-order denial, not complete producer histories/graph/model clocks/usage or a managed SDK outcome. Temporary HTTP/Kernel resources closed; no runtime activation, campaign, local feature branch or new worktree.

Confirmed invocation handoff defect — next dependency before managed launch

IMPLEMENTATION_DEFECT: Reviewer executes each selected Node verifier in a distinct owned process (src/verifiers/guarantees/command.ts + node-case.ts). Agent campaign sets TREESEED_ACCEPTANCE_WORKDAY_ID only in its own test child. Selected profile/context/graph/record/physical Agent cases and API protected-observation/normal-schema cases require that ID in later isolated children, which cannot inherit the mutation. SDK's proposal lookup fallback does not carry identity to those owners. No live attempt was needed or launched to discover this.

Bounded repair will retain the existing API-issued treeseed.workday-start-receipt/v1 beside the immutable SDK freeze, then resolve the exact observed ID from that receipt and validate its preflight identity/digest, original public workday/proposal/team/mode/start. Preserve explicit-ID advanced/continuation/controlled-failure cases, reject conflicting/foreign/missing/malformed/redirected receipts, retain original bytes through duplicate/concurrent capture and interruption, and stop the already admitted exact simulation on capture/read-back denial. This reuses API receipt authority and existing acceptance input/evidence storage; no second run model, runner, role rule in Reviewer or SDK product defect repair. Regression/native isolated-child proof and owning component coverage must precede source repair and fresh CI. Agent391/API530 held candidates remain unchanged while their current required native checks finish; integrate this follow-up from their checked staging deliveries. Aggregate actual archive install remains separately unproven (different existing exact SDK dependency pins must be reconciled against held artifacts rather than silently substituted).

Agent391 checked delivery

Checked native CI https://github.com/treeseed-ai/agent/actions/runs/38083844224 / verify job114306099030 passed with submission validate. Tested merge 29d01929dcf6f5fae8f62d97d3549839ab4d41de, tree db1d1e98383d9fb1c91eb35e6d8c46cd1367694f, exact source 31aa2d86918b404007090faa128801ecad4d50f1, fresh base 6dc791fffed3f160471f02c4b59d3c64eb45b5ad. Strict protection requires verify with current base; zero required human approvals, admins enforced. Fresh Agent948/948 (20:30:42–20:32:10 UTC) and executing Reviewer200/200 (20:32:10–20:34:23 UTC) preceded all672 component +23 planning/recovery steps. Zero failed/skipped/todo/blocked/diagnostics. Fresh prerequisite report SHA256 Agent 22a6a2feb43c1267d354021a406bed7f753ab5d27c01df082358c2114e97ecd8, Reviewer 525ba84e0aa1d362b75d275d6ada3a03efacea2f79a885d623ae0219fa0c82a9. Scene artifact11682105588 ZIP ce2972dfc2c50dcede3075dfb03b3d5046348eee24532436337b918fec6fc6f8; report 2a3de2a6b1fb5c7601f427311ea136bfeca92925c74fdfdde3199527bace4fde; raw job log 7ac1504dd1a530649d260100f699c75639e17393ed580e73a1c06c1f8bf5c716. Package artifact11681876018 ZIP e44f8f88230ae1e77d1ff74394724adf85cdd45a065d0c4732e3b64cf5856682; actual treeseed-agent-0.13.0-rc.57.tgz bc352e92c30e27e082cbd4b9e5e26d72a45b6d6bde3a77136127b80ad34af122. Managed SDK acceptance and178 unbound criteria remain unproven; this delivery repairs only the observer clock-order defect.

Ordinary staging merge delivered 5acc2b2bd8845db6370c8d6482f133cafff569af; its tree equals tested merge 29d01929 exactly (db1d1e98383d9fb1c91eb35e6d8c46cd1367694f). Clean primary staging safely fast-forwarded, historical local main 92394bb526714f02db6b092614f95768ea45a846 retained. Only this delivery's temporary remote branch deleted under exact 31aa2d8 lease. Existing worktrees/history preserved. Next bounded issue is actual WorkdayStartReceipt handoff across isolated verifier processes; no campaign launched.

Agent isolated workday receipt repair — held source 9f6617cec473229f7046fe32a31f675b139e3975

Reviewer launches isolated verifier children; the campaign's child environment assignment cannot identify later Agent/API/SDK children. Agent 5acc2b2bd8845db6370c8d6482f133cafff569af → refactor d86415628d7a1bee081fd9c26bacdd3dde4f66e1 → RED 8a19cffc6363814f40d8f24b5b34a0d1fd042008 → repair 9f6617cec473229f7046fe32a31f675b139e3975. Reuse the existing API v1 start receipt beside the unchanged freeze, exclusive fsynced capture and scoped public run read-back. Capture denial stops the actual admitted simulation before discussion/approval. Selected Agent consumers share the original receipt; advanced explicit IDs retained. No second runner/model or product repair.

Regression: 2 failed / 0 skipped, log SHA256 550ab5705055fb165be69dfd09fc12218d2d883f9462bd8ebb8d937c4308d005. Final local pinned Node 24.12.0, original Platform authority e4c4cad1e526f53d3549c8fc27c3e60122b20ee4: all guarantee tests 95/95 (877e99dfac6ffc719a9c09150db1a9d4f3b962e8416df2d8cf41aaa6bc9712ad), typecheck, source limits/architecture, build and diff checks passed. Three unit cases, native public SDK/HTTP isolated-process/concurrent/interrupted writer/denial/retry case and exact scoped-stop composition case mapped to five component scene steps. Controlled API responses are not native producer or managed proof. Original failed fixture/environment/architecture observations retained.

Required Actions with fresh complete owner prerequisites before component scenes remains pending; API and SDK consumers follow separately. Current strict 464/204/26/178/260 unchanged. No campaign launched, no SDK readiness/pass, no binding credit added. Owned test subprocesses/sockets/temp roots terminated/closed/removed; live development selections,34 leases,worktrees,encrypted data and keys retained.

Agent receipt handoff PR: treeseed-ai/agent#392, held head 9f6617cec473229f7046fe32a31f675b139e3975, pending required native checks before staging delivery. PR description retains exact regression-first lineage, commands, log digests and five-case component mapping. No managed invocation.

Agent #392 replacement source 12cc083996cb5e169fa3b5830b381cd0fa6e6c2f: initial required run 38086683620 failed before scenes because 93 read-back assertions shared invalid synthetic ID workday-test. Existing shared fixture now uses a valid synthetic UUID; all negative cases and strict guards retained. Seven affected read-back files plus all guarantees passed 199/199, zero skipped (SHA256 59103810b11985f2925e0b32d7fd9ed1e297363b97f89c0bd7b996197c05e585), typecheck/diff passed. Failed job114314543698 retained; no CI rerun or passing receipt reuse. Replacement push requests normal fresh Actions; staging delivery still pending.

SDK exact API workday handoff — held source f6d20d9

Base 64f25a0 → behavior-preserving extraction14c4e5138e6d309af3abee8c92a825170ce3a0b5 → REDf93e445b3d0e1aae713133ca53e097705ae85629 → repairf6d20d9ac593836b7f14dda0c3be81dc5d4d0212. SDK acceptance now consumes the original API v1 start receipt beside the unchanged freeze and independently verifies public exact workday/preflight/team/start/proposal/project authority; proposal-list fallback removed. No SDK product/non-enumerable field implementation changed. Three unit/native cases selected by existing component registry/scene; current checked Reviewer108f pin and owning exact-pin test updated together.

RED2failed/0skipped (SHA256 af06ab6d9f0e354f512751fbfca02a5cb9a3eafa2857f76c3712c45d2e285004); related99passed; release:verify includes complete570passed/0skipped plus strict build/standards/source rules (885b31ec7960ac29a251077968bb42a08213323d651a357b25ee09e970a4fea2). Actual npm pack + standards:acceptance archive passed440files/66exports/213declarations, archiveSHA29d48f3d39b3c6425ba63aa14933ce8c6c343607687a30b775c1fe47d7a462d9; this precommit local archive is packaging evidence only, not final candidate/installed custody. Fresh required Actions with SDK+Reviewer complete prerequisites before component scenes pending. No managed campaign, no bindings credited,178unbound unchanged. Native test children/sockets/temp roots cleaned and original older root archive retained.

SDK receipt consumer PR #390, held source f6d20d9; required current-candidate Actions pending. Agent #392 replacement pending. API #530 remains in required native component scene verification; none of these three candidates merged or activated during this checkpoint. Read-only cleanup audit finds zero remaining handoff-test subprocesses.

SDK #390 candidate checked: required38087335147/job114316466296 +validate114316468480 pass. Exact tested merge8b2e5883026bb97f035faa2385898ca0dd6c5688, treeaece6eaead8792c845b1310679768ee118d21840; fresh SDK570/570 and Reviewer200/200 before223component+16custody=239steps, zero failures/skips/todos/blocks/diagnostics. All three new receipt cases and archived assets/definitions match tested source. Sceneartifact11681879764 reportSHA16cee3130c1ae14d486b04ea60af21f549ab9edda3b4713a55fad0cda0647ed1, packageartifact11682009565 actualarchiveSHA319a8e2a0b02ff2eae648c02293f254ae7622eebd411e82209143f16eadb2a2b; fresh receipts/raw logs/ZIPs retained and recorded in PR body. Ordinary staging merge/read-back pending; no combined installed custody or managed pass,178unbound retained.

SDK #390 delivered by ordinary staging merge c5a9936; parents64f25a0a162e0a30735dd07ca0a9ef16174914b8/f6d20d9ac593836b7f14dda0c3be81dc5d4d0212, treeaece6eaead8792c845b1310679768ee118d21840 exactly matches tested merge8b2e5883026bb97f035faa2385898ca0dd6c5688. Fresh protected read-back, clean local staging fast-forward and exact-lease deletion/absence of only codex/sdk-workday-receipt-387 passed. Historical local mainfc67674caf11218f5f9b5690f1ea8f26e8e4d070 preserved. Required38087335147 freshSDK570/Reviewer200 before239component/custodysteps and fresharchive319a8e2a0b02ff2eae648c02293f254ae7622eebd411e82209143f16eadb2a2b retained. PR body read-back records full Actions artifacts/digests. No release/publication/runtime activation or managed campaign. Agent392/API530 still pending;178unbound unchanged.

Agent392 checked replacement12cc083996cb5e169fa3b5830b381cd0fa6e6c2f: required38087126503/job114315861541 passed; fresh953Agent+200Reviewer complete prerequisites before677component+23planning/recovery=700steps, zero failed/skipped/todo/blocked/diagnostics. Testedmerge92c884fc6ac23a09d6dcbc0649feb2537cd61a15/tree2e53f0fa1a8c44c702a01bf4e0cd37542cc3857f; all5newcases+11shippedassets match source/archive. Sceneartifact11683250897 reportSHAdaa0875240b0b05b4cca4f654cc29580ef2fcb6983775a1c7c46a641497028c7; packageartifact11683835469 actualtgzSHA053e0b82b368caccf93738e88f21968b142f1d6115ac7c116a558361da255303. Initial stale-body validate114315857840 retained (logSHA3cdfa158f3562aab9a28728931859f788e0e07e42ca42ba3dd4d163972168cc5); corrected later114315932057 passed on the same source. Earlier93fixture failures/run38086683620 retained. Ordinary staging delivery pending; no managed pass/binding credit.

Agent392 delivered by ordinary staging merge5cffc5725e7ab3ec6186437914dc0ea021b2c8dd, parents5acc2b2bd8845db6370c8d6482f133cafff569af/12cc083996cb5e169fa3b5830b381cd0fa6e6c2f, tree2e53f0fa1a8c44c702a01bf4e0cd37542cc3857f identical to testedmerge92c884fc6ac23a09d6dcbc0649feb2537cd61a15. Required38087126503 fresh953Agent+200Reviewer before700component/planningsteps and exactarchive053e0b82b368caccf93738e88f21968b142f1d6115ac7c116a558361da255303 passed/audited. Corrected latestvalidate114321456200 passed; both historical failures retained. Protected read-back/safe clean local staging FF/exact-lease deletion and absence of only codex/sdk-workday-receipt-handoff-368 passed. Historical main92394bb526714f02db6b092614f95768ea45a846, allworktrees/34leases/keys preserved. No runtime activation/release/campaign. SDK390 also delivered; API530 still verifying;178unbound unchanged.

API530 checked: required38083425841/job114304850513, authorization114304851408 and validate114304851752 passed on testedmerge6444aa4f8e9fcc70be92e848aba4cb1f1ffb3b12/tree7d361ee87640a93b509d456f76452e6b1fe5d832. Fresh2023API+200Reviewer complete prerequisites before834passingcomponentsteps, zero failed/skipped/todo/blocked/diagnostics. Bothnewcases+4shippedassets match held source/archive. NativeTreeDX/allSDKs, signedloopbackservice, realPGmigration/identity/concurrentallocation supplements and servercleanup passed; raw native logs are supplemental, not strict managed invocation receipts. Sceneartifact11683332825 reportSHA4e83b798fcaf1fa998c505f19f77034d2e68d0889ed03f50c9b61a797a5b8c42; packageartifact11683737540 archiveSHA065831b36166f01db5ed53d400ea6e59cc7dd8084168772ff87c02befee3c64d; native11683432622/source11683082928/rawlog digests recorded in PR. Ordinary staging delivery pending. New normal SDK schema case stillunselected untilreceiptconsumer integration;178unbound unchanged.

API #530 delivered read-back

Delivered by ordinary merge as f56549966f9781d7193a39007191806293d83b7c; delivered tree 7d361ee87640a93b509d456f76452e6b1fe5d832 exactly matches checked merge 6444aa4f8e9fcc70be92e848aba4cb1f1ffb3b12. Fresh protected-head read-back and parent verification passed; the clean local staging checkout was safely fast-forwarded, historical local main retained. Only this delivery's codex/normal-sdk-clean-schema-515 remote branch was deleted with the exact source lease and absence verified. The new normal managed schema case remains unselected pending receipt-consumer integration and semantic binding review. This is component delivery, not SDK launch readiness or a managed passing receipt.

API original workday-start custody implementation — API #531

Outcome

Bind isolated API managed schema and protected-observation verifiers to the original retained API workday-start receipt, its exact scoped PostgreSQL operation record and public completed workday. Child-process environment mutation cannot provide this invocation authority. Reuse the existing receipt and inventory helper; no run discovery, new authority or production API rewrite.

Work authority

• Work item / Issue: API #515; implementation continuation Complete strict SDK capacity-provider and agent acceptance bindings #387.

• Proposal / decision: User-approved strict capacity-provider and agent-execution acceptance implementation plan.

• Assignment / checkpoint: Original workday-start custody across isolated managed verifier processes.

• Actor: Codex.

• Human authority: adrianwebb, explicit implementation authorization.

• Agent / capacity provider: Codex desktop; no simulated provider proof claimed.

• Exact base ref: staging f56549966f9781d7193a39007191806293d83b7c.

• Exact head ref: codex/api-workday-start-custody-515 a97e46f87bbabb38691d47811a0f3e9e871036c7.

• Agent-authored under human authority

Plan

Regression first, then use the original ten-field v1 receipt at the immutable freeze sidecar. Reject missing/malformed/redirected/unreadable files, conflicting explicit IDs, foreign preflight/public authority, incomplete original inventories, changed bytes and ambiguous native records. Query the original team/operation/resource/idempotency scope, compare the complete cached response and owning canonical request digest, and retain two-connection immutable schema rereads. Advanced non-SDK cases retain their explicitly supplied IDs. Original 120-second observation bounds remain unchanged.

Changes and commits

• 444dd8d0: behavior-preserving extraction of shared explicit input resolution; related 5/5 passed.
• be5064d4: committed RED reproduces missing isolated-child ID despite retained original receipt; 1 failed, zero skipped; log SHA256 ca712a5c632e1e3570fa438c9560f3c1a55e775b70443a00386485cfe6fca1d9.
• a97e46f87bbabb38691d47811a0f3e9e871036c7: receipt resolution, exact native/public custody, byte immutability and four selected component cases. Both existing managed observation functions consume the helper; the new normal SDK schema case remains unselected pending integration review.

The actual owning public producer additionally exposed a consumer contract defect: API SHA-256 uses base64url, not hexadecimal, and the stored start request digest has the original sha256 prefix. This change compares that original representation exactly. Coordinated Agent/SDK consumer regressions are being repaired separately; no SDK product defect is externally fixed.

Behavior-to-proof mapping

• Unit: execution-start.test.ts proves original isolated input, malformed/missing/foreign/conflicting authority, file denial/redirect, incomplete/duplicate response, exact public authority, original errors, mutation denial and unchanged retry.
• Real owning integration: the same file invokes the existing public preflight/start fixture, reads the producer's actual cached response and exact replay. Its SQL/TreeDX HTTP inputs are controlled; it does not prove native concurrent PostgreSQL or actual governed campaign authority.
• Native PostgreSQL: execution-start-postgres.test.ts requires disposable loopback PostgreSQL, all original migrations, independently observed backend PIDs, four concurrent read-backs, scoped denial, actual in-flight command cancellation, exact retry and unchanged native/retained bytes. Start inputs are controlled, not producer completeness or a managed campaign.
• Scene: four named cases registered in the original component scene. Managed schema/normal schema/protected observations reuse the original complete verifier paths. No scene was launched locally without fresh complete prerequisites.

Validation

Pinned Node 24.12.0. Related five files: 31/31, zero failed/skipped/todo; log SHA256 e57fb9cf31a65d30016da9d6dbbe48f48fc33dbd2c7acb1655729f45eed4222d. Source/architecture policy and strict build: pass, log SHA256 fbacdb40e05886248ba25f8dd07cbbcc13f56a62c46de1ec310762c967038810 / 14d9a4d3da9b8735b37a1290645b0e065d45c6c4b59fe370351fcd06cf6db937. Existing test-inclusive default typecheck retains the 96 baseline diagnostics, none in changed files; it is not a passing typecheck (SHA256 bdfcca3b41d654a44ed087365766e5393dcefff441825c21365ae6c2f0230ad9). Local native PG case failed explicitly for missing TREESEED_TEST_POSTGRES_URL, not skipped or substituted (SHA256 8c2b0a8deed917130dd72b37d4093a307952ef811113c251ba476a7089b6f871). Required native Actions and fresh API/Reviewer complete prerequisites before component scenes remain pending.

Boundaries and cleanup

No managed invocation, runtime activation, SDK product repair, source fallback, publication, release or deadline change. Controlled fixture roots/connections/server close in finally; historical failures, worktrees, leases and keys retained. All 260 deferred identities remain; strict binding count is still 26/204. Ordinary checked staging merge and exact-tree read-back only after required Actions and artifact review.

Producer digest contract correction — Agent #393

Outcome

Consume the API producer's original base64url SHA-256 receipt digests during SDK campaign capture and isolated read-back. The prior hexadecimal-only guards rejected real v1 receipts even though synthetic hexadecimal fixtures passed. Retain the original receipt shape, exact frozen digest equality, file custody, public authority and scoped-stop behavior.

Work authority

• Work item / Issue: Agent Promote verified capacity-provider endpoint validation through staging #368; implementation continuation Complete strict SDK capacity-provider and agent acceptance bindings #387; coordinated producer/consumer proof Bind managed API verification to original workday-start custody api#531.

• Proposal / decision: User-approved strict capacity-provider and agent-execution acceptance implementation plan.

• Assignment / checkpoint: Repair producer-to-consumer workday-start digest contract before managed execution.

• Actor: Codex.

• Human authority: adrianwebb, explicit implementation authorization.

• Agent / capacity provider: Codex desktop; no simulated provider proof claimed.

• Exact base ref: staging 5cffc5725e7ab3ec6186437914dc0ea021b2c8dd.

• Exact head ref: codex/api-receipt-digest-368 6614478e4ab122bdd31859b354ed9a062f327800.

• Agent-authored under human authority

Changes and proof

• 516398a: regression first; controlled fixtures now generate actual SHA-256 base64url values using Node crypto, matching the owning API security function. Existing three receipt cases all failed before repair, zero skipped; retained RED log SHA256 10782721c787b5909e8803d9637893d8aa8592c0fb348a810f20e332a5a6365d.
• 6614478e4ab122bdd31859b354ed9a062f327800: two exact-format guards corrected to the original 43-character base64url representation. Additional malformed-length, punctuation and wrong hexadecimal-representation denials preserve failed bytes and no receipt creation. Every previous negative remains.
• Unit: original selected receipt positive/denial/read-back cases.
• Real integration: original selected native SDK HTTP/child-process receipt case now carries the producer's digest representation through capture, four concurrent retained writers, interrupted child, foreign public reads, denial and exact retry. Inputs remain controlled; this is not PostgreSQL producer completeness or a real campaign.
• Scene: original five workday-start component cases retain their IDs and selection. The actual public API producer integration in API #531 independently confirms preflight/start encoding, stored response equality and exact replay.

Validation

Pinned Node 24.12.0 and unchanged retained Platform authority /tmp/sdk369-platform-authority-de2LzF. All guarantees tests 95/95 across 16 files, zero failed/skipped/todo; SHA256 9b15018ca6d47a3a54581b95b255b2e624ed5bbbe4af2993ed8250fddd794293. npm run typecheck, npm run check:file-lengths (including architecture) and npm run build:dist passed. Required fresh complete Agent/Reviewer suites, component scenes and candidate package artifacts remain pending Actions; no scene was launched locally.

No production runtime/product changes, compatibility path, new digest implementation, runner, schema, runtime activation, managed invocation, deadline changes or SDK product repair. Test children and temporary roots close through the existing native finally paths. All historical failed evidence, leases and worktrees retained. Strict binding count remains 26/204; this repair is not launch readiness. Ordinary staging merge/read-back and exact temporary branch cleanup follow required automated verification.

Current receipt-consumer delivery contracts — supersede the earlier pending candidate metadata

API #531 final source 52449d4b1ca430fb507a2cf95c1a27281816b563; original candidate's superseded run 38090763999 was explicitly cancelled to conserve native CI capacity, retaining its failed submission observation. Normal-SDK explicit-only RED SHA256 3fbf12d5322723348f9b8b292fbf93a9a01d9224410c4d1c48ec35c9f876d595; final 8/8 focus SHA256 9fc22cd3b304c7292ee5f320e2218666e0fe9b9a7f8ee231ecb78caa50ba2891. No passing receipt is inferred from cancelled work.

Outcome

Bind isolated API managed schema and protected-observation verifiers to the original retained API workday-start receipt, its exact scoped PostgreSQL operation record and public completed workday. Child-process environment mutation cannot provide this invocation authority. Reuse the existing receipt and inventory helper; no run discovery, new authority or production API rewrite.

Work authority

• Work item / Issue: API #515; implementation continuation Complete strict SDK capacity-provider and agent acceptance bindings #387.

• Proposal / decision: User-approved strict capacity-provider and agent-execution acceptance implementation plan.

• Assignment / checkpoint: Original workday-start custody across isolated managed verifier processes.

• Actor: Codex.

• Human authority: adrianwebb, explicit implementation authorization.

• Agent / capacity provider: Codex desktop; no simulated provider proof claimed.

• Exact base ref: staging f56549966f9781d7193a39007191806293d83b7c.

• Exact head ref: codex/api-workday-start-custody-515 52449d4b1ca430fb507a2cf95c1a27281816b563.

• Agent-authored under human authority

Plan

Regression first, then use the original ten-field v1 receipt at the immutable freeze sidecar. Reject missing/malformed/redirected/unreadable files, conflicting explicit IDs, foreign preflight/public authority, incomplete original inventories, changed bytes and ambiguous native records. Query the original team/operation/resource/idempotency scope, compare the complete cached response and owning canonical request digest, and retain two-connection immutable schema rereads. Advanced non-SDK cases retain their explicitly supplied IDs. Original 120-second observation bounds remain unchanged.

Changes and commits

• 444dd8d0: behavior-preserving extraction of shared explicit input resolution; related 5/5 passed.
• be5064d4: committed RED reproduces missing isolated-child ID despite retained original receipt; 1 failed, zero skipped; log SHA256 ca712a5c632e1e3570fa438c9560f3c1a55e775b70443a00386485cfe6fca1d9.
• a97e46f87bbabb38691d47811a0f3e9e871036c7: receipt resolution, exact native/public custody, byte immutability and four selected component cases. Both existing managed observation functions consume the helper; the new normal SDK schema case remains unselected pending integration review.

The actual owning public producer additionally exposed a consumer contract defect: API SHA-256 uses base64url, not hexadecimal, and the stored start request digest has the original sha256 prefix. This change compares that original representation exactly. Coordinated Agent/SDK consumer regressions are being repaired separately; no SDK product defect is externally fixed.

Behavior-to-proof mapping

• Unit: execution-start.test.ts proves original isolated input, malformed/missing/foreign/conflicting authority, file denial/redirect, incomplete/duplicate response, exact public authority, original errors, mutation denial and unchanged retry.
• Real owning integration: the same file invokes the existing public preflight/start fixture, reads the producer's actual cached response and exact replay. Its SQL/TreeDX HTTP inputs are controlled; it does not prove native concurrent PostgreSQL or actual governed campaign authority.
• Native PostgreSQL: execution-start-postgres.test.ts requires disposable loopback PostgreSQL, all original migrations, independently observed backend PIDs, four concurrent read-backs, scoped denial, actual in-flight command cancellation, exact retry and unchanged native/retained bytes. Start inputs are controlled, not producer completeness or a managed campaign.
• Scene: four named cases registered in the original component scene. Managed schema/normal schema/protected observations reuse the original complete verifier paths. No scene was launched locally without fresh complete prerequisites.

Verification

Pinned Node 24.12.0. Related five files: 31/31, zero failed/skipped/todo; log SHA256 e57fb9cf31a65d30016da9d6dbbe48f48fc33dbd2c7acb1655729f45eed4222d. Source/architecture policy and strict build: pass, log SHA256 fbacdb40e05886248ba25f8dd07cbbcc13f56a62c46de1ec310762c967038810 / 14d9a4d3da9b8735b37a1290645b0e065d45c6c4b59fe370351fcd06cf6db937. Existing test-inclusive default typecheck retains the 96 baseline diagnostics, none in changed files; it is not a passing typecheck (SHA256 bdfcca3b41d654a44ed087365766e5393dcefff441825c21365ae6c2f0230ad9). Local native PG case failed explicitly for missing TREESEED_TEST_POSTGRES_URL, not skipped or substituted (SHA256 8c2b0a8deed917130dd72b37d4093a307952ef811113c251ba476a7089b6f871). Required native Actions and fresh API/Reviewer complete prerequisites before component scenes remain pending.

Boundaries and cleanup

No managed invocation, runtime activation, SDK product repair, source fallback, publication, release or deadline change. Controlled fixture roots/connections/server close in finally; historical failures, worktrees, leases and keys retained. All 260 deferred identities remain; strict binding count is still 26/204. Ordinary checked staging merge and exact-tree read-back only after required Actions and artifact review.

Final normal-SDK input gate

Review exposed a second gap: the normal SDK case could accept an explicit advanced-case ID without its original retained receipt. Committed regression b2eb0fde reproduced that omission (1 failed, 2 passed, zero skipped), then 52449d4b1ca430fb507a2cf95c1a27281816b563 requires the retained input for the normal SDK scope and rejects unknown scope values. Latest focused three files pass 8/8, including the real public producer. Default typecheck's 96 diagnostics normalize identically to the retained baseline, with no new-file diagnostics. The initial API #531 submission check failed because required PR-template headings/checklists were omitted; this description repairs the metadata and preserves log SHA256 40a1fc0940fc160a822eba858e6445dbbfaa659f46985d8b7f8d00b59f819a98. Initial source candidate is superseded, never passing final-candidate evidence.

Risk and rollback

Acceptance-only read-boundary repair; no production data migration. Recover through an ordinary checked PR with git revert --no-commit f56549966f9781d7193a39007191806293d83b7c..52449d4b1ca430fb507a2cf95c1a27281816b563, commit, run required verification and integrate ordinarily. Reverting restores the isolated-ID gap and blocks SDK launch.

Completion summary

Implementation, focused regression, real owning producer integration and strict build/source checks complete. Native PostgreSQL and fresh complete API/Reviewer prerequisites/component scenes/package audit remain pending required Actions. No managed acceptance or readiness claim.

AGPL committer authorization

The unchanged base-owned workflow verifies provider-authenticated adrianwebb against the existing approved-committer policy. No grant attestation, identity spoofing or policy change.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.

Agent #393 final submission contract

Outcome

Consume the API producer's original base64url SHA-256 receipt digests during SDK campaign capture and isolated read-back. The prior hexadecimal-only guards rejected real v1 receipts even though synthetic hexadecimal fixtures passed. Retain the original receipt shape, exact frozen digest equality, file custody, public authority and scoped-stop behavior.

Work authority

• Work item / Issue: Agent Promote verified capacity-provider endpoint validation through staging #368; implementation continuation Complete strict SDK capacity-provider and agent acceptance bindings #387; coordinated producer/consumer proof Bind managed API verification to original workday-start custody api#531.

• Proposal / decision: User-approved strict capacity-provider and agent-execution acceptance implementation plan.

• Assignment / checkpoint: Repair producer-to-consumer workday-start digest contract before managed execution.

• Actor: Codex.

• Human authority: adrianwebb, explicit implementation authorization.

• Agent / capacity provider: Codex desktop; no simulated provider proof claimed.

• Exact base ref: staging 5cffc5725e7ab3ec6186437914dc0ea021b2c8dd.

• Exact head ref: codex/api-receipt-digest-368 6614478e4ab122bdd31859b354ed9a062f327800.

• Agent-authored under human authority

Plan

Reproduce actual producer-format rejection first; correct the two owning acceptance guards, strengthen existing negative and native paths, then wait for fresh required Actions and audit the exact candidate artifacts before ordinary staging merge.

Changes and commits

• 516398a: regression first; controlled fixtures now generate actual SHA-256 base64url values using Node crypto, matching the owning API security function. Existing three receipt cases all failed before repair, zero skipped; retained RED log SHA256 10782721c787b5909e8803d9637893d8aa8592c0fb348a810f20e332a5a6365d.
• 6614478e4ab122bdd31859b354ed9a062f327800: two exact-format guards corrected to the original 43-character base64url representation. Additional malformed-length, punctuation and wrong hexadecimal-representation denials preserve failed bytes and no receipt creation. Every previous negative remains.
• Unit: original selected receipt positive/denial/read-back cases.
• Real integration: original selected native SDK HTTP/child-process receipt case now carries the producer's digest representation through capture, four concurrent retained writers, interrupted child, foreign public reads, denial and exact retry. Inputs remain controlled; this is not PostgreSQL producer completeness or a real campaign.
• Scene: original five workday-start component cases retain their IDs and selection. The actual public API producer integration in API #531 independently confirms preflight/start encoding, stored response equality and exact replay.

Verification

Pinned Node 24.12.0 and unchanged retained Platform authority /tmp/sdk369-platform-authority-de2LzF. All guarantees tests 95/95 across 16 files, zero failed/skipped/todo; SHA256 9b15018ca6d47a3a54581b95b255b2e624ed5bbbe4af2993ed8250fddd794293. npm run typecheck, npm run check:file-lengths (including architecture) and npm run build:dist passed. Required fresh complete Agent/Reviewer suites, component scenes and candidate package artifacts remain pending Actions; no scene was launched locally.

No production runtime/product changes, compatibility path, new digest implementation, runner, schema, runtime activation, managed invocation, deadline changes or SDK product repair. Test children and temporary roots close through the existing native finally paths. All historical failed evidence, leases and worktrees retained. Strict binding count remains 26/204; this repair is not launch readiness. Ordinary staging merge/read-back and exact temporary branch cleanup follow required automated verification.

Risk and rollback

Acceptance-only contract correction; no persistent data migration or product change. Roll back through an ordinary checked PR using git revert --no-commit 6614478e4ab122bdd31859b354ed9a062f327800 516398a, commit the result, and verify before staging integration. Reverting restores the prior receipt rejection and therefore blocks SDK launch.

Completion summary

Implementation and focused/type/build checks complete; required complete suites, component scenes, archive audit and staging merge remain pending. All broader strict campaign/binding/environment obligations remain open.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.

SDK #391 producer-format correction

Outcome

Consume the API's original base64url SHA-256 start receipt digests in SDK golden acceptance. The prior hexadecimal-only validation rejected real receipts even though controlled hexadecimal fixtures passed. Preserve exact frozen digest equality, original receipt shape, public completed-workday authority, installed asset custody and all previous negative checks.

Work authority

• Work item / Issue: SDK Current sdk backlog: retained requirements after issue consolidation #376; implementation continuation Complete strict SDK capacity-provider and agent acceptance bindings #387; producer contract proof Bind managed API verification to original workday-start custody api#531.

• Proposal / decision: User-approved strict capacity-provider and agent-execution acceptance implementation plan.

• Assignment / checkpoint: Producer-to-consumer workday-start digest representation.

• Actor: Codex.

• Human authority: adrianwebb, explicit implementation authorization.

• Agent / capacity provider: Codex desktop; no simulated provider proof claimed.

• Exact base ref: staging c5a99361c47fbc977a5d1136d796be17b38af38f.

• Exact head ref: codex/api-receipt-digest-387 4a64a1ac5b793eccacbc4ddbd0ccd232676c842e.

• Agent-authored under human authority

Plan

Commit the failing producer-format fixture regression first; correct only the two receipt-format guards, strengthen malformed representation denials and reuse original native child/HTTP integration and selected component cases. Require fresh complete SDK/Reviewer prerequisites, component scenes and package artifact verification before ordinary staging merge.

Changes and commits

• 8d88452d: regression; Node crypto generates SHA-256 base64url digest values matching the API security function. Both original receipt unit cases fail before repair, zero skipped; RED SHA256 42d66286d6ee9110b21d038c761d386234da083c8f8da25637cec0e199a30766.
• 4a64a1ac5b793eccacbc4ddbd0ccd232676c842e: accept the producer's exact 43-character base64url representation, deny wrong hexadecimal and malformed lengths, retain every previous authority/immutability/denial assertion. No SDK product source changes.

Verification

Pinned Node 24.12.0. Related three files: 12/12 including original native HTTP/isolated-child case; SHA256 c38fe1f369b1b4a6dffcaf5543eb171cedbf977e84207bbf510b3216df131d45. Initial npm run release:verify failed because the required pinned Platform workspace variable was omitted (36 failures, 534 passed, zero skipped); retained failed log. Corrected invocation with TREESEED_DEVELOPMENT_WORKSPACE_ROOT=/tmp/sdk369-platform-authority-de2LzF passed source/architecture, strict build, standards and complete 570/570 across 76 files. Exact full-suite log digests are retained in SDK #387. No scene was launched locally. Required Actions still must supply fresh complete SDK/Reviewer prerequisites before the existing component scenes and actual candidate archive audit.

Unit mapping: original selected workday-start positive and denial cases, strengthened for actual digest representation and malformed lengths. Integration mapping: original selected native SDK HTTP/isolated-child test carries the same digests through exact/concurrent resumed read-back, foreign authority, denied response, interruption and retry. Those responses are controlled; actual public producer preflight/start and durable cache format are proved separately in API #531, not claimed as a managed SDK workday here. Scene mapping: original three receipt component cases retain exact IDs and selection.

Risk and rollback

Acceptance-only contract repair, no data migration. Recover through an ordinary checked PR with git revert --no-commit 4a64a1ac5b793eccacbc4ddbd0ccd232676c842e 8d88452d, commit and verify before staging integration. Reverting restores rejection of real API receipts and therefore blocks launch.

Completion summary

Implementation and local related/full verification complete. Required Actions, exact archive/scene audit and ordinary staging delivery remain pending. No managed acceptance, product implementation, runtime activation, release, source fallback or deadline change. The non-enumerable retired-field defect remains reserved for the genuine simulated Tester/Reviewer/Engineer chain. Strict binding count remains 26/204, all 260 deferred obligations retained; campaign authority and other plan gaps remain open.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.

SDK local complete-suite retained failure SHA256 25a7758a994fbb5f10ba6cf3b3d7d46976c534bdb63f9e64792d139f747138ad; corrected exact-pinned authority invocation SHA256 fe2130386c3033cf60c89529b18230d96cdae046012ef92b73752bc5cac58e96 (570/570). Both histories remain retained, not relabeled. None of these deliveries establishes managed campaign readiness.

Required invocation failure retained — SDK #391

Run 38091092189, job 114327505562, tested merge a76def8b30187028612f599293fa4413fd79ae08: fresh SDK suite 570/570 passed; fresh executing Reviewer 108f153b18896e62cd0fb7507c2fa78c4ffaec36 suite 199/200 failed, zero skipped/todo. The actual production-install integration reported ACCEPTANCE_INSTALLED_PLAN_ETIMEDOUT: pack 1209.67ms, install 22435.22ms, dependency exports 132.82ms, then plan 1145.33ms exhausted its original 25-second work portion / 30-second total. No scene executed: both guarantees blocked, zero failed/passed scene counts. This is retained failed prerequisite evidence, not a component/managed pass; no rerun or deadline extension was requested. Native command-link/PATH custody repair in Reviewer is independently in progress; a checked replacement runner candidate is needed before further integration.

Retained Actions scene artifact 11684735792 ZIP SHA256 a2ffb7d031f9f7992ac7a723bc5d0f21aa38850374ed89d30d9a39073ce9900a; report SHA256 47c9ca415cfa1d489e0b534104dcc555cac948f376e0c3e0dd59565361cd00bf; SDK prerequisite SHA256 7dbf2c832a2f6d87ef3728c73fc0b7c18b35083277382267d30901f5f7ac04b6; failed Reviewer prerequisite SHA256 4ba4150c69e923fbb74db9592227485edb5589d7145d8d9071bde0e7439ca080; raw job SHA256 9371ca761c8936d20fa5db350082e0174bd931384c05374aac5d1180fcf53fb5. Files retained under the existing native-verification cache and authoritative Actions artifact.

Reviewer installed native command custody — PR #118

Outcome

Hold installed owners' top-level command links in the same archive custody as their bundled command links, and resolve those installed commands before inherited PATH during native verifier execution. Agent and SDK acceptance invoke public CLI commands; the previous installed runner could execute an uninstalled same-name command even while its TypeScript imports were fenced to installed assets.

Work authority

• Work item / Issue: Reviewer Expose account concurrency revisions #98; strict implementation continuation Complete strict SDK capacity-provider and agent acceptance bindings #387.

• Proposal / decision: User-approved strict capacity-provider and agent-execution acceptance implementation plan, bounded installed-execution interface repair.

• Assignment / checkpoint: Product-neutral archive-declared native command custody.

• Actor: Codex.

• Human authority: adrianwebb, explicit implementation authorization.

• Agent / capacity provider: Codex desktop; no simulated provider or managed proof claimed.

• Exact base ref: staging 108f153b18896e62cd0fb7507c2fa78c4ffaec36.

• Exact head ref: codex/installed-command-custody-98 7ec58da46287d69822afc25b2aabb382dda665af.

• Agent-authored under human authority

Plan

Reproduce top-level link substitution and inherited command selection before repair. Reuse the existing InstalledOwner bins inventory, package bin declarations, regular archive target checks and original pre/post custody diagnostics. Native workers use their existing held owning working directory and installed package identity, then prepend that owner's bundled command directory and the selected installation's command directory. Keep the exact installed-location option, original runner, source prerequisites, report format and all original watchdogs. No product names or role policy enter Reviewer.

Changes and commits

• 1de4e10: focused regressions first. Missing top-level owner link was silently accepted; the real production-installed native fixture selected an uninstalled conflicting command. Both targeted tests failed; four other assertions were filtered in this focused regression, which is not a complete-suite receipt. RED log SHA256 d6c93dbc04224c9a8e7fd479c6215f8c0e9f2993419b4650cfc9911d0dba2830.
• 7ec58da46287d69822afc25b2aabb382dda665af: retain top-level and bundled links from the same archived package declarations; reject missing/foreign/absolute/directory targets and redirected command directories; include links in existing immutable custody diagnostics. The native installed worker validates its held cwd package location and uses matching bundled/root command directories first. Existing production fixture also exercises a bundled command against an inherited conflicting binary.

Verification

Pinned Node 24.12.0. npm run check:file-lengths, architecture check, npm run typecheck and npm run build:dist: pass. Complete focused files (without filters): 3/3 files, 7/7 tests, zero failed/skipped/todo; log SHA256 f1264b945595cbb284ad13e45c63433c346cc3fe0692644b473b401745ed0a93. Earlier fixture-authoring failures are retained: inappropriate directory unlink and a metadata-dependent owner lookup were corrected; the native worker instead uses its already-held owning cwd and regular package manifest without requiring a new product resource.

• Unit: existing installed-assets case proves exact external owner-command inventory, redirected command directory denial, foreign link denial and unchanged retry, retaining all old archive/source/mode/dependency cases.
• Real integration: existing native npm production fixture installs actual owner/bundled archives with production dependencies and scripts disabled; missing/substituted top-level links fail custody; both archived commands win over inherited conflicting executables. Actual installed Reviewer and SDK dependency exports still execute; checkout imports/missing helpers remain denied before exact retry; complete cleanup is asserted under the unchanged 30-second/25-second work bounds.
• Scene: existing selected reviewer.prerequisites.installed-bins-native, installed-assets-unit, installed-production-native assertions are strengthened in place in the original prerequisite component scene. No local scene was launched without fresh complete prerequisites. Native complete Reviewer suite and all component scenes/package audit remain pending required Actions; missing local Elixir/native prerequisites remain explicitly unproven.

Risk and rollback

No new runner, schema, authority, CLI option, service or dependency; no production runtime mutation or relaxed timeout. External native toolchains retain their original prerequisites. Recover through an ordinary checked PR with git revert --no-commit 7ec58da46287d69822afc25b2aabb382dda665af 1de4e10, commit and verify before staging integration. Reverting restores installed command-custody gaps and blocks SDK launch.

Completion summary

Implementation and related native/type/build checks complete; required complete-suite/component/package checks and ordinary staging merge remain pending. No managed campaign or binding readiness is claimed; strict selection remains 26/204 bound and 260 deferred. SDK #391 separately retained a failed fresh prerequisite at the old runner: 570/570 SDK, 199/200 Reviewer, production install 22.4 seconds exhausted the original plan deadline before any scene. That failure remains failed; this bounded command-custody repair does not pretend to prove cold dependency latency. No blind rerun or watchdog extension. Owned test processes and fixture roots were removed; source history, unrelated processes, leases, keys and existing worktrees retained.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.

Checked candidate evidence — Agent #393

Required run 38090888656, job 114326907191, passed on tested merge 7120d838c80a5959fc3a1af636e6a4b84e63542b, tree 08ce74ceaab97a51db6561934460b63c7de41798. Fresh complete Agent 953/953 (22:20:50.300–22:22:10.806 UTC) then executing Reviewer 200/200 (22:22:10.806–22:24:18.895 UTC) preceded all 700 component/planning/recovery steps. Zero failed/skipped/todo/blocked checks and zero diagnostics. All five original workday-start selected source digests match tested Git bytes; shipped campaign asset matches the actual archive. This proves the controlled component contracts, not governed managed producer completeness.

Package artifact 11683789482 ZIP SHA256 0b5dd266259b3b2b0a2a2b86f27dc554b7cbd5cde24f5a61112b8debff29fd95; actual tgz SHA256 18336960526e50df2a31c9c9d4c08563a2d4eae57b9a8da6ee106139cf35757d. Scene artifact 11683499603 ZIP SHA256 1176b1f3185b899a8294025819b6deacb3c326625cd6efd9088113751c688d62; report a5e8c5c773f4c95f6010df771e5f861017471fa307ade937a37187a7747b0690; Agent prerequisite 72c31e5d29420682b46aff783a42288ec767012f06611fae822d2a87171bed11; Reviewer prerequisite 6be839e0769dcb9b21c728171da03cf3fda2123d2e7154ef5fe89cd4a9c7c07d; raw job 67da6be35b334d4733e98950b6123baf028c6b660bf178ae55c8b5532da7c851. Initial submission failure (missing template fields) remains retained at SHA256 02e1305d1261fdeabf7b74c280c96aeb13ab948174a111dc88858d6fd8d32ec9; corrected validation 114327364009 passed unchanged source. No failed observation was relabeled. Detailed authoritative artifacts retained in Actions and the existing native-verification cache. Ready for ordinary staging integration with fresh exact-head/tree read-back; campaign readiness and 178 unbound criteria remain open.

Delivery read-back: PR #393 was merged ordinarily to staging at 3899fc2962c2217c8fb0f3667ac512b2e370a075. Its parents are the held base 5cffc5725e7ab3ec6186437914dc0ea021b2c8dd and source 6614478e4ab122bdd31859b354ed9a062f327800; tree 08ce74ceaab97a51db6561934460b63c7de41798 equals the checked merge candidate. The clean local staging checkout was fast-forwarded, historical local main preserved, and only this delivery’s remote codex/api-receipt-digest-368 branch was deleted with the exact source lease. This delivery corrects API receipt digest representation; it does not establish managed producer completeness or SDK readiness.

Next integrator checkpoint: normal SDK clean-schema selection

Owner: Agent #368; API #515 owns the existing verifier and native PostgreSQL proof. Hold Agent staging 3899fc2962c2217c8fb0f3667ac512b2e370a075, API #531 source 52449d4b1ca430fb507a2cf95c1a27281816b563 (not yet checked/delivered), and Reviewer #118 source 7ec58da46287d69822afc25b2aabb382dda665af (not yet checked/delivered). Add a focused binding regression before selecting api.golden.execution-normal-sdk-clean-schema-live-1 once after canonical terminal records and before physical absence. Preserve the stricter historical-calibration architecture case, normal cold/default-zero admission, all existing scene steps, independent package test discovery, and every deferred criterion. Gate delivery on the API candidate’s required native checks and exact staging read-back; use the checked Reviewer candidate only after its own required checks/read-back. Review criterion 195 separately; selection alone does not certify that broader semantic binding, installed package execution, producer completeness, or any managed outcome. Unit binding checks, API’s real public/native integrations, and the existing managed scene are the owning coverage boundaries; managed execution remains blocked by the unchanged launch gates. No campaign is authorized by this checkpoint.

Reviewer #118 checkpoint: required run 38091948574 passed a fresh 200/200 prerequisite before 114/114 component steps; actual archive SHA256 6dec47d082c28f440a4fbf71e9b57f18584b957fdc893839059cb8ffd731dceb, report 2008e12046d8d3f0a5c79cfef1d5b156dff6d004ab2d903dc7b0189658b13475. PR #118 contains complete evidence hashes. Delivered staging df1a0bb3b4791aa39f5212fedfb845042636f283, exact checked tree c3580c210100237286445d93876ee13ef07c2323; ordinary parents/source and clean checkout read-back verified, temporary branch removed with exact lease. Next held SDK #391 replacement will retain source 4a64a1ac5b793eccacbc4ddbd0ccd232676c842e history and the failed old-runner cold-install report; update the existing workflow and its native binding assertion to this checked Reviewer staging commit, then run fresh complete prerequisites and required Actions. This is a concrete new command-custody candidate, not a blind rerun or a latency/deadline allowance. Agent clean-schema selection regression 0b495868104979dbaf806642792d471e31bfc4bc fails exactly once (6 pass, zero skips); API #531 checks remain pending before selecting its managed case. No new acceptance binding or managed pass claimed.

Checked runner replacement candidate

Current source is 00232905190a5420436322005b2e27ca83f06451, preserving 4a64a1ac5b793eccacbc4ddbd0ccd232676c842e and all earlier RED/repair lineage. Pin regression commit 82e78412d3bbf09d6b54b68d9eae44c20b9dcc30 produced exactly one intended failure, nine pass, zero skips (SHA256 f79ce0c3c40c7e75cc85df602a76421dee74b34f2728f9eb8c9540346e46e783); repair commit 00232905190a5420436322005b2e27ca83f06451 updates the existing workflow to checked Reviewer staging df1a0bb3b4791aa39f5212fedfb845042636f283. Reviewer #118 passed fresh 200/200 prerequisites then 114/114 component steps in run 38091948574 and delivered exact tested tree c3580c210100237286445d93876ee13ef07c2323. Related SDK canonical/pin, original workday receipt and product verifier files passed 21/21, zero failed/skipped/todo (SHA256 67b2cdbb8062ec852cba67f70b600fd1705d805cb8e215c529544a3bc6085ed2); file architecture passed (SHA256 ae8acd8b2ac595c53d817674d49f0e3c696576ac3ce8d476d334e8ba8b27c512). No new SDK product change, dependency relaxation, source fallback, timeout or campaign. Complete verification on this exact new candidate remains pending required Actions; prior full-suite evidence is historical. The failed old-runner invocation above stays failed. The replacement adds proved installed command custody; it does not claim a repair to cold network latency.

Integrator candidate Agent #394: held base 3899fc2962c2217c8fb0f3667ac512b2e370a075, RED 0b495868104979dbaf806642792d471e31bfc4bc / 424ad68d0e7ab86374b6db5bff9f8fdb80132639, repair/source 5980f61f4b93c5b8e24d6a037f4b54cfb8df8e8d. Reuses the existing selected composition unit case/ID to select API’s normal clean-schema case after canonical records and before physical absence; checked Reviewer pin df1a0bb3b4791aa39f5212fedfb845042636f283. Related 95/95, strict typecheck and source architecture pass; exact commands/digests and native owning API boundary are in the PR. Plan eba49fde792e0564e6dfa2faaf3d55630b44a26ba2b8a8f46a699661f6910f63 retains 464/204/26/178/260 with identical selected/deferred IDs, 19 scene refs and only original uncovered diagnostics. API #531 checked delivery plus Agent’s fresh complete CI/component/archive proof gate merge. No criterion 195 binding yet: selection does not replace review of complete CLI/API semantic and installed custody proof. No local managed scene or campaign.

Next SDK installed-asset checkpoint (after #391 delivery)

Strengthen the existing native workday-start public-read case in place: pack the actual held SDK owner with its normal native package entrypoint into an owned isolated directory, install that exact archive with production dependencies and scripts disabled, and run the same original receipt/public-HTTP denial/interruption/concurrent-retry assertions from the installed SDK helper and installed public SDK exports. Compare helper/archive/installed bytes, reject missing/altered installed helper, preserve immutable freeze/receipt bytes and existing source/production dependency identity. Retain the original 15-second test and five-second child bounds and finally cleanup; no development tsx/checkout import fallback, dependency override, duplicate runner, registry substitute for the SDK archive, or new acceptance model. Reuse the existing native verifier ID/scene. This is actual SDK asset closure proof with controlled API responses, not native PostgreSQL producer completeness, the genuine managed product chain, combined six-owner installed execution, or criterion 2 completion. No SDK product source change; the non-enumerable field repair remains reserved.

Checked replacement Actions evidence

Required run 38092916053, job 114332851754, passed on tested merge 40fb8afc67a89eda375fb9a0f6ee2eebedc12d72, tree 262d2ff70ce95d31912a0b2359a1cef3ec324b91. Fresh SDK 570/570 ran 22:53:12.169–22:54:35.981 UTC; fresh executing Reviewer df1a0bb3b4791aa39f5212fedfb845042636f283 200/200 ran 22:54:35.981–22:57:36.162 UTC, both zero failed/skipped/todo, before 239/239 component steps passed with zero blocked/failed/skipped steps or diagnostics. All three original receipt verifier evidence entries match exact tested source digests; shipped tests/acceptance/golden-product.ts bytes match tested Git. Public product implementation remains untouched.

SHA256: scene artifact 11684459833 ZIP 983b8a7e05b04a79ebdfb2198799724c1de795de637a811288e705a64224f9df; report 3b8a9c00c0b5522609a99b2f05bee259044c600b31900ad93832038bb6be0ef0; SDK prerequisite d80d970109e8b93ecafe4c42b30c52a5654f0f5fc253a919042264fe3902c6b6; Reviewer prerequisite 3d13fdedf83c6f14a64bdb1a8b082a53b89b3e57b0fb99f00553a4b3ae7750cf; package artifact 11684469829 ZIP 73e83ca8acbe64db24104f6289fd9578f354586aac7e34c0a5eb07d5a26452ec; actual archive 3b0aa419cd4ce684b81603c1330499604f9f0e41f5202980f4e6e82a5a2525e8; raw job log 7a200084f0ddcdd790e0043f54ca4bfeb7b7bc0f7b657388c9b62198d19d9b43. The old failed invocation above remains failed. This checked replacement is bounded component/package evidence and does not certify cold latency universally, combined installed owner custody, SDK managed readiness, or managed golden acceptance.

Delivery read-back: ordinary SDK staging merge 8698ce113b9c6a25429394a4f193428e8b209b51 has held base c5a99361c47fbc977a5d1136d796be17b38af38f and source 00232905190a5420436322005b2e27ca83f06451 as its two parents, and exact tested tree 262d2ff70ce95d31912a0b2359a1cef3ec324b91. Clean local staging was fast-forwarded; historical local main fc67674caf11218f5f9b5690f1ea8f26e8e4d070 preserved. Only codex/api-receipt-digest-387 was removed using its exact source lease; absence verified. Prior failed invocation remains retained; no managed campaign, product implementation repair or readiness claim.

SDK checkpoint refinement — concrete archive reproducibility defect

Existing tests/contract/standards/package-archive.test.ts already proves actual production-installed SDK public imports; reuse it rather than duplicate that proof. A cheap actual SDK #391 archive probe confirms compiled public exports load, while raw TypeScript under node_modules is correctly rejected by Node 24 without the required production Reviewer loader (ERR_UNSUPPORTED_NODE_MODULES_TYPE_STRIPPING). Probe roots/processes removed; retained diagnosis SHA256 4409b8cfa29ba4a5617727b8111c5f5001c297d625f6259dfc750411899ebb56. The earlier loader-free probe failed and remains failed (68246d173ae71aab105ad5f6d5c73419a5a8a9a1876a7b6c11557c238173e7d1); no installed managed proof claimed.

Comparing local SDK pack c4065d9fea0928b70eb314abe4df61f92c7ec8bbc0f134db18bbcf00a47cd7af with checked SDK #391 archive 3b0aa419cd4ce684b81603c1330499604f9f0e41f5202980f4e6e82a5a2525e8 finds 440 identical member identities and only dist/.treeseed-build-complete.json differs, solely its completedAt timestamp. Exact diff evidence SHA256 ed5a1c99cec65a80d6c852ea359e4c247de6a51d354fd1cccd8c81120ddf4fcd. This is an implementation packaging defect, not authority to relax installed archive-byte custody. Hold fresh SDK staging 8698ce113b9c6a25429394a4f193428e8b209b51; add focused unit/native regressions first, preserve the actual live build marker and lifetime semantics, exclude final/temporary markers from npm files (as CLI already does), and reject contaminated archives through the existing public standards:acceptance entrypoint. Strengthen existing native installed/public-archive cases and their selected component IDs in place; original time bounds unchanged. No SDK product implementation change, new runner, release, dependency override or managed campaign. Actual combined installed Reviewer/owner execution remains a separate unresolved gate.

Checked Actions evidence

Required run 38093023224, job 114333160142, passed on proposed merge 8619fa19f8a82fd243a2932880c5d077b513c7c7, tree 07ecf03b107a0d7322dab7a7dca5cdb341cc816d. Fresh Agent 953/953 ran 22:55:22.238–22:56:51.467 UTC; fresh executing Reviewer df1a0bb3b4791aa39f5212fedfb845042636f283 200/200 ran 22:56:51.467–22:59:09.748 UTC, zero failed/skipped/todo, before all 700 component/planning-recovery steps passed without blocked/failed/skipped results or diagnostics. Both modified binding/pin verifier source digests match tested Git. The actual archive's SDK scene bytes match tested Git and contain the normal API schema ref exactly once. The managed SDK scene was not executed by this component run.

SHA256: scene artifact 11684769902 ZIP b0331255fc95191ffe9b060bffa951b4252a2ca214d13981cb07d588303143f1; report 0f175a8552b01215644c0a33457575137d2b7e1833858f5974b59fe59eebe0c9; Agent prerequisite c83408c0ef55454444eb9eefd862eca04e04d6e40a9eee5b2182b765906d74e5; Reviewer prerequisite 90bab93a7ce91a48442507cc2ebdad71c48dd80286fd8d5c8cce8b4e81f9b268; package artifact 11685590597 ZIP ec1e2031ccb83b5f0787c3230dbeaa567f429f37bd9005cdc6fde90cbe5150a0; actual archive b541796d3838ee256e74146c4fe172583714e45e6c3cead6e4c51bbe8d50e28d; raw job 2df2d154373b6cffc10ba2629163eeefc0feda539f01449067ab4ff69f4d18fc. API #531 required native check/delivery remains a merge gate. Strict plan stays 464/204/26/178/260; no new semantic binding or managed readiness is claimed.

SDK marker candidate #392: held base 8698ce113b9c6a25429394a4f193428e8b209b51, RED 9d700bc53f554b4e07c52f0a2df8c28d9de91b2c and 2349dfbf91a99091d4cb9b6f2ed5f6a5c4899552, repair/source 19a2f57c5cf7fe5729627ee92340dca4fa68a2b2, remote codex/sdk-archive-marker-custody-387. Exclude final/temporary local build coordination markers from packages and reject canonical/aliased contamination through the original public archive command. Reuses existing unit/native/scene IDs; no product source/dependency/lifetime/deadline changes. Related 15/15, final native original-archive reproducibility assertion, source length/architecture and strict build passed; precise commands and SHA256 evidence (including initial corrected alias fixture failure) are in the PR. Full exact-candidate SDK/Reviewer prerequisites, component checks, actual archive audit and ordinary staging delivery remain pending. No blind SDK campaign, combined installed proof or binding/readiness claim. Native fixture roots/children cleaned; live marker and unpublished data retained.

API #531 checked dependency — 2026-10-10

API #531 required run 38091049594 passed on tested merge 89c861bfc5167f2b78cbc84b441e6650568dd4b1, source 52449d4b1ca430fb507a2cf95c1a27281816b563, base f56549966f9781d7193a39007191806293d83b7c. Fresh complete API 2,027/2,027 and Reviewer 108f153b18896e62cd0fb7507c2fa78c4ffaec36 200/200 (zero failed/skipped/todo) preceded all 838 passing component steps. Four new retained-start cases, including independent native PostgreSQL concurrent reads/cancellation/denial/exact retry, match tested source digests; both shipped acceptance assets match tested Git bytes. Scene artifact 11685656625 / report SHA 61140e2268d57535c446ebef04869cabe7a9817e41901d07f3b7474dc17b6927; package artifact 11686000678 / actual archive SHA febccffe24791a90b9d2a9a8a781b172959ff6a4210b459a74d1c35931cfcf00. Detailed prerequisite, ZIP and log custody remains in the PR body and original Actions artifacts. No managed invocation or new acceptance binding is claimed. Agent #394 remains held pending checked API delivery.

API #531 staging delivery: 7e9d932136e2d672b2afd01dbb7c088e76f3df16; original parents and tested tree 8212f7dd65ca587c994a44b6cfd66491fc7b20eb verified after fresh protected fetch. Clean local staging fast-forwarded, historical main retained, exact-leased temporary branch removed and absence verified. Agent #394 dependency is now delivered; no managed readiness claim.

Agent #394 dependency integration delivered staging 34bef1ddecfe7dd836c673f0b823e5b86ae7ad08; original parents and tested tree 07ecf03b107a0d7322dab7a7dca5cdb341cc816d verified. Fresh native CI evidence remains 953 Agent + 200 Reviewer assertions before 700 component/planning-recovery steps. Clean local staging fast-forwarded, historical main retained, this delivery's temporary remote branch exact-leased/deleted. Strict inventory remains 464 total / 204 selected / 26 bound / 178 unbound / 260 deferred, with 19 managed refs. No managed invocation or criterion-195 binding claimed.

Next Agent monitor regression contract

On fresh Agent staging 34bef1ddecfe7dd836c673f0b823e5b86ae7ad08, strengthen the existing live-assignment immutability unit and native Kernel/Git/SDK-read case to reproduce lifecycle status regression. The observer currently removes status from held authority comparison and has no separate status progression check. Preserve exact issued authority/clocks, allow repeated reads and forward lifecycle observations, deny backwards active states or changed terminal dispositions before progress, preserve the prior complete observation on denial and exact retry. Reuse the existing selected component verifier IDs and managed campaign observer/scoped stop; no new runner, record model, role policy or inferred producer completeness. Commit the failing focused regressions before the minimal owning acceptance-observer repair. Fresh complete Agent/Reviewer suites and all component scenes remain required in Actions; managed SDK proof remains blocked.

Agent #395 holds source 787836f9623c62a9461eed38aba802e4da4ef0a2 on base 34bef1ddecfe7dd836c673f0b823e5b86ae7ad08, preceded by RED a9b3502039ec312fc197e3cc1746f443a5dc9721 (two intended failures/five passes). Related 47/47, strict typecheck and file architecture pass; existing immutability/native cases retain their IDs and component selection. Native complete suites and scenes remain pending; no additional strict criterion binding claimed. Local RED/related log SHA256: 36745c035aca19856ab19e6d457d48e38decf35a392eaeda62ef9a43103a63da / d82d33c499d480a36eb7310b5bb8845b1a51283044a17f6497e2b6e717af9dab.

SDK #392 required run 38094647898 passed on tested merge 9e56a7c4a65ed829951d60dc09689142edb7c5a2: fresh SDK 570/570 + Reviewer df1a0bb3 200/200 before 239 passing component steps, zero failed/skipped/todo. Actual 439-file CI archive a66206ce0e2514f4a3eb9e49d172c662585f2e4e0128800b54acef3a14f86fd9 excludes both transient markers and matches tested manifest/acceptance asset bytes. Report SHA cf33262444ab1a78073700517404505b982ef06f356ac499717431f24c64e709. Full artifact custody and 14 changed-file case digests are in the PR/Actions. Local and CI file contents agree; three non-executable file modes differ (0640/0644), so local archive 89c13f9038913a05efd33a6e4d7b8776a79d428df21cd5bd40f5da8e65b10b54 remains separately held and matches native local npm inventory. No custody relaxation, permission normalization, six-owner installed proof or managed pass claimed.

SDK #392 delivered staging 933f8ba3803226b647fd9c9b824fcbe11f4ce34a; original parents and tested tree 2e33db6af91de15ef3991cbf707b397ab92bfe26 verified. Clean staging fast-forwarded, historical main retained, exact-leased temporary remote branch deleted/absence verified. Local build markers retained; no product implementation or managed campaign change.

Next installed-custody diagnostic uses native npm-pack output for the six actual held owners (Agent/API/SDK/CLI/Deployment/Reviewer), records exact source commits/archive digests, and performs the plan's isolated production install with scripts disabled and no SDK dependency overrides or registry replacement of top-level owners. This is installation/plan inspection only, not a scene or managed passing receipt. Preserve any failed dependency/loader evidence and remove only the disposable install tree/processes after inspection. Fresh complete suites remain required before every executable scene; current governed campaign authority and full managed physical closure remain unproven.

Installed npm-bin entrypoint defect — implementation continuation

Actual six-owner archives installed with --omit=dev --ignore-scripts --package-lock=false --no-save without dependency overrides (718 production packages, exit zero). Running the installed node_modules/.bin/treeseed-reviewer-guarantees with --plan exited zero with zero stdout/stderr bytes; no report or acceptance proof was produced. Its npm link resolves to the archived command SHA a557e1ee1ceee0cddcd33e1b5fe0fb2ab4628c1a3ea157d8324876698b45fe3d, but the main guard compares module URL against the unresolved argv symlink. Installation log SHA 39750a2c853e06a8837d159fc72d308d60a0282d0d00d9fa2eb7b112e41a2087. Classify as IMPLEMENTATION_DEFECT; fixed proposal/interface remains valid. On fresh Reviewer staging df1a0bb3b4791aa39f5212fedfb845042636f283, commit focused source-symlink unit and actual production-installed npm-bin regression first, repair only real-path entrypoint identity, retain existing selected verifier IDs, source import behavior, archive/command custody and original watchdogs. Full native suites/component scenes required before checked delivery. Retain original failed diagnostic/archive bytes and remove its disposable installed dependencies after inspection. No source fallback, alternate runner or managed pass.

Reviewer #119 holds source af573f92f341eb818f7dc3164eb9aa87391ec292, base df1a0bb3b4791aa39f5212fedfb845042636f283, preceded by RED 99878e0a49112c063949cdc3a176568e22fc0248. Two intended focused failures reproduced source/installed npm-link silent exit. Rebuilt related tests 43/43, strict typecheck/build/architecture passed; native CI pending. Original unrebuilt failed run retained. Existing selected unit/native verifier IDs and watchdogs unchanged. Six-owner probe's disposable dependencies removed; six archives and failed evidence retained. Detailed exact commands/digests remain in PR #119 and Reviewer #98.

Strict implementation continues in SDK #393; prior contract and failed evidence remain preserved here.