SDK exploratory source custody and canonical workday closeout repair

Authorized strict acceptance implementation — 2026-10-09

Current contract/checklist continuation: SDK #415; all 204 exact selected criterion identities and prior approved contract remain retained in SDK #387; composition coordination remains Platform #633. This Issue remains owning implementation/evidence authority. Reviewer prerequisite shell support (#105) and installed-owner execution (#106) have passed native CI and ordinary merged to staging; these are bounded runner repairs, not TreeDX strict reporting, actual installed multi-owner execution or managed SDK acceptance. API #528 and TreeDX #88 were reconciled through their existing ordinary promotion PRs with exact tested-tree readback. Preserve all failed observations and deferred obligations. No managed campaign, new runtime selection, tag, release or publication occurred during this implementation.

2026-10-09 19:55 UTC — API fresh scene PASS; stop requested by human

API PR #528 verification Actions https://github.com/treeseed-ai/api/actions/runs/37972900967 (job113963784243) completed SUCCESS. Independently audited ALL823 exact original component scene steps and fresh COMPLETE original2012/2012 prerequisite tests: failed0/skipped0/todo0, unfiltered original control-plane command. Three real PostgreSQL supplements3/17/28 also passed; overlapping counts NOT summed. Native TreeDX prerequisites and allocated server cleanup steps passed. Scope local-component-tests, NOT managed SDK/golden acceptance.

Held staging789a94e99cb18bea28017af4463f1fcea5695418 and actual tested merge1a9bb2050987f5b09ba4bb4f01a81493fb6b6882 share treec9461348b52c675711121b09803101c2a3a7ae52. Scene18:46:50.759–19:53:43.006UTC. Artifact11641871984 ZIP /tmp/sdk376-golden-r3-api-scene-37972900967-1.zip SHA256214703a50e073c78125d6ebdebd3c2b1187fc970e9eb7d5f653e3e3d47236a34; native reportSHA25645168021bbdc55956b9aa6960367544f353d369f6cd1832f9d9591a5698b0fc4. Independent audit /tmp/sdk376-golden-r3-api-scene-audit-20261009.json SHA256d535ffed07e769db4259ad2be495839b5c81842cac78ce0cdd8922c044f9ad75.

Human: "After this API scene completes go ahead and stop so we can address these 179 binding gaps." STOP after verification/persistence. NO SDK guest/model check, workday/campaign, further PR merge or implementation. PR528 remains OPEN; local API staging clean. Final original candidate() readback of all7 held owner HEADs/source digests matches the fresh invocation inventory. No tags/releases/activation/new branches/worktrees.

Strict SDK selection remains204 entries:25 bound/179 unbound;260 deferred/464 whole. These are specification-to-selected-executable binding gaps, NOT179 failing tests. Exact source audit has NOT yet classified how many are mapping-only versus missing assertions/integration/live proof. All25 existing bindings also require semantic validity. No blanket binding or parser/spec weakening. Next authorized review/work: audit owning assertions, add missing unit+real integration+native scene proof, installed assets and physical closure, then exact bindings and fresh full prerequisites/strict acceptance. Golden acceptance remains UNPROVEN. Entire prior Issue body retained unchanged below.

2026-10-09 — API standalone chat producer delivered; native retry pending

API PR527 merged with lineage into staging789a94e99cb18bea28017af4463f1fcea5695418; source38358b5e and testedmergecc4e6bad exact treec9461348b52c675711121b09803101c2a3a7ae52. Independent original Reviewer candidate digest after merge remains c4be874813a7916d0ea7ef37b5ea7b2f57e0b2b145c6a6d0799419cd2918d0a5; all six other held owner digests unchanged. Required Actions37962055513/verify113927078393 and authorization/submission checks SUCCESS. Complete original API2012/2012 in372files, plus real PG supplemental checks. Independently audited823/823 exact component scene steps, each file/name/sourceSHA/nativeexit0/no signal/diagnostics, with FRESH unfiltered2012/2012 prerequisite0fail/skip/todo. Artifact11637995241 SHA6a686167ff59adae342e5d0e4e02c75f08a91349eaf93bbbb497ac1b7fc6b1e2; reportSHA8aa75499a30beb2ff22e7f13ee580c486a3b3ad49207e43879a2da61482adacd; /tmp/sdk376-chat-r2-api-scene-audit-20261009.json. Component proof NOTmanaged golden. Remote feature branch deleted after ancestry verification. Main promotionPR528 open; required checks pending. App attachment attempt failed because thread already has100attachments, PR remains accessible by URL.

Fresh supported assignments list leased full page empty before restart. Existing manager api.service restart in progress; runner restart/selected-byte readback/native smoke pending. No new SDK workday/proposal/campaign. Queued agent paging/handler-scope regressions remain UNAPPLIED to preserve held candidate during this invocation. Strict SDK179unbound requirements and all broader acceptance still OPEN. Entire prior history retained below.

Fresh exploratory SDK prerequisites — 2026-10-09 17:22 UTC

Same held invocation/candidates; no SDK campaign launched and no golden pass. SDK 563/563, CLI 366/366, Reviewer 174/174, Agent 922/922 fresh complete suites pass with zero fail/skip/todo. Earlier missing-authority invocation failures remain unchanged below, not product RED.

Deployment original disposable installer/native CI run 37949102814 attempt 2 / verify job 113929017971 passes: full suite 1280/1280 and all 202 component checks, including its fresh complete 1280-test prerequisite. Artifact 11632562962, scene archive SHA256 9c52accbfa8cb4fcece56df8d7b01435d65bf5aa3af526609e569c29b457ccc7; independent original audit /tmp/sdk376-chat-r2-deployment-scene-audit-20261009.json SHA256 bf584f1aeab23a124c4395befb8071404435d178d6946bfc3013ead42897b920. Complete native log /tmp/sdk376-chat-r2-deployment-native-complete-20261009.log SHA256 75dc2a2b51a50e878bd126093efc245f286ae0c5510cfb372d9b07e87f0ac23d. No live-host privileged runner or user sudo.

TreeDX original release-gate run 37962656374 at 367fec4237c6928969c969c05217bdb9832b41ac: all 13 selected verification jobs succeeded, both server architectures and all TypeScript/Python/Rust/Elixir SDK architectures. Native server 270/0; TS40, Python33, Rust3+47, Elixir32 per architecture; release-contract3. Overlapping counts are not summed. Profile and publication are intentionally unselected, not skipped tests. Complete native logs /tmp/sdk376-chat-r2-treedx-native-complete-20261009.log SHA256 3733f8621d57a1e2625b6e890fa5f1b192b2fa57f040dc17714745932c7ade2b. Human native-log exception is exploratory-only, not a strict golden reporting waiver.

API PR527 candidate38358b5e31a1dabaadc680f936a06c8773566640/run37962055513: complete verify:direct and additional PostgreSQL checks succeeded; required coded component scene still running. No merge/restart/new smoke/campaign yet. All seven sourceDigest inventories remain held as below; API nested original fixture submodule initialized at its unchanged pin. Current strict SDK gate still has179 unbound criteria. Prior failed smoke physical sandbox closure remains independently unproven, not inferred from its teardown report.

2026-10-09 — Fresh prerequisite invocation for standalone-chat repair (in progress)

API PR #527 / local clean staging candidate 38358b5 is still under full Actions verification 37962055513. No new SDK campaign or model probe has been launched.

Fresh complete local prerequisites for this retry:

SDK 952195376b53bf39742e64f320f2a3b109cc77c0: original npm run release:verify, 563/563, 73 files, zero failures/skips/todo. /tmp/sdk376-chat-r2-sdk-prerequisite-corrected-20261009.log SHA256 0a9d356f709f91d7baaabddae3591d29d0c5db33d2807b874e21781efdbf1864.
CLI 63c7928b2ab2456e495a0e55572b9a47d379315c: original npm test, 366/366, zero failures/cancelled/skipped/todo. /tmp/sdk376-chat-r2-cli-prerequisite-corrected-20261009.tap SHA256 73f4c11f71353af728bd284694400eed353b062f8f736407036dd390ee70f84e.
Reviewer 1e3019fbf24163116222dc96a70c126bf3488389: original npm test -- --reporter=json --outputFile=/tmp/sdk376-chat-r2-reviewer-prerequisite-20261009.json; 174/174, original fullSuitePassed independently true. SHA256 9847379ef71315d1ae18eba30a8180d8b0ab2d3b4e38347709042634ab3ca3b4.
Agent c34f8d029588deae699c19b3a07c7c9ef1a43a96: original npm run test:modern -- --reporter=json --outputFile=/tmp/sdk376-chat-r2-agent-prerequisite-corrected-20261009.json; 922/922, 117 files, original fullSuitePassed independently true. SHA256 aefd88494a9330e765d793f3c73273b85afd7e30581fc7e4fb64b5a0f3815025.
Commands use pinned Node24.12 and existing Elixir wrapper, NODE_EXTRA_CA_CERTS=/etc/treeseed/cli/localhost-ca.crt; SDK/CLI/Agent require existing TREESEED_DEVELOPMENT_WORKSPACE_ROOT=/tmp/sdk369-platform-authority-de2LzF.

Invocation errors retained, NOT product RED: initial SDK/CLI/Agent commands omitted that required authority environment; SDK527/563, CLI360/366, Agent915/922 accordingly failed. Original logs/reports remain, SHA256 respectively d053bc9d26f9ebfe10c5a55f69aff86a22253e2a08ec7619c217a7d78f0209d7 / c9161d6f0e667cab4f8090f6588e610589b83b241347bb7a3630d8e424b9d9b3 / 2025466b4ad68e1fee04222e39cd56e4cd42c6b13e8f28206fb398cd55e7b7c1. No assertion/product/deadline changed; full corrected suites ran, not filtered replacements.

Deployment unchanged f10e85d008f5d217b1948e7615a273e375c044b4: fresh native verify job113929017971 in run37949102814 attempt2 through existing disposable installer/Kata/LUKS host; original full suite then coded scenes in progress. Earlier passing attempt is NOT reused. TreeDX unchanged367fec4237c6928969c969c05217bdb9832b41ac: fresh original release-gate dispatch37962656374, performance_profile=false, complete native matrices in progress. API complete suite and scenes in progress. These three prerequisites are NOT yet PASS.

API original declared .fixtures/treeseed-fixtures was uninitialized; original candidate custody rejected it. git submodule update --init --checkout -- .fixtures/treeseed-fixtures now checks out EXACT existing Gitlink940d1de721656bf84e63b60e7fbea6c86034e08b, no branch/pin/source changes. Original candidate now independently reads full nested bytes. New all-seven source digests are held in memory for subsequent comparisons. Earlier outer-source/Gitlink-only limitations remain historical, not retroactively upgraded.

Both original dev restart plans for api.service (live) and api.operations-runner (candidate), sessiondev-5007e344-493 are read-only valid; no restart yet. Correct complete public leased query returns0/page.hasMorefalse. Initial guessed --all option was rejected before network, empty stdout parsing error retained; corrected original --status leased --limit100 used. Old failed smoke reports sandbox teardown verified, but direct independent directory stat is permission denied; do not claim independent physical closure from that report.

Next: audit all three remaining fresh prerequisites, merge only checked exact repair, supported scoped API restart/build with actual selected-byte readback, then original smoke once. Strict SDK stage179 uncovered requirements and full golden remain OPEN. No count, fixture or exploratory result is a golden pass. Entire predecessor body preserved below.

2026-10-09 16:51 UTC — standalone chat source repair committed, API PR527 in full verification

#527 exact38358b5e31a1dabaadc680f936a06c8773566640 on temporary REMOTE codex/standalone-chat-source515; local remains staging, no worktree/new local branch/tag/release. Protected staging7f44f31ff520898cf179f6792115c6d4057a7d6d and main089577a6a5b139d1ab8fd64ec7e3943eafc3898c freshly fetched before delivery. Cleanup both protected merges then remote deletion remains required.

Test-first commit a8cc685: TWO UNIT+ONE real original ControlPlaneStore/full native PostgreSQL/HTTP context tests. First run2 genuine unit failures plus missing native env (retained NOT productRED); after binding existing allocated loopback disposable postgres17 fixture, ALL3 genuine failures: source refs empty instead of exactSHA, upstream denial silently accepted. Native RED /tmp/api515-standalone-chat-source-native-red-20261009.json SHA256edee861010967905f15d2be52bbbbbb6d7b961345a836207c365e52680168e46. Original failed live preflight remains unchanged.

38358b5 repair uses existing selected software tuple, managed source authority and exact resolver before issuance. Explicit existing Proposal Git context stays frozen, no source.read→no lookup, no fallback around ambiguous/denied/malformed source. No new fields, service, source pin, role special case, timing or allowance changes; original missing-context consumer denial retained.

Exact cases now in tests/unit/control-plane/capacity/execution/architecture/communication/communication-source-context.test.ts:

UNIT freezes configured source-read Git context before issuing an arbitrary configured chat assignment / api.golden.standalone-chat-source-unit.
UNIT denies ambiguous source and rejected or malformed upstream revisions without repairing communication input / api.golden.standalone-chat-source-denial-unit.
REAL native PostgreSQL and HTTP freeze standalone chat source while denials and unchanged retry preserve all stored input bytes / api.golden.standalone-chat-source-native.
All mapped original golden.verifiers/component-boundaries.scene. Scope local-component-tests, NOT managedE2E. Controlled GitHub response is input; actual original SQL/store/resolver/HTTP runs, not authentication, model/charges or physical closure. Original live guest-model-smoke retained as managed production-shaped obligation.

Complete FOUR-file focused command unchanged original Vitest config: new file +ready-execution-node.test.ts +source-workspace-service.test.ts +assignment-attempt-builder.test.ts =>95/95 zeroFAIL/SKIP/TODO. /tmp/api515-standalone-chat-source-final-green-20261009.json SHA2565674b8c9dfc9c3092c83f2ad8bec26dceb58d38ca371543bdc6be48a717eb716.
Original strict declaration buildPASS; file lengths+architecturePASS; diffcheckPASS. Initial new direct test-root count11 failed existing10 policy, fixed by intact relocation, no checker change. Initial narrow strict invocation omitted existing team-service-interface.ts augmentation and reported13 missing methods; corrected command includes it, strictPASS/emptylog. No check disabled/old assertion weakened.
Fresh full Actions/component prerequisites pending. Prior7f44 passing2009+820 is NOT this candidate. Next exact merge/readback/runtime update, then NEW acceptance invocation with fresh ALL7 complete prerequisites before original live smoke/SDK campaign. Strict179 stage gaps/fullportfolio remain OPEN.

2026-10-09 — new native SDK preflight failure: standalone chat lacks exact source context

Original Agent guest-model-smoke on seven freshly verified held candidates failed after40504ms: ACCEPTANCE_CLI_COMMAND/send communication_execution_failed. Receipt /tmp/sdk376-readiness-guest-model-smoke-20261009.json SHA25674a98f1c7d19b7d4f64d1d90a224134357af88f34fb4efb43bc87533e930eccd. No SDK campaign/proposal/workday was started; prospective helper not executed.

Exact native assignment assignment_CtvLy35dY4vRFYRgJAQBnzh2aBbY7ti9 failed with assignment_source_context_missing before model execution. Public immutable Attempt grants sourceRead=["treeseed-ai/sdk"] but contextRefs has no Git reference; TreeDX discussion workspace remains sole mutable workspace. Existing source authorizer correctly denies missing exact context; do NOT weaken that fence or synthesize authority after issuance. Actual recorded teardown verified and lease released; this is not independent physical closure/whole settlement proof.

IMPLEMENTATION_DEFECT: original ready-node workItemContext attaches Proposal Git refs for proposal-bound conversation, but standalone communication only receives TreeDX refs. Repair earliest producer using existing verified software repository selection, existing managed source credential authority and existing exact GitHub ref resolver BEFORE immutable assignment construction. Preserve Proposal supplied exact refs without following moving heads; no extra source pin/model/field/role hardcoding. Existing store.config.fetchImpl is sufficient for native controlled transport, no new adapter.

Planned focused UNIT in original ready-execution-node.test.ts: standalone source.read receives exact configured Git SHA; no permission→no lookup; already exact Proposal refs untouched; provider denial/malformed/repository ambiguity retain inputs and no success. REAL native PostgreSQL+HTTP/original ControlPlaneStore and workItemContext integration in original living-graph-postgres.test.ts; real resolver transport with controlled upstream inputs, immutable SQL reads/retry. Existing golden registry/component scene gets exact bindings, original managed smoke retained as actual live failure/pass obligation. First reproduce focused RED before repair, then original complete checks/Actions, staging→main/temporary-branch cleanup. Current completed 7f44 Actions37949363309 is passing prior candidate, NOT proof of this new defect repair or future acceptance prerequisite.

2026-10-09 — team-lock repair delivered through main; temporary branch removed

Main PR526 required Verify37887808790/job113681634930 completed SUCCESS, including complete original unit/integration suite, native PostgreSQL, native TreeDX server/client prerequisites and original coded component scenes. All required authorization/validation/candidate-build/candidate-seal checks PASS; release promote intentionally skipped (tags/releases held), not skipped prerequisite coverage.
Merged PR526 expected staging head7f44f31ff520898cf179f6792115c6d4057a7d6d -> main089577a6a5b139d1ab8fd64ec7e3943eafc3898c. Fresh fetch independently confirms same staging/main tree a5c67be6999a67b47e370f7f089ffc166729555f and staging ancestor of main. Local staging clean unchanged. Temporary remote codex/team-key-lock515 at originalsource8edc2585d2b3094dd74725937c9c3d6457321669 deleted after merge, commits retained in lineage.
Actions scene artifact11599639579 SHA2569e0468e8be1ca00ca6c8cad47626c6db88f1d91d4fd0734e5e20f96cdb321d3a; native prerequisite artifact11600041277 SHA256047bcb725c54d57043abff289d8b3422ced66e88b0d6c0d5002e89d821f5d3f7; candidate11600131094 SHA25621fab78e05ff742efb8afa5580ea4c15fc391859e804e4aadb415800a350e8f4. Exploratory source-identical merge prerequisite exception remains explicit. No new SDK run, tags, release or golden PASS. Volume storage repair remains Deployment-owned, not another API lock repair.
Full prior body retained below.

2026-10-09 team-key lock delivery: staging merged; main verification running

PR525 #525 MERGED after required full checks. Source8edc2585d2b3094dd74725937c9c3d6457321669, tested merge78759c78dfb1e775c499c2a0ffd954d7e2e48d0c, staging7f44f31ff520898cf179f6792115c6d4057a7d6d all exact treea5c67be6999a67b47e370f7f089ffc166729555f; source ancestry independently verified after explicit test-merge fetch. Local staging clean. Main5f808016ad145eef09db267e07ac9ea4c6f76b8c remains unchanged pending PR526 #526.

Required PR525 run37880845552/job113659936911 SUCCESS: original complete371files2009/2009, extra original PostgreSQL suites3+17+28 allPASS (overlapping totals not summed), native TreeDX server/client prerequisitesPASS; original coded component guarantee820/820stepsPASS including exact team-key-lock-unit and native cases. Duration1h28m47s. Original lock repair is FOR NO KEY UPDATE at three owning team locks; real independent PostgreSQL pool retains compatible foreign-key KEY SHARE while competing team writer denies55P03, no callback retries/accounting mutation.

Actions evidence:

scene artifact11596957611 SHA256c1a6c7a453e250920eea6c183655c20aaa2900e798f4d97c973aaa2a48287c65
native11597156929 SHA2563467050d9b112a271c2debde0f67b69fbc03c8064ea3a12b581624a4d52c04d5
package11597057434 SHA256ad1ccc208c31251076a1b2512b240b4ef03ab45c4624b5c4393f2acbfb99ad22
source11596768305 SHA2563d4b5ccf33e4c2ebfb6cd8709fbd42bab88585f6e56373ad42c048da67af850a

PR526 staging→main required verify37887808790/job113681634930 is still running: native TreeDX server and all client SDK prerequisites completedPASS; original npm run verify:direct running. Authorization/submission checksPASS. No protection/auto-merge changes or bypass. Remote codex/team-key-lock515 retained until checked main delivery then deletion. No local branch/worktree/tag or runtime activation. Component/full-suite pass is not managedSDKgolden/all-attempt settlement proof. Failedb9/e615 evidence and unresolved usage remain retained; no second SDK launch. Approved preservation-only32GiB storage expansion separately under Deployment834/PR854; native/live proof pending.

Delivery update — 2026-10-09 03:49 UTC

Candidate8edc2585d2b3094dd74725937c9c3d6457321669 committed primary staging and pushed ONLY remote codex/team-key-lock515. PR525 #525. Required verify37880845552 running. Initial submission-contract validate37880845583 FAILED because my PR description omitted required template fields; NOT product RED. Corrected exact-base/head authority/verification/rollback/checklist description; original validation retained, no policy bypass. Full verification/scene pending. All earlier72/72 focused evidence unchanged.

2026-10-09 — native team-key lock regression/repair; delivery in progress

Fresh exploratory SDK workday workday-b750f968-9b9b-4823-89f6-63774e93f0d8 failed before model work. Actual PostgreSQL diagnostics at03:18 UTC show a cycle involving capacity_admission_counters, reservation insertion's team foreign-key key-share lock, and terminalization team FOR UPDATE. No arbitrary callback retry or accounting rewrite.

Exact added cases / original owner maps:

UNIT tests/unit/control-plane/capacity/execution/graph/architecture/living/living-graph-contract.test.ts: "serializes graph writers without taking a team key lock that blocks reservation foreign keys" / api.golden.team-key-lock-unit.
REAL independent PostgreSQL pools / actual persistExecutionGraph + ProviderAssignmentLifecycleService.fail: tests/unit/control-plane/capacity/execution/graph/architecture/living/living-graph-postgres.test.ts: "native graph and failure-report writers allow independent team foreign-key readers while excluding competing graph writers" / api.golden.team-key-lock-native.
Original golden.verifiers.yaml/component-boundaries.scene.yaml bindings; component scope, NOT managed SDK pass/full deadlock closure.

Genuine pre-repair RED: /tmp/api515-team-key-lock-unit-red-20261009.json SHA256 75c7a3650d041b28305d7a0c68390deb960ebfa73779fadbd68af7d5d05387c3 and native /tmp/api515-team-key-lock-native-red-20261009.json SHA256 005adf2df80058af29454fae0d39430a48cecf99ff09a8be776f874a2940d2a7. Native both KEY SHARE returned55P03 rather than acquisition. Filtered REDs additional regressions NOT complete prerequisites.

Narrow repair three original team locks execution-graph-service.ts, assignment-lifecycle-service.ts, living-execution-lifecycle.ts: FOR UPDATE -> FOR NO KEY UPDATE; node/assignment locks/revision/financial rules unchanged. Two older exact SQL literals updated; no assertion removed. Native integration requires real key-share acquisition AND competing NO KEY UPDATE55P03, exact public graph and immutable snapshot. Missing-assignment failure exercises actual lifecycle lock only, NOT complete admitted assignment/usage closure.

Complete six affected files72/72, zero failure/skip/todo; /tmp/api515-team-key-lock-native-complete-20261009.json SHA256 bde02b935e7f7e3a84e8a0c8a4f34616e4b7a2be9851f6a6fa8ad5e567581713.
Exact command: node node_modules/vitest/vitest.mjs run --config ./vitest.control-plane.config.ts tests/unit/control-plane/capacity/execution/graph/architecture/living/living-graph-postgres.test.ts tests/unit/control-plane/capacity/execution/graph/architecture/living/living-graph-contract.test.ts tests/unit/control-plane/capacity/execution/graph/living-execution-graph-persistence.test.ts tests/unit/control-plane/capacity/assignments/assignment-graph-transition-retry.test.ts tests/unit/control-plane/capacity/execution/graph/persistence/concurrent-results-postgres.test.ts tests/unit/control-plane/providers/assignments/lifecycle/architecture/terminal-races.test.ts --reporter=json --outputFile=/tmp/api515-team-key-lock-native-complete-20261009.json.
Existing labelled disposable PG container/original full migrations/only allocated UUID fixture databases; no production DB changes or credentials logged. Strict original npm run build:dist PASS, file architecture/length and diff PASS. Primary staging base0150b21f79e24d8b67f9db1cd8c764dd9b6a13d0 plus nine uncommitted files. Full Actions prerequisite/scene pending on repaired candidate; no activation. Fresh all seven owner suites required next SDK launch. Storage deficit/failed b9bf1750 closure still open. Entire prior issue retained.

ALL seven fresh prerequisites verified; ready for ONE fresh exploratory SDK attempt — 2026-10-09 03:14 UTC

API37871353926 SUCCESS on protected0150b21f79e24d8b67f9db1cd8c764dd9b6a13d0: complete2007/2007 FIRST, then818 original component steps; fail/skip/todo/blocked0. Artifact11593143381 ZIP50f0312a348b7446c2c796420aa1d8f2e04d73a173024c97bbdaa768da001aa5/report22b4a6c28095f3a392cd0541d9f0904dd9b2d1677f35ecbd188f7cbe29da0c53; independent audit /tmp/api-fresh-scenes-audited-20261009.json SHA25609622abe65494d68c1052f2ed4bbc612e4f6b3b2a439089eb35246881e1d839a. All real PostgreSQL/native TreeDX checks and final cleanup passed. Native log lookup while job was running returned404/BlobNotFound, not a test failure; final artifact now independently audited.

Same fresh invocation prerequisites: SDK37871253007 563/563+218/14steps; Reviewer37871255101 174/174+87; CLI37871569979 363/363+162; Agent37871356381 920/920+644/23; Deployment37873434763 1258/1258+179; TreeDX37873481108 complete original native Rust/API/server and all four language SDK suites on both architectures, zero skipped tests. Exact commands/artifact hashes and limited native-log format exception retained below. TreeDX separate external federation live acceptance remains unconfigured/unproven, not included as a passing acceptance claim; strict golden179 missingbindings remains OPEN. No previous invocation passing receipt reused.

ALL local/remote protected staging heads independently fetched and unchanged: SDK952195376b53bf39742e64f320f2a3b109cc77c0; Reviewer1e3019fbf24163116222dc96a70c126bf3488389; CLIfef3f375e241ae5946d89b88ab87bfc5b967347f; Agent12e7cd0dd28473d4feedad8e6634473bbf6d52cc; API0150b21f79e24d8b67f9db1cd8c764dd9b6a13d0; Deployment357051df93eade6969f9eb0853fe36effd2c4d2e; TreeDX367fec4237c6928969c969c05217bdb9832b41ac. Clean primary staging, no local branch/worktree/tag.

Fresh03:14 native readback repeats exact selected Agent113dist entries and API1391 mounted tracked entries/pins with unchanged digests/build/start times; no rebuild/activation. Old e615 workday independently public-read FAILED,12failed+1expired assignments and none active; no old accounting mutation, claim reconstruction or PASS. Source admission/active-clock Reporter repairs are in held Agent and fresh tested bindings.

Proceed ONLY with original compiled Reviewer node-case.js selecting original Agent campaign.test.ts exact “Frozen SDK campaign drives planning acting review and terminal golden gates”, original native fresh Book-before-open preparation, fresh unique draft/operator/freeze; unchanged3600s/1200planning/180turn/concurrency5 and existing configured Codex subscription/model. User explicitly authorizes separate fresh exploration after irrecoverable old local custody loss; old failure/unknown usage remains unverified. No API key provisioning/replacement, no inferred usage/approval/citation/zero settlement. Research14400 mismatch remains unverified under earlier explicit exploratory exception. This is NOT strict golden acceptance or full capacity-system delivery.

Fresh-start prerequisites and handoff delivery — 2026-10-09

Human permits a separate fresh exploratory SDK attempt; the lost original claim is not reconstructed, unknown active usage is not inferred, old automatic zero rows/dispute/restored original holds stay unchanged, and the old attempt remains failed/unverified. No further historical restoration attempts or new SDK launch yet.

CLI PR291 all required checks passed; full original363/363 FIRST plus162 native component steps independently audited on exact PR test merge2671edc075c2bbf23a92a22d8d569b017eebfe22/source fef3f375e241ae5946d89b88ab87bfc5b967347f. Artifact11590229351 ZIPb90060f7170ff93d8780d989460d3e52c4b0a82cdd2533124f6432514c025b99; audit17665bc07a3651622139ba79f5410d79f5be5f9bf7d35f976a8e6ac6c09f2246. Checked ordinary main merge8bece2990d8cad42f69df987611b29c17f5f8550; same treeffbb93c7121403365654836fd5199cfffc86be79. Remote codex/provider-handoff274 deleted ONLY after fresh main ancestry proof; independent remote absence verified. Primary CLI staging stays clean fef3.

API PR523 all required contexts passed, including staging37866109947 and PR37866112390, original source/build/seal/authorization/validation. Fresh PR artifact11590117879 independently audited2007/2007 FIRST then818 steps; ZIP5fdd24a15230a1e7cc2906e7b2c513393cc676516e7163db54edd60b61299495/report12ee17280db9366219078193ebf8e2dbd32d807c3bd139d295e79a20ea42d7b0, audit5e0cd335db96f535dad6cc0e4b09c131e6faef27b1792ffe4ee0db9818d8a70b. Ordinary main merge5f808016ad145eef09db267e07ac9ea4c6f76b8c; staging0150b21f79e24d8b67f9db1cd8c764dd9b6a13d0 unchanged. These are delivery receipts, NOT reused as fresh SDK prerequisites.

Fresh same exploratory invocation: Reviewer37871255101 PASS174/174 FIRST+87 exact native steps; artifact11589988269 ZIPbbc550783c5d2e6a85e31cfd011ce74f7b5a87b3a0308e41401a995deadf86aa/reportca594e964ad98b0d574690d9efc028928f79ea809c396f7f5b424ab42285f1b4; audit0f2f9feb2d907cc4a25e0aaa7117a1b43c7c65cc10ac16227e3e0c6d14b5e367. Fresh CLI37871569979 PASS363/363 FIRST+162 original steps independently audited; artifact11590922711 ZIP6486692b0900efbfb72dbc4babf7415cf47728eab786de052be4d6f0ada0223a; auditba67461d1bcab24c263327852b78bcc523a9cd11fcc1b6135ea8944dce74b883. SDK37871253007 and TreeDX37871257369 finished success; detailed native evidence audit ongoing. Agent37871356381/API37871353926 still running, not passing receipts.

Fresh Deployment37855458313 attempt2 FAILED1257/1258: native failure-evidence fixture5417ms > original5000ms. SDK remains BLOCKED. Original failure log preserved; no timeout/allowance/prewarming/assertion removal. Small CI-only startup simplification committed deaa368cf56401e71ccdd7636e85314ba7f8bf25 in primary staging; remote PR850 treeseed-ai/deployment#850 requires full original native checks and scenes. Only same original test file: native Node24 executes same exact erasable Reviewer TypeScript without extra tsx worker; one test file needs no redundant config bundling six times; BOTH full fresh prerequisite commands additionally asserted exact/unfiltered. All6 native Vitest processes, two real complete suites, failed/retry observations/evidence/candidate immutability/cleanup/5000ms preserved. Complete focused12/12/native3073.965235ms, strict/source-shape/diff pass. Local timings do not establish loaded CI repair; waiting actual CI rather than erasing failed observation.

Discarded thread/config experiments and introduced new command-path oracle failure retained in PR850; corrected only fixture-native entrypoint expectation. Existing original deployment.golden.execution-selected-failure-evidence-native-1/component scene unchanged. No architecture/UI/product/model/cap/deadline/tag/release/host activation changes. All179 strict golden unbound criteria remain open; exploratory is not golden PASS. Entire preceding body retained below.

Recovery handoff follow-up — API accounting remains exact; local provider custody loss unresolved

After the approved Agent r3 original recovery succeeded, normal CLI handoff transiently restored released provider code and lost the original retained local claim. Independent original API native readback after handoff remains exactly SHA2564e7bdb6e5a7247a660c54742b3edd56d1e437897b044bef5093b3729193a50e0: original assignment, reservation, zero usage/ledger rows, explicit dispute and restored original two holds unchanged. Private retained native-after-provider-handoff report is an accounting readback, NOT a successful provider handoff or SDK closure.

Owning CLI repair treeseed-ai/cli#290 atcce850d52b44570c301c12ddf115b969b6628514: test-first3 genuine failures, focused32/32/full363/363/strict/layout PASS; Actions pending. No recoverable exact local claim preimage found in bounded temporary/provider searches; newest authenticated host backup predates the attempt. No reconstruction or usage inference. Human asked once for independent backup or explicit exception to retain this failed attempt unresolved before a separate exploratory SDK run. No new SDK launch. Agent #368 remains actual custody-failure authority; API PR523 main checks still running, no tags. All old rows/history/receipts retained below.

Provider consumer follow-up, no new accounting mutation

Approved operator dispute and original hold restoration/replay remain verified exactly as below. Actual r2 original Agent recovery subsequently retained/control_plane_unavailable: event audit missing or invalid despite audit present. Original claim/usage/output unchanged, one-shot allocation removed, old pollers safely resumed. Owning cause: API actual public root capacityProviderId vs Agent providerId; current canonical status/finishedAt also required correct frozen terminal handling. Agent PR381 source873060bc502f130c4c52d7729a95dac6dc849ac3 includes test-first UNIT + real original recovery/client/native HTTP/durable-store regression and original scene bindings; focused19/19, full verify passed, scenes pending. See Agent#368 exact mappings/evidence. No additional operator apply, inferred usage, new settlement, cap increase, successful handoff or SDK pass. Post-handoff independent native accounting readback still required.

Actual approved operator dispute — 2026-10-09 00:48:12 UTC

API PR524 merged through staging0150b21f79e24d8b67f9db1cd8c764dd9b6a13d0, exact e537 tree. Supported node /tmp/sdk515-disputed-zero-operator-20261008.ts rebuild|apply 0150b21f79e24d8b67f9db1cd8c764dd9b6a13d0 /tmp/api524-native-scene-audited-20261008.json succeeded. Original dev rebuild api.service/sessiondev-5007e344-493 returned, healthy new container and all1391 mounted tracked entries exactly SHA498340d8931ebe037f2c1ee2a896ca7a53ce9757839e312a823c2b8848d5e511 (Gitlink pins, NOT nested dependency/cache closure).
Actual authenticated supported assignments recover NEW keysdk-e615-disputed-unresolved-20261008/stateversion3 wrote sole eight-field unresolved audit plus separate original-settlement dispute evidence. Native PG read-only before/after: original assignment/reservation/ledger/usage rows EXACT unchanged; BOTH original12/12 actual-settlement claims restored released0; original counters0->12 and180->192 ONLY plus their original version/timestamp updates. Exactly two scoped human audits retain original rows/claims; no inferred time, erased settlement, budget cap change or new-day reset. Complete original public assignment/usage/ledger unchanged. Same supported command replay returned exact response and whole native snapshot immutable.
PRIVATE summary/tmp/sdk515-e615-disputed-zero-20261008-summary.json SHA57313064ce81cec1fc265274c581a4442789c5ca4c20f08b4b5a5328eb1e81f8; native-before e441154fa53fe8b7d2caaa99a86c6e873ac77fd2ab2368d138768780a9f1c2ff; native-after AND replay4e7bdb6e5a7247a660c54742b3edd56d1e437897b044bef5093b3729193a50e0. Actual usage UNRESOLVED/settledfalse, expired assignment/history retained; NOT zero, successful Settlement or old SDK PASS. API main PR523 freshchecks pending. Approved provider maintenance now invoked separately; no handoff success claimed before its independent readback. No new SDK run or tags.

Exact native verification complete — operator recovery candidate

PR524 head e537cc2/test merge70c5397923b40689a2a9909955a7298e7507c28b have identical tree9b5ce3efe241d9709fd490c5166af9dae5284343. All required checks PASS: verify37859771220/job113592465910, authorization37859768734, validate37859768029. Original native TreeDX server/client and all additional PostgreSQL verification steps PASS. Independent downloaded scene archive audit requires complete original2007/2007 FIRST, zero fail/skip/todo, then all818 exact component verifier steps/source digests/native test identities, no diagnostic or blocked result. Artifact11588456297 ZIP SHA2568de63f38c6dff6144ca72f2cbf7bb4457bbe5612ac6fd2394b502ae0d5abd3cd, local /tmp/api524-native-scenes-37859771220.zip; actual audit /tmp/api524-native-scene-audited-20261008.json. Component proof only, NOT managed SDK acceptance. Actual --strict whole-test diagnostics88 remain retained/unwaived; original strict distribution build PASS, no check disabled. Live dispute/provider handoff NOT yet executed; old unknown usage remains unresolved authority. Merge preserves every commit/history and failed observation, no tags.

2026-10-08 precise strict-check correction and approved operational preparation

The broad /tmp/api515-disputed-consumer-strict-20261008.log name did not make that original-tsconfig run strict: original tsconfig.json has strict:false. Its93 diagnostics are retained, not waived or called PASS. A distinct actual tsc --project tsconfig.json --noEmit --strict now completed with88 diagnostics/exit2; NONE match the newly authored operator-recovery or provider-assignment-service paths. Exact logsha256a363bc1cce1f146e312750d327da40a11c43f32adde771713d217fc43b1c837e. Original production distribution build explicitly strict:true/noCheck:false/noEmitOnError:true passed as already recorded; no configuration change/check disable or whole-test strict pass.

Primary staginge537cc2b874e25ecc0e59772549ef59e52b30d00 remains clean. PR524 native Actions37859771220 has passed original native TreeDX server and SDK prerequisites and is executing original verify:direct; complete2007 and818 coded-component evidence not yet established. No live operator dispute or provider maintenance launched. Agent staging172/main92394bb526714f02db6b092614f95768ea45a846 now checked and temporaryremote cleaned, full918 FIRST/642+23 component steps, all required candidate image checks PASS. Those are not SDK acceptance or a waiver of API prerequisites.

Human-approved operational drivers use the supported version-checked CLI, original native read-only PostgreSQL snapshots, original sealed provider configuration, checked original Agent recovery ONCE and normal trsd handoff. Fresh no-active checks before/paused/after; no direct SQL writes, claim deletion, invented measurement or new SDK run. Prepared drivers pass actual strict noEmit with Node-native TypeScript import support; generated probes come from TypeScript. Unexecuted operator driver source2c9c97752f9089c65fc90fdb174cb1f5c7556436e856bb67be88f1f98883e7c6. Original oldzero, earlier denial and all failed history remain retained. Apply audit only after full native CI exact independent readback; restore only original12+12 holds once.

All prior evidence/history retained verbatim below.

Consumed dispute provider read repaired and pushed; fresh native delivery pending (2026-10-08)

Test-first7ea23bc2 retains genuine13/11PASS/2FAIL (1445cae14de20bc88b5fdc41c06e560c3108948a22e84bba1f22764568acb7e2) before e537cc2 owning read repair. Original provider.show keeps released reservation authority; disputed consumed rows expose the same eight-field audit ONLY with matching original settlement.disputed action/team/resource/provider/member/key/actor/type. No rewrite of consumed row/ledger/usage, no new schema/field/route or parallel recovery. Every earlier negative remains retained. Same existing independent-PG cases strengthened to read exact audit through BOTH original native connections, not a mocked provider consumer.

First attempted SQL repair contained one extra closing parenthesis: first13/11PASS/2FAIL report f5100b32dedcc45f14b9372db5db549efff4f7b3e6bf06d9e9b4873f86650ae9 is INTRODUCED repair syntax failure (also affecting original released read), NOT new baseline product RED. Exact syntax correction keeps all assertions and passes13/13 (7d794210daca21ea241b75446eaf8cbf55a61490c02b279aa85fdcf625165821).

Fresh COMPLETE original six focused files with owning disposable native PostgreSQL27/27 PASS0fail/skip/todo. Same original six-file/config command below, current report /tmp/api515-disputed-consumer-native-green-20261008.json SHA66d0e7f3f086e5113eb05c1fa2f1791501ea74432dd3c429939d83099625c4cc/logc51a9a5956ca3bdd5ad17b32e0594956fb347ae2fe595c511d74287d9963e89a. Original npm run build:dist PASS14d9a4d3da9b8735b37a1290645b0e065d45c6c4b59fe370351fcd06cf6db937; original shape PASSfbacdb40e05886248ba25f8dd07cbbcc13f56a62c46de1ec310762c967038810; diffcheckPASS. Original whole tsconfig.json diagnostic FAILED93 TS errors, zero matching diagnostics in edited recovery/provider paths, SHA beb257564b3aa22b6a04bb9378fa25eda97954d2f09fcb95b1b09ad0c39a856f. NOT whole strict-test PASS or waiver; no config/check disable.

Owned native Postgres container0f6d4fe42e43bc29d28beeb62f59d6c86e72ec30ca9c58e46c61fa1d37f7aba0 STOPPED/REMOVED after original allocated-database cleanup and independent name inventory empty. Only allocated test resource removed; installed/live database and old quarantined fixtures untouched. No test deadline/allowance/concurrency change.

Same temporary PR524 updated/pushed e537; exact body/head independently read back. New818 component bindings/full2007 test inventory must receive fresh original configured native full checks FIRST; old91f run cannot prove new bytes. Primary local staging clean, no local branch/worktree/tag. Live operator dispute, poller pause/recovery/handoff and SDK launch remain HELD. Prior authoring/RED/repair/environment failures and entire earlier body retained below.

Disputed consumed audit consumer regression reproduced; live mutation HELD (2026-10-08)

Before live recovery, ORIGINAL provider-assignment-service.show was found to expose the existing unresolved audit only for reservation.state=released. Approved dispute deliberately preserves the consumed zero-settlement row, so its provider consumer would not see the audit. This is now reproduced, not merely source inspection. No new SDK run/provider pause/live accounting mutation occurred.

Two focused regressions appended in original recovery files; all older cases/negative assertions retained. Exact maps:

UNIT request/output/auth/immutable-input boundary: tests/unit/control-plane/providers/assignments/architecture/recovery/operator-recovery.test.ts — "reads the exact operator audit for released or disputed consumed reservation authority without invoking productive lifecycle operations" — api.golden.operator-settlement-dispute-read-unit / step operator-settlement-dispute-read-unit. Mocked repository input/SQL-request checks are UNIT only, not SQL semantic or native authority proof.
REAL owning provider.show + existing operator.recover + original settlement + native PGlite SQL: tests/unit/control-plane/providers/assignments/architecture/recovery/operator-recovery-native.test.ts — "native provider read exposes only matching disputed consumed recovery audit and retains original zero settlement and restored claims through repeated reads" — api.golden.operator-settlement-dispute-read-native / step operator-settlement-dispute-read-native. Requires positive actual audit read after consumed dispute, no-audit denial before, exact ownership and changed dispute team/provider/member/resource/key/actor/action denials, concurrent/repeated reads and immutable accounting/audit rows. Controlled principal/fixture rows are inputs, not authenticated API HTTP/model/usage/managed E2E.
Both bindings authored in ORIGINAL golden.verifiers.yaml/component-boundaries.scene.yaml using existing vitestCase/ownerPackage contract. Component scope, NOT executed scene or managed acceptance. Initial new binding authoring used wrong type/scope spelling and was corrected before metadata execution; no schema/runner/timeout change.

COMPLETE original two-file command on held source91f35bc1a4279bb394796ce115f8338132a85bd0 plus new uncommitted test bytes: PATH=/tmp/sdk-native-node2412-PjB5qe/bin:$PATH node node_modules/vitest/vitest.mjs run --config ./vitest.control-plane.config.ts tests/unit/control-plane/providers/assignments/architecture/recovery/operator-recovery.test.ts tests/unit/control-plane/providers/assignments/architecture/recovery/operator-recovery-native.test.ts --reporter=json --outputFile=/tmp/api515-disputed-consumer-red-r3-20261008.json
Final RED13/11PASS/2FAIL/0pending: native exact audit missing; unit consumed/dispute query boundary missing. Report SHA1445cae14de20bc88b5fdc41c06e560c3108948a22e84bba1f22764568acb7e2. Earlier same13/11/2 reports retained cddeaf5f360c335e819d9a278ba9a473ded52b9f17ff76cd1d29973fd729129d/ef33dfda0681d74c2fb62b1a45660cb9149fb206242f74781ee2d32ceb02dfce; source-only typed mock cleanup removed introduced casts/no compiler failure or weakened assertion. Original npm run build:dist PASS log14d9a4d3da9b8735b37a1290645b0e065d45c6c4b59fe370351fcd06cf6db937. Product still unchanged for this regression; test-first commit next, then smallest original read-boundary repair.

Approved maintenance preparation only: original Agent prepare-only manager/runner build PASS, source172c8263637a88216fe30d1c58772a7325270cb6/SDK9521953/Deployment911ce2c all tracked clean before/after. Original copyDevelopmentRuntime/private runtime readback materialized5452files/509751949unique bytes/digest sha256:87c18d04b4bfa8969132624be45190e9ecd25d4ff052c644185aabb521c77151; build log93f388a89f97b624803093b27ce6081b98de9f92a6016c29a9ee852bd5662b4a. No live provider stop/switch/recovery. Full CI source91f still pending; new consumer defect must be batched into same PR524 and fresh complete native checks before live recovery. Older pending checks cannot prove new candidate.

APPROVED retrospective dispute implemented; native focused25/25; delivery pending (2026-10-08)

Human explicitly approved automatic-zero dispute/original unmeasured hold restoration AND bounded verified old-poller maintenance handoff. Earlier pending-approval statements remain historical below. No live accounting mutation, provider pause, forced handoff, inferred usage or SDK launch has occurred.

d956425 failing native tests + original scene bindings FIRST, 12377ba corrects a negative fixture whose released3/reserved2 hit the original DB constraint before recovery. First10/8PASS/2FAIL comprises genuine positive recovery denial plus introduced invalid fixture (9ddcdc1abbdcf9654cda5cd19dbafc1e00702644509f690a60da57cd1eb96cf5). Corrected RED10/8/2 (63d8067be6fce49b4eecd1d0f625edadd0a5a7afeecfa77f63d64c3b609a484f): both final valid-input recoveries denied, no valid claim restored. First repair also failed10/8/2 because it incorrectly expected team/member/reservation columns on usage rows; source read of original usage writer corrected that introduced boundary mistake without new columns. Partial report retained, NOT additional product RED.

91f35bc repairs original OperatorAssignmentService only. Existing exact-version authenticated recover command/body and eight-field unresolved read-back unchanged; no new endpoint/schema/table/runtime policy/role hardcoding. Original consumed reservation/ledger/usage/assignment rows stay byte-equivalent; existing audit action assignment.settlement.disputed retains original ledger, usage and released claims, while existing assignment.usage.unresolved remains the sole provider disposition. The distinct dispute fact needs its retained old accounting/claim snapshot; it is NOT a replacement successful settlement or copied usage authority. Require exact original automatic deadline source,0/0, absent original active clock, same identities, no measured native/token/cost/aggregate or incremental usage, original fully released period claims/owning counters, native workspace closure. Restore ONLY original amount by addition (never reset shared commitment); leave terminal concurrency released. Both period and actual-settlement release policies tested. Fail closed malformed/foreign/moved/actual measurement/unrelated source or inconsistent claims; transactional late audit interruption rolls back every represented write; matching independent calls/replay produce one dispute+one unresolved audit.

Exact new ORIGINAL mappings:
UNIT operator-recovery.test.ts — keeps settlement dispute authority server derived and rejects every caller hold refund settlement or measurement before recovery — api.golden.operator-settlement-dispute-unit.
UNIT SAME file — requires exact original deadline zero identities and absent active clock without treating native or malformed facts as disputable — api.golden.operator-settlement-dispute-authority-unit. Direct owning predicate boundaries/immutability, not native accounting proof.
REAL public service/original PGlite SQL operator-recovery-native.test.ts — native recovery disputes only original automatic zero settlement and restores original period holds once while retaining all failed and accounting bytes — api.golden.operator-settlement-dispute-native.
REAL SAME file — native settlement dispute rejects measured foreign moved corrupt and unrelated settlements or claims without accounting changes — api.golden.operator-settlement-dispute-denial-native.
REAL independent PostgreSQL connections/full original migrations/public OperationRegistry operator-recovery-postgres.test.ts — native PostgreSQL settlement dispute restores only original holds after atomic audit rollback and independent matching calls without rewriting zero history — api.golden.operator-settlement-dispute-postgres-native.
All paths under tests/unit/control-plane/providers/assignments/architecture/recovery/. Exact binding/steps in original golden.verifiers.yaml/component-boundaries.scene.yaml; now816 component refs,2005 total full tests. Older PostgreSQL case/assertions retained through SAME owning shared exercise; no new support file/runner. Controlled settled inputs are NOT actual provider-generated charges, native authenticated operator HTTP or managed physical closure.

Fresh original SIX COMPLETE files25/25 PASS zero fail/skip/todo:
TREESEED_TEST_POSTGRES_URL= PATH=/tmp/sdk-native-node2412-PjB5qe/bin:$PATH node node_modules/vitest/vitest.mjs run --config ./vitest.control-plane.config.ts tests/unit/control-plane/providers/assignments/architecture/recovery/operator-recovery.test.ts tests/unit/control-plane/providers/assignments/architecture/recovery/operator-recovery-native.test.ts tests/unit/control-plane/providers/assignments/architecture/recovery/operator-recovery-postgres.test.ts tests/unit/control-plane/providers/assignments/architecture/recovery/operator-recovery-workspace.test.ts tests/unit/control-plane/providers/assignments/lifecycle/architecture/terminal-performance.test.ts tests/unit/control-plane/capacity/workdays/lifecycle/architecture/terminalization-persistence.test.ts --reporter=json --outputFile=/tmp/api515-settlement-dispute-native-green-r2-20261008.json
Report fe661872446f128b9d71a65f46f250d9848704e0fd0852503b0beb546ec5d031/log cc5ca7a77df4e05864988a3e083bfc2a9fbf0ad2e7b7be6dd23fe2a8b1a30fb5. Original strict build14d9a4d3da9b8735b37a1290645b0e065d45c6c4b59fe370351fcd06cf6db937 / shape fbacdb40e05886248ba25f8dd07cbbcc13f56a62c46de1ec310762c967038810 PASS. Disposable original CI-pinned Postgres17.11 image allocated ONLY for tests, original fixtures cleaned their databases; exact owned container stopped afterwards. Installed live database never used for tests. Focused25 is NOT full prerequisite evidence; no local scene.

Primary staging only, new source91f pushed SAME temporary remote PR524. Fresh original configured native CI37858019669/job113586800447 pending. Metadata37858018272 failed stale previous headce72 ONLY; PR body now records exact91f, edited validation follows. Platform approved docs PR637/638 checked and merged staging598d108cf3bf4ef1484d6b07d260e74a3b31f40c/main9aa15c8b5b6c8b768f5756505d3458d7745a46d9, temporary doc branch deleted after main ancestry. No tag/local branch/worktree/UI/model/allowance/deadline change. API delivery/live recovery/maintenance/full SDK acceptance remain OPEN. Entire earlier body retained below.

Fresh local complete-suite failure; native Actions pending (2026-10-08)

Held ce72d38 original unfiltered command:
PATH=/tmp/sdk-native-node2412-PjB5qe/bin:$PATH node node_modules/vitest/vitest.mjs run --config ./vitest.control-plane.config.ts --reporter=json --outputFile=/tmp/api515-unknown-terminal-time-full-20261008.json
2000 total/1894 passed/96 failed/10 skipped/0 todo; success false. Report SHA256 78275d88053f4fe92750c4e20b5aa41238d12c7a90e764702b0ee23be77d345f. Compact complete failure classification: 69 require explicitly configured disposable PostgreSQL (47 ARCHITECTURE_POSTGRES_REQUIRED plus 22 TREESEED_TEST_POSTGRES_URL); 27 require disposable native TreeDX conformance URL/token. All 10 skipped cases are existing PostgreSQL-gated browser sessions, identity mapping, restricted runtime, principal store, pool budget, workload registration, and replication migration. No empty failed suite. Missing environment/skips remain unproven; local result is NOT prerequisite PASS and no local scene/SDK run followed. No installed live database used, skip removed, fallback, deadline extension or narrowed command.

PR524 configured native Actions37855691932/job113579183652 pending, authorization37855692042/validation37855692041 passed. Original native CI supplies disposable PostgreSQL and owning native TreeDX. Old PR523 checks pending independently. Focused 11/11 is additional regression evidence only; it does not waive full native prerequisites. Future terminalization fix does not alter existing old zero-settled accounting. Retrospective dispute and original hold restoration remain a separately requested architecture extension, not implemented; original recovery denied consumed reservation as designed. No new SDK run until old recovery resolved. Entire earlier body retained below.

Future unknown-time terminalization repair: test-first delivery PR524 (2026-10-08)

Base protected staging b7d23f7 verified fresh. Primary local staging only. 84bf8e0 committed failing original unit/native+scene bindings FIRST; 1b85c63 strengthens native inputs across expired/failed/cancelled AND BOTH original held reservation states; ce72d38 repairs original shared measurement gate and original unsettled query. Temporary remote codex/unknown-terminal-usage515 / #524 only; no local branch/worktree/tag.

First complete two-file RED11/9PASS/2FAIL0pending: unit failed to throw unknown time, native falsely returned success. Report d547c5fcdcb8216af12abad7503def8950b22b960630909bfa8f20fb326a9ad3 / log bfff4568c4190a62674c82d22d9303b73833acab893f15a5332e4151b77c1a15 (/tmp/api515-unknown-terminal-time-red-20261008.*). The existing fixture uses consuming, not reserved: this exposed ignored held-state closure, NOT proof that that particular first native invocation inserted zero. Initial expected-state literal corrected by stronger explicit BOTH-state matrix, no removed assertion. Partial measurement-gate repair still11/10/1 (misnamed green file retained as FAILED52490c9420d008b0129cd1bbad5b086f45d148ab23b675ad6d92cf33081417c6). Strengthened RED-r2 also11/10/1, 7642799b1f4bb31e9e60556af98fa6be6254ffa1ed061e889e674de359b6e810. The original gate required measurements only after executionStartedAt, and unsettled cleanup selected only reserved. Final owning repair requires measurements when already-classified operator-action AND includes consuming; no duplicated policy, new representation, inferred measurement or historical rewrite.

Final complete focused11/11 PASS0pending fd5c9c5f3283d8bbc7aed0ad613b07239dd4880f6c2603f2982a4bcad4f861e5 (/tmp/api515-unknown-terminal-time-green-r2-20261008.json). Every older case retained; six native combinations deny/retry with exact original assignment/reservation/usage/ledger/counter readback. Original shape/build PASS fbacdb40e05886248ba25f8dd07cbbcc13f56a62c46de1ec310762c967038810 /14d9a4d3da9b8735b37a1290645b0e065d45c6c4b59fe370351fcd06cf6db937; diffcheckPASS. Full unfiltered local original suite running on ce72; PR524 fresh full native Actions/component scene811 pending. Component maps are obligations, not managed SDK proof. No scene starts before fresh complete prerequisites, no old receipt reuse.

Actual old-run recovery remains denied correctly by consumed settlement guard; no new audit, old zero-row/counter/claim mutation or SDK run. Additional retrospective dispute/original hold restoration and verified bounded provider maintenance remain awaiting human approval. Selected API b7 source proof was point-in-time BEFORE these later edits, not ce72 loaded-runtime proof. All preceding evidence retained below.

Unknown operator-action time: deadline zero-settlement regressions (2026-10-08)

The actual old Reporter recovery denied capacity_recovery_reservation_conflict. Independent READ ONLY native SQL corrected the prior premise: reservation already consumed by capacity_workday_deadline_terminalization at 2026-10-08T21:00:32.520Z, with aggregate/ledger active0 elapsed0 and original period claims released. No new unresolved audit, inference, old-row change or SDK run. Existing settled-history guard is retained. Additional retrospective dispute/budget restoration is awaiting explicit human approval; prior failed observations remain unchanged below.

New original owning maps, authored before product repair:

UNIT tests/unit/control-plane/providers/assignments/lifecycle/architecture/terminal-performance.test.ts: "requires actual time for an operator-action recovery even when its original active clock never started" -> api.golden.operator-unknown-terminal-time-unit.
REAL native owning repository/service/original SQL tests/unit/control-plane/capacity/workdays/lifecycle/architecture/terminalization-persistence.test.ts: "native deadline terminalization retains unknown operator-action usage and every original budget claim without fabricating zero settlement" -> api.golden.operator-unknown-terminal-time-native.
Both bound in original golden.verifiers.yaml and component-boundaries.scene.yaml; step IDs omit api.golden. Unit requires both measurements for each existing operator-action reason, exact denial and input immutability; measured positive and truly unstarted zero-release retained. Native expired/failed/cancelled supplied inputs, original absent clock, retained report/elapsed1, actual overlapping calls+retry must deny409 before aggregate/ledger/reservation/counter/assignment mutation. PGlite overlap is NOT independent PostgreSQL concurrency or native provider measurement/physical closure. Component scene obligations are NOT managed golden proof.

Focused complete two-file command (not yet run): PATH=/tmp/sdk-native-node2412-PjB5qe/bin:$PATH node node_modules/vitest/vitest.mjs run --config ./vitest.control-plane.config.ts tests/unit/control-plane/providers/assignments/lifecycle/architecture/terminal-performance.test.ts tests/unit/control-plane/capacity/workdays/lifecycle/architecture/terminalization-persistence.test.ts --reporter=json --outputFile=/tmp/api515-unknown-terminal-time-red-20261008.json
Base staging b7d23f7; new tests uncommitted. No product repair or acceptance launch yet. Any eventual scene needs fresh complete owning prerequisites on exact candidate FIRST; no old receipt reuse. All previous assertions/history preserved.

2026-10-08 ACTUAL recovery DENIED; earlier "unsettled Reporter reservation" diagnosis corrected by native read-only evidence

PR522 merged with full checked evidence to stagingb7d23f7a1d350c868edc67cd02e783851d150e9b; mainPR523 open/checks running. Original supported dev rebuild api.service completed22:32:37.786 (started22:27:34.744), with original declared dependent operations-runner reaction, not another SDK campaign. Independent /tmp/sdk515-unresolved-api-selected-byte-readback-20261008.json proves healthy API restarted22:27:38.533, exactsource-entrypoint src/api/support/server.ts and ALL1391 tracked mounted bytes/Gitlink pins SHA256e0a6ce1f4de571740eec1f11d9ade05b7fbcaed3c31da7b06c3551697745ce34 with readonlypackages mount. Scope NOT nested dependencies/cache/managed closure. CurrentgenAPI951/runner817, Agent632 unchanged.

Original /tmp/sdk515-e615-apply-unresolved-recovery-20261008.ts independently read SAME complete original expiredassignment/version3 before actual assignments recover exactreason/key. The actual command DENIED capacity_recovery_reservation_conflict / Original held reservation authority is required. Protectedstdout empty/stderr543bytes retained /tmp/sdk515-e615-unresolved-operator-20261008-recover.err; not authfailure and no recovery audit. Do NOT retry by refreshing version/removing guard/altering DB or pretend financial success.

Necessary narrowly scoped native read-only diagnostic through SAME actual API container/database credential binding and original createControlPlanePostgresDatabase, BEGIN REPEATABLE READ READ ONLY, no DDL/migration/writes, exposes source of wrong earlier premise. SAME reservation matches all six owning fields/reverseassignment; state CONSUMED/settlement token present/no usage-report token. Existing ledger5620509e-75f8-42d2-a83f-d9cd5c67b89f is task_completed_actual_settlement active0/elapsed0, source capacity_workday_deadline_terminalization, created2026-10-08T21:00:32.520Z. SAME aggregate usage row usage:assignment_mYh-sJNy-VlyPeey4MFFj4mkjM_cgoHk:1:aggregate also0/0 atthatclock. Earlier informational diagnostic-0 row0/0 at20:00:33.964 remains. TWOoriginal12-unit counter claims actual-settlement bothreleased12; originalproviderlocalclaim stillretains unknownclock/output/12periodhold. Zero unresolved audit. Thus earlier inference from local retained custody that API reservation was unsettled was WRONG; public usage25/ledger12 baseline already contained these historical rows. Preserve baseline/olddiagnosis as failed observations, not silently rewrite them.

Reports /tmp/sdk515-e615-recovery-reservation-readonly-20261008.json and readonly-r2-20261008.json retain metadata only, no token values. Initial extra counterquery used nonexistent counter.release_policy (42703), READ-ONLY diagnostic error NOT productRED; corrected ORIGINAL claim.release_policy after schema/source read, no data mutation. Missing guessed source paths/template lowercase reads retained as read errors, not execution failures. Nativeclock did not start, so zero settlement is not established honest active usage and cannot be reconstructed retrospectively. Actualrecover rightly refuses alreadysettleddata. NEW async architecture/accounting approval requested: explicitly dispute automatic zero settlement preserving oldrows, retain unknown usage and restore ONLYoriginalunmeasuredbudgethold. No approval/reply yet, no such implementation or live mutation. Independent future deadline-zero regression/earliest owning repair can proceed within existing no-fabrication architecture. Previous bounded maintenance handoff approval also outstanding; no poller force stop/claim deletion/nativeusage inference/newSDKrun.

MainPR523 initial metadata validation37853580088 failed original checklist wording only; corrected full original six checked items, followupvalidate37853665130/auth37853665070 PASS; no source/full-suite rerun. Detailed oldsourcefailures/evidence below unchanged.

2026-10-08 exact recovery candidate Actions and all component evidence PASS; live application pending

Primary clean local staging/source2f442d1dfb2286c18bfbdb7f397e065eaade1b58. PR522 required verify37846944991/job113550047138 PASS56m58; authorization37847011311 andvalidate37847011365 PASS. Actual checked PR mergeeba6e68ec3565a69b98b7d6f5255530919800d1d tree independently equals2f source. Original complete native TreeDX server+client prerequisites, verify:direct build+FULL1998/1998/no skipped/todo, actual PostgreSQL backup migrations/transactional identity/independent pools+allocation, pack and native cleanup all PASS. No old prerequisite receipt reused.

THEN same fresh owning scene invocation actions-37846944991-1 passed ALL809 original component cases from21:43:23.908 to22:24:35.609. Every selected ref/order/source SHA256/exact case/result/evidence/process exit/signal/prerequisite commit+unfiltered command/1998 counts independently audited against exact source. Includes ALL nine api.golden.operator-unresolved-recovery-{postgres-native,counter-native,workspace-native,unit,input-unit,native,denial-native,overlap-native,interruption-native}. Scope local-component-tests, NOT live operator or SDK/model/provider/native charge proof. Artifact11582279216 ZIP /tmp/api522-scenes-37846944991.zip SHA2560aab26f79ebd77902ecd4ad5f4d39ccba662354a8015e45f26f2368636408a95; exact report SHA256a1acab316d0e08e6360f83600d2ab220db0688ca64b9f9d0ee54e5f8adabe381. Native-prerequisite-evidence artifact11582368951 retained. Earlier declaration failure, introduced typing errors and all genuine focused REDs below remain unchanged.

Checked staging/main history merges and temporary remote branch cleanup follow. Actual old Reporter stateVersion3/expired/reservation remains unchanged; no financial recovery/audit applied yet, no new SDK campaign. Approved next action is original api.service rebuild with independent actual restarted healthy mounted-source byte read-back, then original trusted operator CLI assignments recover exactversion3/reason/key. Unknown usage must remain unresolved/settledfalse with all period holds/history retained. Original provider handoff cannot consume this newly delivered audit until checked new Agent code runs; separate bounded maintenance handoff approval question is outstanding, no guard bypass/claim deletion/parallel productive polling authorized or executed.

Complete current API suite PASS / live pre-recovery baseline

Exact2f442d1dfb2286c18bfbdb7f397e065eaade1b58 COMPLETE original vitest.control-plane.config.ts1998/1998 zero failed/pending/todo, source/tree+127 exact checked TreeDX dependency files+installed SDK bytes held throughout. Original build:dist PASS. /tmp/api515-unresolved-recovery-full-20261008.{ts,json,log}. Current required Actions/scenes37846944991 still pending, no receipt reused for managed acceptance.

Read-only original CLI baseline /tmp/sdk515-e615-unresolved-before-r2-20261008-summary.json at21:39:58: expiredReporter assignment_mYh-sJNy-VlyPeey4MFFj4mkjM_cgoHk stateVersion3; exactoriginal claimb09e7368-e74e-4271-9e96-1017d3cabf85 recovery/no activeStartedAt/no activeFinishedAt, requested12 held. Claim custody19eb9a207de4b5d46e684cd4232e2e33fae9a4e64232aa686481c590e310d1a7, outputa09b0be042594927aeada6051e5ca2bcfd5f8396b8313711146b083dd98f786f, originalfailure26d2299c6ded7334bc23989044f3b594348c1c57b06d74c91569de26536f36a1 and dispatchf89a5a34380828f0fd8f81cf779fc278dae7498058e73ea1a26eef4ec25de69f retained. Complete scoped usage/ledger readbacks before any mutation, private credentials never printed. First baseline attempt omitted required project option and failed before capacity read (invocation error NOTproductRED); r2 supplied originalassignment.projectId and passed, all receipts retained. No recovery/settlement/charge/provider deletion/deadline extension/newSDKrun applied yet. Current unknown remains unknown.

Approved recovery current candidate `2f442d1`

PR522 open; current Actions37846944991/job113550047138. Same nine mapped regression cases retained; native positive strengthened through original public ProviderAssignmentService.show/native SQL, returning only original owning audit as read-only unresolvedUsageRecovery. Foreign provider403 and input/state immutability retained. Sole original audit remains authority, no new table/measurement/settlement. Test-first69b636be RED16/15/1; productef22896b green16/16. Logs /tmp/api515-unresolved-recovery-provider-audit-{red,green}-20261008.*.

Initial PR522 run37845414186/job113544946489 failed original build declaration on unknown SDK body spread; native server/client prerequisites and cleanup passed, scenes skipped NOT passed. Local strict diagnostics retained /tmp/api515-unresolved-recovery-strict-20261008.log, unrelated original errors unwaived. Candidate2f uses strict record/number/string narrowing, no casts/check disabling; original build:dist r2 PASS /tmp/api515-unresolved-recovery-build-r2-20261008.log. Complete original control-plane suite running with exact source/dependency custody in /tmp/api515-unresolved-recovery-full-20261008.ts; log/report same stem. No current whole-suite PASS claimed yet. No live Reporter financial recovery applied; unknown stays unknown. Existing native workspace closure prerequisite, once-only reservation/terminal counter release, period hold, retained failure/report and zero UsageActual/ledger unchanged. All prior evidence retained below.

Approved unresolved recovery — owning native counter/executor closure, 2026-10-08

Primary staging candidate85fa11dedcd3044b371c6966c2d245b9a6d8ebe6, test-firsta5136089 then20fd763a before owning repair3666a7e3; exact SDK pin952195376b53bf39742e64f320f2a3b109cc77c0 commit85fa11de. Native focused original complete five files plus public binding test:16/16 PASS including actual independent PostgreSQL connections/full migrations, native workspace close/readback, actual late-audit SQL rollback/retry, stale/foreign/live/measured authority denials and exact idempotency. Genuine new orphan-counter and executor mismatch RED16/14/2 SHA02af1188bc7f05ba830c4eaeb2f5a3a47aa6de0726d0f2b0274fd9c408ea9a7b; repaired report /tmp/api515-unresolved-recovery-native-authority-green-20261008.json SHAaa8d9720cc8420b287315d53a5641e1e56e75523d181326902d596a67d846d26. Component SDK source alias in focused fixture ONLY, not delivery build/dependency custody. Original whole suite/build/strict/Actions/scenes still pending on checked installed dependency. No live financial recovery or SDK campaign.

Nine mappings ORIGINAL tests/unit/control-plane/providers/assignments/architecture/recovery/: operator-recovery.test.ts unit+input-unit; operator-recovery-native.test.ts native+denial-native+overlap-native+interruption-native+counter-native; operator-recovery-workspace.test.ts workspace-native; operator-recovery-postgres.test.ts postgres-native. IDs api.golden.operator-unresolved-recovery-, original golden registry and component-boundaries scene, exact prior cases retained. New counter case denies orphan terminal counter claim with whole original native snapshot unchanged; reservation execution provider must equal owning assignment, denial before native closure/write. Original audit remains sole unresolved-usage authority, no UsageActual/ledger/zero settlement; terminal-only reservation/counter concurrency released and period holds retained. Actual expired Reporter recovery remains NOT applied. Remote temporary PR branch codex/operator-unresolved-recovery515 only; local staging, no tag/worktree.

2026-10-08 approved unresolved recovery — focused native15/15 PASS; not yet applied

Current API authoring stays staging; test-first a513608 preceded implementation. Eight exact bindings under original golden registry/component scene: api.golden.operator-unresolved-recovery-{unit,input-unit,native,denial-native,overlap-native,interruption-native,workspace-native,postgres-native}. Files now tests/unit/control-plane/providers/assignments/architecture/recovery/{operator-recovery,operator-recovery-native,operator-recovery-workspace,operator-recovery-postgres}.test.ts; moved intact to retain original10-file rule. Independent native PG fixture FULL original migrations preserves constraints; original controlled membership/provider/project/class/executor rows seeded, retired empty fields explicitly asserted before omission. r1/r2/r3 seed failures retained, NOT product RED. /tmp/api515-unresolved-recovery-native-r4-20261008.json 15/15 zero failure/pending/todo via original vitest.control-plane.config recovery directory+complete assignment-operations file, pinnedNode24.12 and disposable localhostPG; SDK_SOURCE_ROOT explicitly component-only, not delivery dependency closure. Product releases ONLY terminal counter claims/reservation, period claims held, assignment/report bytes unchanged, sole existing audit says usageStatus unresolved/settled false, no usageActual/ledger/settlement. Existing native workspace closure required. API strict/full/Actions/scene/checked merge/runtime still pending; SDKPR385 new existing product-custody scene selection must pass before exact dependency delivery. Old Reporter NOT recovered yet; SDK run held.

Agent checked staging delivery, operator recovery in progress

PR375 merged with lineage preserved to staging9931597ea6dbb603702577e2d33997f65e28a2bb after validate37838775512+verify37838778972 PASS. Independent scene ZIP SHA4491142fc176b4c7dac15ea6d89e83847a2565345e8fa5b3cb83cdc33c582f61 audit proves original636+23 exact component steps and fresh complete912/912 prerequisites on source-identical CI mergecae5a8b356edc6309416432f3bb65a8111653c82; every test identity/source digest checked; reportSHAb88d72677a733e80f4395010c6687186e4c75a43e76816aa737563280b13dda9. Primary staging fast-forwarded; exact remote codex/canonical-sandbox-attempt368 deleted after ancestry readback. Main promotion PR376 OPEN/checks pending. App attachment attempt failed existing100-identity cap, no attachments removed. No tag/release/activation/SDK launch.

Approved recovery test-first APIa5136089 and SDK2daff997 precede implementation. Focused API9/9 and SDK3/3 PASS; new REAL native HTTP workspace denial/closure case and SDK client exact recovery transport case added. SDK full suite in progress. API original layout denied12 files in architecture directory; same three new test files moved intact to architecture/recovery (imports+registry paths only), original500/10 policy unchanged. Native PGlite is not independent PostgreSQL concurrency; controlled native HTTP is not actual TreeDX/Kata. Old expired Reporter remains unresolved until checked operator operation is delivered and applied. No zero settlement/UsageSettlement/native measurement invented.

Unresolved recovery test-first RED — approved contract

Eight new cases authored, existing assertions retained. API two UNIT cases in tests/unit/control-plane/providers/assignments/architecture/operator-recovery.test.ts (team-management/context-derived actor; exact version/reason/prohibited-field denial) and four REAL owning public-service/PGlite transaction cases in operator-recovery-native.test.ts (once-only release/no settlement/immutable expired output; active/foreign/stale/measured/mismatched denial; matching overlap; late audit rollback/exact retry). Verifiers api.golden.operator-unresolved-recovery-{unit,input-unit,native,denial-native,overlap-native,interruption-native} bound in ORIGINAL golden registry/component scene. SDK two UNIT cases tests/unit/operator-contracts/assignment-recovery.test.ts (strict operation contract; one generated command) mapped sdk.golden.operator-unresolved-recovery-{unit,command-unit} in ORIGINAL golden registry/product-custody scene. Component scenes declared, NOT yet executed or managed E2E.

Focused complete-file commands: API node node_modules/vitest/vitest.mjs run --config ./vitest.control-plane.config.ts tests/unit/control-plane/providers/assignments/architecture/operator-recovery.test.ts tests/unit/control-plane/providers/assignments/architecture/operator-recovery-native.test.ts; SDK node node_modules/vitest/vitest.mjs run --config ./vitest.contracts.config.ts tests/unit/operator-contracts/assignment-recovery.test.ts (Node24.12). API base2de93c9:6/6 FAIL missing public recovery implementation; SDK basef43bd785:2/2 FAIL missing catalog/command. Native SQL fixture resources close in finally. Reports /tmp/api515-unresolved-recovery-red-20261008.json SHA5928f60d1355a810d2071c72c0d9c2e806b56251b122f958d59e0eb250076c29; /tmp/sdk376-unresolved-recovery-red-20261008.json SHA798ad637a696ad5e8f9890fe996c9ae759ec9b474749c12319cc3ecc04948da4. Missing-method RED is not evidence of implemented recovery, strict compilation or acceptance. Preserve terminal counter release only; period-budget claims retained because unknown actual consumption cannot justify a refund. No native measurements/zero ledger/UsageSettlement invented. Whole native recovery delivery and SDK acceptance remain OPEN.

APPROVED: explicit unresolved-usage operator recovery (2026-10-08)

Human approved narrowly authorized recovery of expired Reporter assignment assignment_mYh-sJNy-VlyPeey4MFFj4mkjM_cgoHk before another SDK run. Author unit, real public-boundary/persistence integration, and existing coded scene/guarantee cases first. Release held capacity while explicitly retaining active usage as unresolved: NEVER zero usage, fabricated native measurements, successful UsageSettlement, lease resurrection, promoted failed result, or evidence deletion. Preserve expired assignment, report candidate 4e6081d70f458dfdc223b9e772237ecb4626dbde, provider output and failure history. Native workspace is already independently closed; all 12 sandboxes absent. Exact authorization, version/idempotency, concurrent/partial-failure and denial coverage required. No new SDK run until recovery is resolved. Approval is limited to this recovery contract; strict golden requirements remain unverified.

e615 owning workspace closed; operator financial recovery required — 2026-10-08

Supported authoritative SDK treedx.workspaces.close invoked through original CLI OS-custodied client, exact project8cbfb810-6da5-4da2-9ae9-cad53101253f /workspace ws_CMeO7OXRPW4wxPS3o41bU8Vhosgw1_gw. Native before/operation/independent after readback CLOSED; repo repo_a3c347e2abcd09af, candidate4e6081d70f458dfdc223b9e772237ecb4626dbde, originalbasef3146757b664cfb74c6c376c12f3b7efa43b6ae4 and assignment branch retained unchanged. No abandon/deleted branch/published report/promoted expired result. /tmp/sdk515-e615-close-retained-workspace-20261008-summary.json SHA25630c8023cb5802f6541c025c937938f4db6b1dcb283c9acf2491efd40cd96a645; exact after68525d37710bc811a57e53e497a9b3074915a4653841bfb325a3a140a4c0ff7f. Previous12 Kata resources physically absent remains separate proof.

Human explicitly requires resolving operator recovery BEFORE another SDK run; quarantine-only retry rejected. All new SDK launches held. Existing provider settle operation is authenticated ownership-scoped and does not require active lease, but the retained native report measured only elapsed1; active clock never began. Zero active or guessed1 would not establish actual measured productive time. Do not fabricate usage, restore lease, edit DB or promote failed result. Native retained-authority diff against prior complete public inventory identifies only normal terminal finishedAt addition (/tmp/sdk515-e615-provider-authority-diff-20261008.json SHA256519afa76a416453620145f8dfd788ef699f88a728a120f5f39f221ea3c82f86d); ignoring it and blindly finalizing would delete unresolved custody, NOT resolve settlement. No such product repair made. Exact unresolved-usage operator release contract requires human architecture approval; requested explicitly before authoring/implementation. Existing assignment/report/failure/reservation/provider custody preserved. Current Agent375 corrected signing+native execution-start checks continue; local complete912/912 and required verify:local PASS, coded636+23 scenes still running. Cold native fullfile9/9 PASS separately. Full golden remains unpassed.

Live checked writeback applied; original cold-path regression verified — 2026-10-08

Human applied only checked Deployment cf3ff52324b6d71e8418f8c68848cce415d5f3fd deploy/capacity/writeback.conf (SHA256 016526834e530d260c9bfda8e410fc2d56ab37524426e0b111af33c33b9263dd) through original post-install sysctl load. Actual report /tmp/deployment834-live-writeback-20261008.json SHA256 4beeab5eb23a773c451f7a702e754a8fad8a78b53ced506ec3db25f993df5ac1: background bytes16777216 /dirty bytes67108864, both ratios0; unrelated expiry/writeback interval/swappiness/overcommit unchanged. No services/packages restarted/upgraded, no prewarm/cache flush/deadline/tag change.

Fresh root original COMPLETE tests/development-component-status-native.test.ts, original vitest.config.ts and five-second watchdog unchanged, 2026-10-08T20:27:39.775Z→20:27:50.164Z: 9/9 passed, zero failure/pending/todo; cold identity+denial+cleanup 437.184305ms; encrypted backup2197.105601ms. Exact Node24.12 command in /tmp/deployment834-writeback-cold-verification-20261008-custody.json SHA256 3d4eadf07d656da5883603d1591131be51d51d9dcba35c9e21eeb6d54f8ff90a; original report SHA256 1e9164510146daaa947605838b0fa5abbc6ee14426e03e1aa4154fd8f17c5735; log10f9f6e811b9af52398d8e7ead7123e17ed4c7f0fa59f5af4629c7c98dc29455. Exact clean staging source/index and dist inventory unchanged before/after, selected SDK manifest/lock/Vitest entry bytes held. Gitlinks are pin-only, not nested file closure. Earlier 5.982sec failure retained; this observation is not universal performance or independent causal proof. Focused regression NOT full-owner prerequisite, SDK golden, or permission to reuse old invocation receipts. Fresh ALL7 complete prerequisites and managed SDK retry remain required; old e615 Reporter financial custody remains unresolved, no fabricated settlement/PASS.

2026-10-08 native content execution-start regression and failed SDK closeout custody

Agent primary staging044d7caa12776e962cee18d3f6babf9749dcafe5 / temporary remote PR375 combines canonical ordinal repair plus native content execution start. Test-first3b1f301 preceded generic owning product044d7ca: commitTreeDx now opens the SAME memoized API execution window before granted writes, not role-specific runtime policy; original deadline/seconds/model/limits/schema unchanged.

SAME unit "runs the deterministic Reporter through the scoped TreeDX runtime without invoking a model" in tests/modern/kernel/provider-kernel-executor.test.ts (agent.golden.native-reporter-closure and agent.golden.reporter), plus SAME real native HTTP/Git "native renamed Reporter commits one canonical exact-workday Note without model dispatch and retains interrupted raw readback without a passing result" now intact in tests/modern/kernel/architecture/portable/reporting/reporter-integration.test.ts (agent.golden.execution-report-note-native). Existing component scene steps unchanged. Every original oracle retained; new exact-one execution admission before write and admission-denied ZERO request/write/commit/candidate/model assertions. Original500-line and10-direct-files limits retained; failed intermediate layout observations saved, intact move repaired them. No new harness/helper/policy.

RED complete original2files32total30pass2GENUINEfail0pending: /tmp/agent368-native-write-start-red-20261008.json SHA25626e6b1a5808f3d099f0520ccaf2f21b171f1c11cfc96b99dc915d5d6b8d8af01. Final focused COMPLETE4files provider-kernel-executor/context-integration/portable/reporting/reporter-integration/provider-runner54/54: /tmp/agent368-native-write-start-focused-r3-20261008.json SHA256f8e30989dd71b0333a594b259d1086bacf337b30480e3deeb46017ae51ffddf5. Fresh COMPLETE original suite on044d7ca912/9120fail/pending/todo: /tmp/agent368-native-write-start-full-20261008.json SHA256734c6b12af445be0c44f70c673a748b533ff18910ef5b3d45cd2264e8223ce32. Command originalNode24.12 / TREESEED_DEVELOPMENT_WORKSPACE_ROOT=/tmp/sdk369-platform-authority-de2LzF node node_modules/vitest/vitest.mjs run --config ./vitest.config.ts [named COMPLETE files for focused; no filters for full] --reporter=json --outputFile=; paired logs retained. npm run build:dist/typecheck/check:file-lengths and git diff --check finalPASS. Required Actions new exacthead37838778972 pending; prior head checks NOT this candidate proof. PR description template omission failed113518982066; fixed description only, validation nowPASS. App attachment failed100identitylimit, existing attachments retained. Native/component tests NOT managed SDK success.

Actual e615 retained provider closeout cause: /tmp/sdk515-e615-provider-retained-cause-20261008.json SHA25630d1a415a69cd4a72276d7a83a95ebf660b988c389e0ab22944cc754911abf6b. Reporter committed canonical report4e6081d70f458dfdc223b9e772237ecb4626dbde completed20:00:33.956Z with measured elapsed1, but activeStarted/Finished NULL; original API rejected closeout: "Closeout requires a started execution window and a positive closeout duration." It later EXPIRED/operator-action. No inferred zero charge or backfilled successful receipt.

Fresh privileged exact12sandbox check captured20:13:47.772Z ALL task/container/mount/directory ABSENT, /tmp/sdk515-e615-readonly-sandbox-closure-20261008.json SHA2569a9cc97dee0bfc66aec7db2a9871b027334ffcac99236fb455e695f67d98bf39. Supported exact13TreeDXreadbacks:12closed, Reporter workspacews_CMeO7OXRPW4wxPS3o41bU8Vhosgw1_gw remains COMMITTED notclosed; summarySHA256edf82a4bf351fe3f0332b144d48f94add5f64d1fb526e581fbb00ff78910ff35. Complete public usage/ledger pages(limit100/hasMorefalse): twelvefailed assignments eachoneaggregate/native ledger; expiredReporter onlydiagnostic usage/noaggregate. UsageSHA2563938938cfa558430f725f38d4a8dc660fdaf1ac44da015fdcf32e071c4d9675c; ledgerSHA25625284343a426e4a35aa6cfb0a066982178ef5c679ce0ec315fc0ac2c0a195859. Graph Reporter FAILED, reservation uncertainty correctly prevents workday terminal status; no claimed missing expired graph transition. Whole e615 remainsFAILED/closing, oldhistory retained.

Human authorized ONLY exact checked live writeback policy installation via same packaged post-install sysctl load; no tag/packageupgrade/service restart/prewarm/deadline increase. /tmp/deployment834-apply-checked-writeback.ts provided, application/result pending. Prior live settings0/0 and missing packagedfile are NOT repaired yet. FIVE-second whole cold path remains required. No SDK retry before fresh complete7-owner prerequisite/actualsafeclosure/selectedruntime custody. Full objective OPEN.

SDK e615efe0 failed on exact signed sandbox ordinal; repair is Agent-owned

Original native case exit1, criterion ACCEPTANCE_CAMPAIGN_ASSIGNMENT_FAILED, duration292402.758491ms; report /tmp/sdk-exploratory-campaign-e615efe0-20261008.json SHA df90ee96b24ce7d37747fcf9d64675d451a8a891072ea38d6e2670f82d76fcff. Workday workday-ccab7be4-93dd-4d72-9b65-18d9f86a66a1. Original stop invoked; no passing replay/clock refresh/second launch. Freeze SHA36273cf00a439cb23c48ff81faf1db503136b2944672b1672a2a88c867e3c84c, genuine proposalrevision1/nonemptydigest/0estimates and10 receipts retained.

Complete first assignment page19:58:20.707Z: FIVEactualFAILED, ZEROactive, each agent_kernel_failed / "Source authorization does not match the signed assignment.", five distinct native sandboxIDs and recorded teardownverified. Originalpublicfailureclassification terminal/retryablefalse, no model/native token activity. Rawprotected inventory /tmp/sdk515-e615-first-assignment-20261008-assignments.json SHAabe68ea977ebd98fbc093047fbaa856dc784d1288806910da6ec02033ca1716c. Subsequent complete settlement/resource/terminal readback remains required; publicverified is NOT independently proven physical absence.

Source cause: canonical AssignmentAttempt.attempt=1 and legacyattemptCount=1 in ALLfive realrows; original API source authorization uses SAMEcanonical attempt1. Agent signer instead calls activeSandboxAttempt(legacycount), adds1 and signs2. Deployment exact owner guard correctly rejects. Do NOT weaken Deployment guard or change API/architecture. Replace derived ordinal with original canonical Attempt, with focused unit/native Unix executor-signature/scene regressions FIRST; malformed authority must fail closed, old denial coverage preserved. Existing helper UNIT expectation +1 reflects obsolete counter derivation, not canonical authority; retain its history and all malformed-input negatives while retiring only that superseded product path.

Independent ALL7 trackedsource heads/bytes/index held unchanged and CLEAN through entire invocation20:00:58.079Z; before19:55:26.934. ActualmountedAPI1387 exactsource readback19:57:40.345 SHAaec4f6349f8c2f8303bcb6ae5a07e83e0d5787115671fd00ef1463190dfc1563. Prior exact-scope ambiguity repaired; this failure reached actual sandbox creation/source preparation boundary, NOT acceptedmodel execution/goldenPASS. No new timeout/cap/allowance/model/UI/branch/worktree/tag/automation changes. Continue tests-first earliest Agent fix, checked staging/main delivery, full fresh prerequisites before any next invocation.

SDK exploratory invocation e615efe0 — rebuilt exact-scope Agent admitted; original native case running

All seven fresh COMPLETE prerequisites passed before this invocation: Agent908, API1989, SDK560, Reviewer174, CLI357; complete native TreeDX original scripts exit0 (exploratory receipt-format exception only); Deployment1255 fresh Actions37824803566 attempt2 plus all176 original scenes independently audited. Exact commands/candidate/report hashes remain in preceding checkpoint. No old invocation receipt reuse.

ONE required supported Agent provider rebuild succeeded; generation632/sandbox424 READY, API949/runner815/TreeDX497 unchanged READY. Independent actual manager AND runner readback at2026-10-08T19:54:58.607Z compares EVERY113 selected dist entry/raw byte/executable mode to the fresh tested primary build; inventorySHA c624bb95ff63e258f0fa77ad983d0dc9084467861ff74dc59346574b289dcc28, actual runtimeBuild sha256:758e9832e891cece9e7901bd1b1462fcda286e10deba7d2cca17f542c2cac548, exact readonly/session-owned mounts, both actual containers started19:46:01Z. Original supported runtime status owns full private-copy alias/dependency custody; dist comparison is not independent whole dependency proof. Protected receipt /tmp/sdk515-agent-selected-byte-readback-20261008.json; supported status /tmp/sdk515-agent-supported-status-20261008.json.

All7 exact primary heads/index/raw tracked bytes CLEAN unchanged independently19:55:26.934Z: Agentabba4bc/API2de93c9/Deploymentcf3ff52/SDKf43bd78/CLIeac0c33/Reviewer1e3019f/TreeDX6d358bb. Gitlink pins not nested closure. Actual Agent374 main checks running, full verify-local PASS/scenes in progress; no merge/check bypass.

Original compiled Reviewer node-case.js now executes EXACT original Agent tests/acceptance/campaign.test.ts / "Frozen SDK campaign drives planning acting review and terminal golden gates". New operator /tmp/sdk-exploratory-next-20261008-e615efe0-operator.json and original draft -draft.json; freeze /tmp/sdk-exploratory-freeze-e615efe0-20261008.json; separate native report /tmp/sdk-exploratory-campaign-e615efe0-20261008.json/log. Campaign sdk-exploratory-20261008-e615efe0 / proposal golden-sdk-20261008-e615efe0. This is a NEW exploratory invocation with genuine fresh preparation, NOT strict same-proposal retry/reset compliance; prior ab0b failed observations/proposal/13 actual failed assignments/charges/closed workspaces retained. Fixed original SDK objective/topology/source/permissions and3600s/20minplanning/turn180 unchanged. No fake estimates/Decisions/charges/PASS, no old deadline refreshed. Existing exploratory missing-binding/native TreeDX format/research14400-cap exceptions remain explicit, strict golden NOTpassed.

Five-second ENTIRE cold Docker path contract remains unchanged. Checked disposable-installer repair already reached Deploymentmain; LIVE host tuning was NOT applied, not universal/live-host performance proof. No UI/new tags/local branches/worktrees/automation or model/allowance changes. Continue monitoring actual SDK, add unit+owning integration+original scenes before earliest-owner repair on any failure.

2026-10-08 — Agent checked staging delivery; ALL7 fresh prerequisites complete; required provider rebuild running

Agent373 original required Verify37831253597/job113496864160 PASS18m35s and submission validation PASS. Independent archive11573359647 /tmp/agent373-scenes-20261008.zip SHA8d07cc3d7f6eea5514b4fac49262891938b8f4c48d02338c47ed77bad7731a59 proves ALL632+23 exact original component scene steps, own fresh908/908 unfiltered prerequisite FIRST zero fail/skip/todo; exact identity/source digest/duration/exit0/no signal/process error/diagnostics. Report7cc198ec260d10bfe0b51bf99985c48f6ac8e9d20d7a471a51380b3883ddab66, 19:24:24.821Z→19:39:21.212Z. Ordinary staging mergeabba4bc12c13e90c1dbcfdcb6bb4303b2e9cce88 independently fetched parentsfefd0fbf1010b6b670359a251decfc01bf706926+c0d6341bf92880254cd212febe1f1ce5b2197098, exact tested tree06a0307ad2d2cfef2a636b9937583bbb719b73f0. Local staging fast-forwarded CLEAN. ONLY temporary remote codex/exact-repository-scope368 deleted after exact ancestry proof; commits recoverable in staging. Remote ONLY main/staging. No local feature branch/worktree/tag. MainPR374 full original template independently EXACT; Verify37834018751 running on main promotion, no bypass/merge yet. Attach attempt again hit thread100identity limit; no old attachments removed.

NEXT invocation FRESH original Agent full on actual merged abba908/908 zero fail/skip/todo, /tmp/sdk515-exact-scope-agent-full-20261008.json SHA62f587ec7804d89c6692e3c33ed0a7daa9b2b2a9f2eba9b47cba36bb7a40ece1, original build/config/Node24.12. NEW API native full1989/1989 on2de, exact127checkedinstalledTreeDXfiles unchanged, /tmp/api515-exact-scope-sdk-prerequisite-20261008.json SHA0228adad0a77fada28feba3d590fb84f3976b8e140df26b4280730151fec039e/log8d8004dae3c7e1940af3634eeccbbbd0a630496b86d0d01deabe358849ffc5bd. SDK560/CLI357/Reviewer174/TreeDXoriginal complete server+allSDKscripts fresh passes/hashes below are SAME current invocation, not prior campaign reuse.

Deployment exact-staging37824803566 attempt2 PASSALLthreejobs, new artifact11574895574 /tmp/sdk515-exact-scope-deployment-scenes-20261008.zip SHAc7f1e3be83495e5c616a7b3a5e76d788e5e0866ec3c673ed5b22a54e6cf0ace3. Independently audited176 exactsteps/actualexit0/no error/signal/digests, own fresh1255/1255 zero fail/skip/todo prerequisite FIRST19:36:05.497Z→19:37:06.450Z onexactcf3. Report24f34a0fbb5a8e819551bf45b3c1d522ec2fe4bd544b44c735570fa28d4e6f2d, completed19:41:17.548Z. Original entire5sec cold watchdog passed on disposable originalinstaller host; NOT livehost kernel tuning/performance proof. No old Deployment receipt reused.

ALL7 FRESH COMPLETE qualified before new native SDK invocation; primary staging source/index/gitlinkpin+bytes independently CLEAN at19:43:52.120Z and19:45:32.843Z. Agentabba sourceSHA6eba625afa4b977b5f7f0ff3907ab308bca1f1330bf5e73f3d77e7aba2455f0f; other six exactheads/source unchanged from19:31:36 snapshot below. Gitlinks notnesteddependencyclosure. Same originalconfigs/timeouts/concurrency. NativeTreeDX logs-only exception exploratory; strict179unboundcriteria/research14400vs7200 mismatch stay OPEN.

ONE actual-required supported dev rebuild agent.provider --session dev-5007e344-493 --json started via /tmp/sdk515-agent-exact-scope-staging-rebuild-20261008.ts on exactcheckedabba. New wx600 receipts pending; no readiness/source-to-selected-build/loaded-cache claim yet. This rebuild is necessary for the repaired provider-context path; no UI/manager/model/cap change or repeated arbitrary activation. Original SDK native case follows verified selectedruntimeadmission; ab0b failed invocation/13failedsettlements/history preserved, no passing replay/issued-clock refresh. Full objectiveOPEN; continue, do not stop at this evidence update.

Incidental metadata errors retained: Agent audit first lacked localCImergeobject, exact refs/pull/373/merge fetched then ONLY readonlyaudit rerun. Deployment audit first used guessed absent registry/scene paths; sourceinventory recovered original golden.verifiers.yaml +agent/golden scene, same audit/assertions passedr2. ghprview baseRefOid andget_pr_info repositoryargument were unsupported/wrongmetadata calls, no productRED; get_pr_info supportedschema used. gh requiredchecks initially no reported contexts while jobs initializing, originalworkflow visible/running, no bypass. Broad tmp searches producedpermission/truncation errors, not source or test failures.

2026-10-08 — API main promotion complete; fresh SDK retry prerequisites progressing

API PR521 required main Verify37823498218 and separate staging Verify37823246455 BOTH PASS. Ordinary main merge9f150534d3498da7c1e8c732bdaad97fb2c2bd89 independently fetched: parents89ee7b0b522a75e8c12a4296101cd8bdaf8b49f4 +2de93c9daa8529a40af7f681b669a1b75641abe9; tree4efde50b92ff5d22d787743908ce59c31077c129 exact checked source/CI tree. Local main fast-forwarded by ancestry; primary staging/HEAD remains clean2de, remote ONLY main/staging. No source change, squashed history, tag/release/deployment or prerequisite head change. New independent staging archive11574283179 SHA b1cefe9a03cfb00947e946aba8f74a357b688fdd50d82d4f82b3c24a4373792a audit proves ALL800 exact component steps, own fresh1989/1989 zero fail/skip/todo prerequisite FIRST, actual identities/untrimmed source digests/exit0/no error/no signal. Report f62b7fc17cf919ee6be2f4c9c2c3491670108e8370a03951baa2cd348e5009d7, actions-37823246455-1 18:39:15.855Z→19:34:35.970Z. Component delivery NOT SDK golden PASS.

Next SDK invocation FRESH original SDK560/560 (report15327011052fc1a080c650c3f23743760b607e7d4581251413a52cc62d50bf4c), Reviewer174/174 (1680c19237fda09a5a0fb1cbd0c61eb0ff2e789ea77798d2a6202a6c164e4beb), CLI357/357 zero fail/cancel/skip/todo (TAPf6bb17e90b76ff2d9f0f39904413601f057ba88c368b4a870bf71e4c4ddaa16d), and original complete nativeTreeDX server/allSDK scripts exit0 (log4d45cdc486909ad6a2a0e3409037d685cef621256ef77f20c10501b2c4cfbf2f) complete. All paths /tmp/sdk515-exact-scope-{owner}-full-20261008.*; same original build/scripts/config/concurrency/limits and fixed primary staging sources. TreeDX native logs exception exploratory-only. New API full prerequisite8687 still running, fresh Deployment37824803566 attempt2 has passed complete verification and is executing coded scenes. Agent373 original632+23 component steps still running; new Agent exact final-head prerequisite must follow checked staging merge. No native SDK newworkday yet, no reuse of prior failed-run receipts.

2026-10-08 — fresh prerequisites for repaired exact-scope SDK retry

The prior ab0b5d31 SDK invocation remains FAILED; no old passing receipt reused. Next invocation has started FRESH original SDK560/560 zero fail/pending/todo (Node24.12, original full vitest.contracts.config.ts after build:dist + standards:build), /tmp/sdk515-exact-scope-sdk-full-20261008.json. Original complete API native PG/TreeDX, CLI recursive native runner, Reviewer whole Vitest and TreeDX test-all.sh + test-sdk-packages.sh now running under unchanged configs/watchdogs. No new model/workday launch yet. Six unchanged owner staging candidates held; Agent c0d repair awaits checked staging merge before its new exact-commit full prerequisite. Existing all7 byte custody at19:31:36.006Z is a before-merge observation, NOT all7 final candidate receipt.

A deliberate FRESH Deployment complete original workflow run37824803566 attempt2 on exact stagingcf3ff52324b6d71e8418f8c68848cce415d5f3fd started19:31:51Z via unsupported-connector full-rerun CLI fallback. This is required fresh native prerequisite evidence for the NEW SDK invocation, not blind failed retry or prior receipt reuse; original installer/native suite/scenes/teardown unchanged. No live host privileged runner or local sudo/timeout/kernel mutation.

Agent373 complete Verify passed its whole verification and is still executing coded component scenes. API521 main800-scene audit passes; separate required staging Verify37823246455 still pending. No check bypass or merge while pending. SDKfull was run before other heavy local suites to avoid prior contention; no deadline/allowance/concurrency extension. Incidental diagnostics retained: broad tmp/ps/PR-diff display truncations/read permission errors are NOT product RED; gh run view unsupported attempt field corrected through read-only gh api. Required command/report/hash final map follows after completion. Objective OPEN; continue delivery, provider rebuild and original SDK case.

2026-10-08 — exact-scope Agent whole-suite PASS and PR373; SDK failure retained

Agent committed candidate c0d6341bf92880254cd212febe1f1ce5b2197098: fresh COMPLETE original unit/integration suite908/908,0failed/skipped/todo; /tmp/agent368-exact-repository-scope-full-r2-20261008.json SHA256 b33105055c09acbd1469828e02749fcc93481157f0e68c86870fe14ce95d6fad. Same original unfiltered config/Node24.12/authority path; source/build/strict typecheck/original length+ownership/diff checks PASS. Earlier908/907/1 fixture mismatch and both genuine REDs remain retained below. No native model/managed acceptance PASS from these totals.

PR treeseed-ai/agent#373 opened from ONLY temporary remote codex/exact-repository-scope368 into protected staging fefd0fbf1010b6b670359a251decfc01bf706926; exacthead c0d6341, currentCImerge9373a6e7e3c9d379b137eb12840660ed93b246d8. Original required Verify37831253597/job113496864160 running; submission validation PASS. Full original PR body independently exact; attachment tool attempted but current thread100identity limit rejects it; existing attachments were NOT removed. Local staging CLEAN/ahead4, no feature branch/worktree/tag, no branch cleanup claimed yet. Merge/main promotion/new SDK launch require original checks and fresh exact-owner prerequisites, not old passing receipts.

Correction to earlier shorthand: “5546301b” was a transcription error, not a Git ref or tested candidate. Independently resolved actual first tests-first commit5546301012b00966b8b07d06743c95db73010ed3; secondf6e41105ca1ae435a87fd3e722e492291b976741; third7deacf1b28833b6a472183f402c546ea007be998; owningrepairc0d6341bf92880254cd212febe1f1ce5b2197098. All ordinary lineage preserved.

API main PR521 Verify37823498218/job113470255613 PASS; its NEW scene ZIP11573386267 independently digest-matched6bc22011cab0b08bcd53fa0acb0ee062f392931fb4c6330421d1821abe124b55. Read-only artifact audit ALL800 selected original scene/ref/test identities/untrimmed candidate source hashes/exit0/nosignal/noerror/native duration and ownfresh1989/1989 unfiltered prerequisite receipt PASS on CImergec47e6c85ba38d6ed23d03ac2558d27091e94fa1c, whose tree exactlyequals heldstaging2de93c9daa8529a40af7f681b669a1b75641abe9. ReportSHA256c9c35adda0040c377b760248567c079dc39d470149f163bb51cb76b43f7c1add; runactions-37823498218-1,18:34:53.797Z→19:14:25.525Z. Scope local-component-tests NOT SDKgolden. Required staging-push Verify37823246455/job113469400737 still pending; no merge bypass. Initial read-only large artifact display truncated; recovered exact required receipt fields and full independent audit succeeded. gh pr checks --json unsupported on installedCLI, corrected supported plain required check; no failed workflow rerun/waiver. PriorAPI whole-test strict254-line gap remains unwaived.

2026-10-08 — Agent exact-scope repair committed; failed SDK closed publicly, no passing replay

Local staging tests-first5546301b→f6e4110→test-only7deacf1b, earliest owning repair c0d6341bf92880254cd212febe1f1ce5b2197098 (parent7deacf1b28833b6a472183f402c546ea007be998/tree06a0307ad2d2cfef2a636b9937583bbb719b73f0). No new local branch/worktree/tag. Remote staging basefefd0fbf1010b6b670359a251decfc01bf706926 still independently held. Repair modifies ONLY original Agent materialize-context.ts and microvm-executor.ts: select existing immutable repository grants by exact commit/path/model for context and exact commit/path for file tools; retain primary current base, duplicate/foreign selector denial and frozen inputs. SDK assignmentPathAllowed reused. No new authority/schema/storage/service/config/model/clock/deadline/allowance/UI change. Genuine SDK failed inventory showed independently pinned objective/proposal/discussion rows in one repository; this is routing correction, not architecture change.

Additional ORIGINAL case maps (same cross-project files and original component scene, step IDs omit agent.golden):

agent.golden.exact-repository-tool-scope-unit / “routes explicit exact file tools and the primary current view across independently pinned repository scopes”.
agent.golden.exact-repository-tool-scope-native / “official native file tools select the exact pinned primary or explicit project scope without collapsing repository grants”.
agent.golden.exact-repository-tool-denial-unit / “denies unmatched pinned file-tool commits and paths before invocation without primary fallback”.
agent.golden.exact-repository-tool-denial-native / “unmatched pinned file-tool scope denies before official HTTP while native source and authority remain unchanged”.
Together with prior4 maps,8 added cases. Existing original duplicate/foreign/missing/denied/transport/input-custody tests retained. Original managed campaign already rejects any returned assignment; no new campaign/runner/policy. Component scene bindings NOT yet executed/managed golden proof.

Second genuine focused RED13/11passed/2failed at current repository ambiguity, /tmp/agent368-exact-repository-tool-scope-red-20261008.json SHA256 a7bf95a4e1b8e643864f7a08a9547124b4851a4f88305bebab2378c1d3a3694d, same original two-file command. After earliest correction complete four focused files30/30 /tmp/agent368-exact-repository-scope-r2-20261008.json SHA2567be72a730b344e7f5f149523d3ba35087b86e2145c4063d8969cd9d933715a0e. Original full suite908/907pass/1fail retained /tmp/agent368-exact-repository-scope-full-20261008.json SHA256606cbfd8cf07c91d1cddf33438363db82a3e38f3e0486cc4ab6e720f2f33e234: old Codex predecessor fixture granted literal commit-2 but requested unrelated exact SHA. API providerRefAuthority source independently confirms missing pinned-ref authority must deny. SAME old positive assertions and unknown-repository negative retained; fixture baseRef now exact requested predecessor, extra changed-commit denial and no invoke mutation asserted. Not an observed product defect or removed test. Corrected complete three focused files29/29; strict original typecheck/build/layout/diff pass. Fresh whole908 suite on COMMITTED c0d candidate RUNNING, not a passing prerequisite or launch permission yet. No test timer/config/filter/assertion weakening. New malformed/scope observations retained.

Independent failed SDK closure: actual workday public run status failed; complete13 assignments failed/0active; each original TreeDX workspace public show independently CLOSED with exact workspace/repository/project identity. /tmp/sdk515-ab0b5d31-retained-treedx-summary-20261008.json SHA25644239f2d582479df45084fb4b8407b542605e7de4b40d6c2f18eec4878a1de29. Complete usage26 (13aggregate+13diagnostic-0), ledger13 distinct settlements with exact assignment/reservation/workday joins, all activeSeconds0 and elapsedSeconds1 on aggregates/ledgers, empty nativeUsage. Usage SHA256977ca010246a6cc8575d92f0d484b39467210a46b3d0ea16166a365cb3f75649; ledger SHA25690154729a67b833f001f769f4db6c0cee66b97dd19c9e95e467507b522bd4022. These are actual failed infrastructure observations, NOT generated model tokens, successful results or physical resource absence. No sandbox ID is present; do not reuse old four-sandbox closure receipt for this run. Earlier failed cases/charges retained without backfill or relabel.

2026-10-08 — resumed SDK failed at exact repository context resolution; focused RED retained

Fresh all-seven prerequisites preceded original SDK case “Frozen SDK campaign drives planning acting review and terminal golden gates” on campaign sdk-exploratory-20261008-ab0b5d31 / workday-74c00400-d45d-4b11-a248-aba40c3d815e. Actual native report /tmp/sdk-exploratory-campaign-ab0b5d31-20261008.json SHA256 2289c6ab420c5a3abbe4e3c0e88b6cd2784f8d70a30d9c70ca485ca779bbe0d7: 0 passed / 1 failed, ERR_TEST_FAILURE criterion ACCEPTANCE_CAMPAIGN_ASSIGNMENT_RETURNED, duration280402.6883ms; stderr empty. NOT golden PASS or timeout. Original public stop ran; fresh complete assignment inventory captured19:06:53.204Z:13 failed,0 active. Protected /tmp/sdk515-ab0b5d31-returned-run-scoped-20261008-assignments.json SHA256 d85cc52524878f717df51104b58fbfabebc5afe10caf31d8173d263c505be7f9 retains every lastReturn: agent_executor_failed / assignment_context_read_failed / assignment_context_repository_ambiguous for project objective and discussion context. Public revoked handles/teardown metadata are NOT physical closure or settlement proof; those remain open. No blind relaunch.

Owning Agent materialize-context.ts projectFor selects repositoryId only; native public handle has multiple legitimate rows for ONE repository at independent original context/proposal/discussion commits. Exact commit/path/model scope must select the owning route, never merge grants, use row order, broaden to primary, or manufacture context. Existing duplicate/foreign project denials retained. No architecture change, UI, timer/allowance increase or new schema/service.

Tests-first authored four cases in ORIGINAL cross-project-authority.test.ts + cross-project-native.test.ts, existing golden.verifiers.yaml/component-boundaries.scene.yaml bindings:

agent.golden.exact-repository-scope-unit: “resolves independently pinned reads from one repository by exact commit path and model rather than repository row count”.
agent.golden.exact-repository-scope-denial-unit: “denies absent exact commit path or model scope even for the primary repository without falling back or changing grants”.
agent.golden.exact-repository-scope-native: “owning Kernel consumes exact scoped context when one repository has independently pinned grants without merging authority”.
agent.golden.exact-repository-scope-denial-native: “owning Kernel refuses unmatched primary exact read scopes before native HTTP or execution and retains candidate bytes”.
Each step uses same ID without agent.golden prefix. Component scenes declarative NOT executed/managed SDK proof. Native original Kernel/official SDK/native HTTP/Git uses controlled grant/content/executor inputs, NOT actual production authority/model/charges/Kata.

Exact focused command in Agent, pinned Node24.12: node node_modules/vitest/vitest.mjs run --config ./vitest.config.ts tests/modern/kernel/architecture/portable/cross-project-authority.test.ts tests/modern/kernel/architecture/portable/cross-project-native.test.ts --reporter=json --outputFile=/tmp/agent368-exact-repository-scope-red-20261008.json (log same basename). Complete BOTH original files:11 total/7 passed/4 failed; report SHA256 fe82e6f6974fb4e3d1a46fb79ac2a37cbe843c4e7871ef154296a7dcd228e443. New positives fail ambiguity; UNIT unmatched scope incorrectly admits; native unmatched scope proceeds through HTTP/executor and fails later with Unexpected end of JSON input—not the required local scope denial. This consequence is retained, not relabelled native authorization success. Earlier assertions unchanged. Source-only readonly facade construction correction preceded execution; no compiler failure. Product unchanged at RED. Agent staging/origin independently fefd0fbf1010b6b670359a251decfc01bf706926; main1dbc7a72677d794b873f6ec6435f7dc2689a4be7. No new local branch/worktree/tag. Native SDK failure retained; strict golden and semantic closure remain OPEN.

Original exploratory SDK case started on fresh ALL7 candidates — 2026-10-08 18:54 UTC

All7 fresh complete original prerequisites passed before native invocation, exact held primary staging heads/source unchanged18:31:30.206Z→18:51:42.487Z. API1989/Agent900/SDK560/CLI357/Reviewer174/Deployment1255 and original complete nativeTreeDX server+allSDKscripts; exact maps/hashes below. No prior passing campaign receipt reused. Native TreeDX log exception only exploratory; strict179unboundcriteria and research14400/7200 mismatch unverified.

ONE supported API lifecycle rebuild succeeds exit0/oktrue: receipt /tmp/sdk515-api-lifecycle-staging-rebuild-20261008.json SHA7214e7672437f0fb748d26275198e4485907014a6a2f9eaa0f9ba44ce1969b8f. ActualAPI949/runner815/TreeDX497 ready; unchangedAgentprovider630/sandbox424 ready, originalmanualagent.provider reaction NOTperformed. ActualAPIcontainerstarted18:45:31.954767629Z after tested repair. Independent actualmounted1387index+byte inventory SHAaec4f6349f8c2f8303bcb6ae5a07e83e0d5787115671fd00ef1463190dfc1563 equals tested2de source; receipt /tmp/sdk515-api-lifecycle-mounted-readback-20261008.json. Gitlinkpins notnestedclosure, mountedliveTSentrypoint notdist/private-copyclaim. ALL127actualinstalledTreeDXclientfiles independently exact vscheckedarchive after rebuild, /tmp/sdk515-api-lifecycle-selected-treedx-readback-20261008.json. SelectedCLIentrybundle independently equals freshcheckedCLIentry. No livekernelwritebacksettings changed, unrelatedUIrebuild/modelchange or extraactivation.

NEWcampaign sdk-exploratory-20261008-ab0b5d31 /prospectiveSDKproposal golden-sdk-20261008-ab0b5d31. Operator manifest /tmp/sdk-exploratory-next-20261008-ab0b5d31-operator.json SHA3fd0bcee1616f5f211b1c2711eef08699ddb32181cb235c99455509f16453a40 independently validated25prospectiveinputs fromexactoriginaldocs/seed, currentnativepolicy/supplyread; startsAt18:52:46.277Z/duration3600/planning100/3/turn180. Fixedrequest/objectives/topology/criteria remain original; no easierproposal, fakeestimate/authority/usage/receipt. Newordinarydraft /tmp/sdk-exploratory-next-20261008-ab0b5d31-draft.json withheldSDKf43source. No originalfailedfreeze/observation overwritten or oldfailedrunrelabeled. FutureSDKfreeze /tmp/sdk-exploratory-freeze-ab0b5d31-20261008.json createdONLYinsideoriginalnativecallbackafteractualBookread/proposalopen/preflight.

Original Reviewer compiled node-case.js invokes /home/adrian/Projects/platform/packages/agent/tests/acceptance/campaign.test.ts exactcase “Frozen SDK campaign drives planning acting review and terminal golden gates”, session9379, started18:54:05UTC. Alloriginalharness/runtime/gates retained. Environment originalTREESEED_ACCEPTANCE_{PLATFORM_PATH,CAMPAIGN_PATH,DRAFT_PATH,FREEZE_PATH,TEAM}, pinnedNode24.12/PATH/currentCLIandlocalhostCA. Protectednew report /tmp/sdk-exploratory-campaign-ab0b5d31-20261008.json and .err. Callbackpreparation/admissionstillrunning, no model/workday/golden success claimed yet. Continue actualnativecase and cheap regressions onanyfailure. MainAPI521requiredcomponentcasescontinue separately, checkedDeploymentmain9b7alreadycomplete. No newbranch/worktree/tag/scheduledautomation.

Fresh ALL7 prerequisites complete; supported API lifecycle rebuild in progress — 2026-10-08

NEW exact-staging API2de93c9daa8529a40af7f681b669a1b75641abe9 original strictbuild +COMPLETE unfiltered original vitest.control-plane.config.ts passes1989/1989, zero fail/pending/todo. Exact127checkedinstalledTreeDXclientfiles held before/after; native disposablePG/TreeDX used, no credentials exposed. Report /tmp/api515-cold-repaired-sdk-prerequisite-20261008.json SHAc916f1bc1bd0d4424a3064eae11206539f6bab9901f372a9a5ea66350c43a50d; loga6469497892bd39cf2823dc16982b99d5f53c36d62237486faa8dd407c5da5b4. Command pinnedNode24.12 /tmp/api515-cold-repaired-sdk-prerequisite-20261008.ts, which invokes original npm run build:dist then original full Vitest with reporter/json path only. No filtering/timeout/config/concurrency change.

ALL7 FRESH COMPLETE before the next native SDK case: SDK560/Agent900/CLI357/Reviewer174/API1989, exact-stagingDeployment1255/1255 receipt after18:31custody, originalTreeDX complete server+alllanguageSDKscripts under human exploratory native-log exception. Exact command/report/log/artifact maps and hashes recorded below; no previous campaign passing receipt reuse. All7 primary staging HEADs/indexed byte inventories independently CLEAN/identical18:31:30.206Z→18:45:29.353Z. Gitlink metadata is not nested closure. Native strictgolden179unboundrequirements/research14400vs7200 mismatch remain OPEN, not passed.

ONE actual-required supported dev rebuild api.service --session dev-5007e344-493 --json now running through original CLI on exactchecked2de, script /tmp/sdk515-api-lifecycle-staging-rebuild-20261008.ts. New wx600 outputs /tmp/sdk515-api-lifecycle-staging-rebuild-20261008.json/.err preserve earlierc9rebuild unchanged. No readiness/candidate/loaded-cache success claim until native readback. Changed API implementation necessitates this rebuild; no unrelated UI/provider/model/manager activation, hostwritebacksettings remain untouched. After actual runtime readback, original native prepareSdkCampaign/campaign.test.ts will drive one NEW exploratory simulation with exactfixedSDKrequest; no easierproposal/changeddeadline/fabricatedapproval/citations/usage/Book/modelprobe. No campaign yet.

Checked host repair delivered to staging — 2026-10-08

Deployment PR845 merged normally as cf3ff52324b6d71e8418f8c68848cce415d5f3fd (parents825ba3c43b91525f984f287385761f96208add75 +2f283116f3211b41fbda583425ad0335425b1555). Exact tree844b0bfddf2cf666d69b4c344d31b30891a2c380 equals tested head and CI merge6b4619963746984fb95eaa7b84db12ebd6b4864b. Primary LOCAL staging clean; temporary remote codex/cold-writeback834 removed after exact-head ancestry proof. Remote only main/staging/gh-pages; no local branch/worktree/tag. Main promotion PR846 awaits fresh required checks.

Current Verify37823188166/job113469198970 PASS: fresh installed disposable capacity host, original complete190files/1255tests, strict build/source-shape505, package verification/sealing; secret-custody and uninstall-vm PASS. Original whole cold5sec watchdog unchanged and passing. Own fresh COMPLETE1255/1255 zero fail/skip/todo prerequisites preceded all176 original component verifiers. Independent exact untrimmed source/test/name/digest/duration/exit/noerror audit succeeded. Artifact11570328141 ZIP /tmp/deployment845-scenes-20261008.zip SHA25613b0a89d86aaa7a20c7459580a7f0120010b590eff7644ba0a07d8bdd6b271a7; report363907a0a02d06e6e3377af4c21c5b60f15ceb1d1cd02729dda34bd4aaaeb860; run actions-37823188166-1 18:22:04.049Z→18:26:13.754Z. Scope local-component-tests NOT SDK golden. Later isolated Docker scene274.036811ms is warm, not claimed first cold duration. Prior6651/5982ms failures remain retained. Initial read-only audit incorrectly expected API explicit config flag; corrected to Deployment original default config and exact unfiltered command, not a product/test failure.

Test-first213321d3 and installer repair2f283116 retained. One manager-owned persistent writeback asset background16MiB/writer64MiB applied ONLY via existing disposable host installer; native actual installed/procfs readback passes. Live host not changed. No prewarm/sync/cache-drop/storage/snapshotter/API/schema/architecture/UI/timeout/allowance change; initial tuning is not a universal speed guarantee.

API lifecycle checked staging2de93c9daa8529a40af7f681b669a1b75641abe9 and independent800 component/1989 prerequisite audit complete, PR521 main checks running. ALL7 primary sources independently CLEAN/held at18:31:30.206Z. Fresh SDK full prerequisites started on unchangedf43bd785 after original build/standards, no new Book/proposal/model/campaign. New SDK acceptance requires all participating owners' fresh complete suites; no previous campaign receipt reuse. Four recorded old sandboxes independently physically absent, historical/unobserved gaps retained. SDK exploratory and strict golden OPEN;179 unbound criteria and research14400/7200 mismatch remain unverified.

Canonical lifecycle delivered to checked staging — 2026-10-08

PR520 #520 MERGED ordinary merge2de93c9daa8529a40af7f681b669a1b75641abe9. Independently fetched exact parents c9eb1bb +2cfbbf65fe3819b18842790bb66f16137836b2eb, source tree4efde50b92ff5d22d787743908ce59c31077c129 equals tested head and CImerge231cf65689bfffd805a8fc19c1573ce47a4f77df. Clean local staging fast-forwarded, no new local branch/worktree. Temporary remote codex/canonical-attempt-lifecycle515 deleted ONLY after exact2cf ancestry proof; independent ls-remote shows absent and preserves staging/main. Main remains89ee7b0b522a75e8c12a4296101cd8bdaf8b49f4; fresh checked staging→main PR521 #521 OPEN, required Actions pending, no bypass/tag/release.

Required Verify37811999539/job113430952710 PASS, plus current authenticated-committer and submission checks. Native TreeDX server/all-language clients, whole direct API suite, all three real PostgreSQL groups, pack, coded component scene and native close all PASS. Independent CURRENT artifact audit: ZIP /tmp/api520-scenes-20261008.zip SHA2568f0e4e8c5a7ba2e8b3dfebcdd70dd329ffb94f7ac62e38d0b2d70a2af5d5dbb4; report512f172ff493b07ed20b81782fa20d59df4541300b4976d9a1d572eedc9b6729; all800 original selected refs/test identities/untrimmed source SHA256/real nonnegative durations/exit0/no signal or process error independently verified against held2cf bytes. Own fresh complete unfiltered1989/1989 prerequisite receipt on CImerge231, zero fail/skip/todo, scene actions-37811999539-1 started17:13:37.783Z/completed18:16:02.435Z. Scope local-component-tests, NOT managed SDK/golden/all-attempt charges/whole physical closure. No old receipt reused for this audit.

Supplemental whole-test strict failure remains254lines outside changed files, baseline unestablished/not waived. Previous SDK failed canonical rows retained, no backfill. Four recorded old sandboxes physically absent per retained independent root report; earlier unrecorded-attempt provenance remains open. Deployment diagnostic native run37821928237 FAILED1253/1252/1 at unchanged5sec, Docker6651ms with Dirty761524KiB→4272KiB. Newly committed Deployment2f283116 proposes manager-owned16MiB/64MiB writeback tuning; fresh native Verify37823188166 pending, no performance/golden success claimed. No new SDK campaign/model/activation. Full acceptance objective OPEN.

2026-10-08 — retained sandbox physical closure independently verified

Human ran the original read-only privileged script /tmp/sdk515-readonly-sandbox-closure.ts. Independent report readback /tmp/sdk515-readonly-sandbox-closure-20261008.json SHA256 383050386bf450b7778d230ef0ceb3a0d0ec0ad9c3389212f95a108403b64339, capturedAt 2026-10-08T17:42:56.476Z. All FOUR recorded sandbox IDs and assignment IDs exactly match /tmp/sdk515-retained-run-scoped-20261008-assignments.json. For each, actual owning containerd task/container inventory, host mountinfo and allocated state-directory inspection report taskAbsent/containerAbsent/mountsAbsent/directoryAbsent=true. Script stopped/deleted/reconciled nothing; failed run, history and inputs retained. This closes physical absence for these four recorded sandboxes ONLY, not unobserved earlier attempts or a new managed run. SDK exploratory/golden still incomplete: Deployment cold five-second native failure remains FAILED; API PR520 current required component scenes remain running, fresh local full API1989/1989 and all prior failed evidence remain intact. No new campaign, timeout/allowance change, tag, architecture or UI change.

2026-10-08 — corrected fresh COMPLETE API suite PASS1989; prior checked repair merged to main

Current lifecycle candidate remains CLEAN LOCAL staging 2cfbbf6 (tree4efde50b92ff5d22d787743908ce59c31077c129/sourceSHA256aec4f6349f8c2f8303bcb6ae5a07e83e0d5787115671fd00ef1463190dfc1563). Fresh COMPLETE original suite PASSES1989/1989, zero fail/pending/todo, exact127checkednativeclientfiles before/after:
PATH=/tmp/sdk-native-node2412-PjB5qe/bin:$PATH node /tmp/api515-canonical-lifecycle-complete-r2.ts
Original strict npm run build:dist + unfiltered Vitest original config/timeouts/concurrency, original disposable native PostgreSQL/TreeDX.
/tmp/api515-canonical-lifecycle-complete-r2-20261008.json SHA256 c9117fccdf34c5c631f6b1992b4d0997997f66b5d46ba8d6c3ccd7976f9dc7c5;
/tmp/api515-canonical-lifecycle-complete-r2-20261008.log SHA256 684e862baf761a513cd028f1d062bea6349eb75961e34bfcf1853792a741ac07.
All seven participating owner HEAD/tree/tracked-source inventories independently identical from16:50:58.767Z through17:02:57.407Z. Other six owners unchanged; no old receipt reuse for this corrected candidate. All earlier genuine RED, full1989/1985/4 failure, stale-oracle23/19/4 and introduced-oracle23/20/3 observations remain intact, not retroactively passed.

PR520 is now ready on exact current2cf head and staging c9eb1bb base. Exact final evidence independently written/read back in its original template; provider-authenticated author remainsadrianwebb. Required Verify37811999539/job113430952710 is still running original verify:direct; NEW800component scene bindings not yet passing. No staging merge/remote branch deletion for this new lifecycle repair until required checks pass. Supplemental whole strict-test failures outside changed files remain unwaived; introducedTS2339 corrected by safe narrowing; corrected supplemental log exactly equals earlier b804 failing log. No “all strict tests pass” or golden claim.

SEPARATE prior repair delivery completed: PR519, stagingc9→main04392551dc97f0cead9099dcde1387f4240bedb0, required Verify37802154331/job113396858404 SUCCESS including native TreeDXserver/alllanguageSDK, verify:direct, all3PostgreSQLgroups, pack, components, allocated fixture cleanup. All required verify and authorization/validate checks confirmed success (promotion skipped is NOT a test). Independent main protection readback retains strict required verify and0humanreview approvals perprelaunchpolicy. No protection change/bypass.

Independent Actions scene ZIP11566605398 /tmp/api519-scenes-20261008.zip SHA2567c668d3998dac27c2a989a1993a200cff47bcd01d9675179ad179d57b7f31f29; reportSHA256eca14a89768e2da832f4215fad9047018d9117183a6aa06c0ec3ff949b691421. Exact793verifier/test names/source digests/onecheckeach independently audited against c9; actual fresh complete1982/1982 prerequisite receipt at CImerge57be5bdf175a98afcf2c19fa77782835a065dfa3, zero failure/skip/todo, original unfilteredcommand. Scene15:58:47.934Z–17:00:52.834Z, scope local-component-tests NOTmanagedgolden. TestedCImerge tree74e79e41be621f816d68100ea4f29ce435464aac equals c9.

Ordinary main merge89ee7b0b522a75e8c12a4296101cd8bdaf8b49f4 independently fetched: parents exact oldmain04392551+c9; tree74e79e41be621f816d68100ea4f29ce435464aac identical testedCImerge/c9; full Git diff empty and c9 ancestry retained. Existing localmain fast-forwarded with exact compare-and-set after ancestry/worktree checks; primary checkout stays LOCALstaging2cf clean. Existing detached historical worktrees were only inventoried, not created/removed/touched. Old PR branch is staging itself and MUST NOT be deleted; one active temporary remote lifecycle branch remains until checked merge.

CLI fallback incidents disclosed: connected status returns no check-runs; installed gh pr checks --json rejects unsupported flag (read-only error, not CI failure), so authenticated gh api check-runs provided exact actual success results. Connected artifact download returns cloud ZIP ref, no local bytes; authenticated gh api binary retrieval used explicit fresh path, no source edits. No credential values/unsafe Issue shell prose. Supported ordinary merge+independent exact readback; no tags/releases/manual reruns/UI/new localbranch/worktree.

SDK exploratory/golden still OPEN, not launched. New lifecycle Actions pending; Deployment cold five-second native prerequisite FAIL and privileged physical sandbox report absent. No fake closure/usage, new Book/proposal/model/campaign, allowance/deadline/schema/config/architecture change. API-only exploratory history-merge exception does not waive other owners or changed bytes.

ENTIRE preceding Issue body preserved unchanged below.

2026-10-08 — four original boundary oracles now PASS; fresh complete corrected candidate running

Current CLEAN LOCAL staging and PR520 remote head 2cfbbf6; tree 4efde50b92ff5d22d787743908ce59c31077c129; source SHA256 aec4f6349f8c2f8303bcb6ae5a07e83e0d5787115671fd00ef1463190dfc1563 (1387 indexed entries; gitlinks pin-only). No new local branch/worktree/tag. Original implementation b804 remains unchanged; ordinary test-only corrections 56e1e77, 59f140c and typed narrowing 2cfbbf6 follow it, preserving all history.

Retained 56e1e7 focused retry FAILED 23/20/3, zero pending/todo: /tmp/api515-canonical-lifecycle-four-focus-r2-20261008.json SHA256 845cfb14a8cdb0b4c37948844e1c3e815ef4fa12836d354cd2c3091be863f7a8. Two later whole-custody checks also expected created after native claim. My added stop-clock assertion incorrectly treated an ALREADY SEEDED earlier closingAt as the current stop clock. It is an introduced ORACLE failure, NOT product RED, clock-widening authority, or a passing retry. Earlier phrase “finishedAt equals first published closingAt” is superseded: the existing phase closingAt remains unchanged; the actual original native root failed_at finish clock is independently read and bracketed by this public call/return, then the FULL canonical raw snapshot must agree exactly and retain those SAME bytes on replay.

All four COMPLETE original files then PASS 23/23, zero failure/pending/todo on 59f140c:
PATH=/tmp/sdk-native-node2412-PjB5qe/bin:$PATH node /tmp/api515-canonical-four-focus-r3.ts
/tmp/api515-canonical-lifecycle-four-focus-r3-20261008.json SHA256 5946dc638d68499cd24f3219425d3441d46e72b161a568c5950a9cacff9fc0b4.
These focused results do NOT satisfy whole-owner prerequisites or prove managed golden.

Supplemental strict check independently exposed introduced TS2339 on the new credential assertion (public operation output is unknown). Retained /tmp/api515-canonical-lifecycle-oracle-strict-20261008.log SHA256 e2cb2a2d13ef56fd5490bf6627b0ceeaeac8d7f11719844701432e60253701fb. 2cfbbf6 adds explicit object/member narrowing before EXACT full canonical equality; no cast, mock field or disabled check. Corrected supplemental log /tmp/api515-canonical-lifecycle-oracle-strict-r2-20261008.log is BYTE-IDENTICAL to the original b804 failing supplemental log, SHA256 a363bc1cce1f146e312750d327da40a11c43f32adde771713d217fc43b1c837e. Introduced typing diagnostic is gone; remaining 254 lines outside changed files are still FAIL/unwaived. No pre-lifecycle baseline or whole strict-test PASS claim. Original layout retry PASS /tmp/api515-canonical-lifecycle-oracle-layout-20261008.log SHA256 fbacdb40e05886248ba25f8dd07cbbcc13f56a62c46de1ec310762c967038810.

Fresh COMPLETE original API suite started 2026-10-08T16:50:58Z on exact final 2cfbbf6:
PATH=/tmp/sdk-native-node2412-PjB5qe/bin:$PATH node /tmp/api515-canonical-lifecycle-complete-r2.ts
Original npm run build:dist then unfiltered node node_modules/vitest/vitest.mjs run --config ./vitest.control-plane.config.ts --reporter=json --outputFile=/tmp/api515-canonical-lifecycle-complete-r2-20261008.json.
Separate log /tmp/api515-canonical-lifecycle-complete-r2-20261008.log; actual original disposable PostgreSQL/TreeDX, original limits/concurrency/watchdogs, all 127 exact client files, all seven owner heads/trees/tracked bytes held. NO full retry result yet. Required fresh Verify37811999539 is running on current PR head; PR remains Draft. Earlier b804 full 1989/1985/4 failed and all focused RED/oracle reports remain unchanged.

Seven new maps/counts unchanged; all older cases/negative assertions/native fixtures and original bindings retained. Existing four original cases are corrected, not added to case counts. No product repair added after b804. No SDK Book/proposal/model/campaign, allowance extension, release/tag/local branch/worktree or UI action. Deployment original cold five-second prerequisite FAIL and missing privileged physical closure remain real blockers. API-only history-merge exception does not apply to changed test bytes and does not waive this fresh full retry or golden.

ENTIRE preceding Issue body retained unchanged below.

2026-10-08 — complete lifecycle suite retained FAIL; four original oracles corrected, focused retry running

Fresh COMPLETE original b804 candidate observed 1989 total /1985 passed /4 failed /0 pending /0 todo; no prerequisite PASS or SDK launch. Report /tmp/api515-canonical-lifecycle-complete-20261008.json SHA256 7afa74dac3f572f9f1af297afac0834f4009f1b6018686eb09573067eb42076a and separate original log retained. All seven participating owner HEAD/tree/tracked-byte inventories independently identical before and after; 127 exact native TreeDX client files held. An initial in-memory custody comparison compared the command wrapper instead of parsed owners and returned false; corrected parsing proves exact actual owner equality, NOT byte drift or erased failed evidence.

Cheap focused reproduction on the SAME b804, all four COMPLETE original files, retained 23 total /19 passed /4 failed /0 pending /0 todo: /tmp/api515-canonical-lifecycle-four-focus-red-20261008.json SHA256 e40099277cf2cf03f52af34bd830b19e95758ea35fb6bc7fe0841f634c61ec71; default reporter log retains every exact diff. Three differences ONLY canonical created→leased in native governance Decision admission/claim, signed credential exchange/poll, and aborted longpoll’s NEW authorized retry. Fourth ONLY canonical created→failed plus first finishedAt on public workday operator stop. No unexpected authority/clock/budget mutation or new product failure was shown by these four diffs.

Test-only ordinary LOCAL staging commit 56e1e77 corrects those four original expectations to the explicit canonical schema (AssignmentAttempt lifecycle may advance, admitted authority stays frozen). EVERY original case/assertion/negative/binding retained. Full expected object retained; signed credential and longpoll now additionally check exact whole leased snapshot, no manufactured execution clocks. Reporter stop asserts exact raw canonical JSON of the entire original authority plus failed/first finish clock independently bracketed against the actual first public stop’s call/return and published first closingAt; second stop must retain the same bytes. Original fixture input remains unchanged. No product/fixture/config/dependency/schema/timeout/allowance change; these are disclosed stale-oracle corrections, NOT relabeled product REDs or “pass” for the failed original suite.

Four-file focused retry currently running on CLEAN 56e1e7 via /tmp/api515-canonical-four-focus-r2.ts, original node node_modules/vitest/vitest.mjs run --config ./vitest.control-plane.config.ts with COMPLETE:
tests/unit/control-plane/governance/proposals/architecture/proposal-decision-native.test.ts
tests/unit/control-plane/capacity/execution/graph/architecture/workday-closeout-persistence.test.ts
tests/unit/control-plane/capacity/execution/architecture/initial/credentials/dependency-credential-native.test.ts
tests/unit/control-plane/capacity/execution/architecture/initial/polling/dependency-longpoll-native.test.ts
Report /tmp/api515-canonical-lifecycle-four-focus-r2-20261008.json and default/JSON log separate; NO retry success yet. Fresh full suite still REQUIRED after this correction.

PR520 is Draft, currently remote b804 (not yet updated to test-only 56e1e7); required Verify37810465414/job113425683588 is running native server prerequisites. Earlier PR519 exact c9 staging→main remains in original component scenes. No merge/check waiver, no new SDK Book/proposal/model/campaign, no tag/local branch/worktree. Deployment cold five-second failure and missing privileged physical closure remain blockers.

ENTIRE preceding Issue body preserved unchanged below.

2026-10-08 — canonical AssignmentAttempt lifecycle batch committed; fresh complete suite running

Candidate LOCAL staging b804234, tree eadbc8b4711651a95de6781a12f5f5514df0b54f, tracked source SHA256 161861ea48b204691f30ae8a320969a868f3c1d1bb1c3ad7a1c55b431d1e96ac (1387 indexed entries; gitlinks pin-only). Remote staging base c9eb1bb; main 0439255. No local branch/worktree/tag, no new SDK campaign or UI change.

Native public readback of the retained failed SDK workday independently exposed twelve root-failed rows whose canonical attempts still said created. No historical row was rewritten. docs/agent.schema.yml permits lifecycle status/timestamps to advance while freezing authority/context/build/limits/workspace. This repair changes only allowed metadata at the ORIGINAL owning transition; no schema, fixture, support, config, dependency, model, storage, or parallel runner change.

Test-first commits 8b24fd9, 854aa8e, 15d4554, 0648569, 6cec788 precede sole implementation commit b804234. Seven new original-file cases, exact verifier/scene mapping (each scene step omits api.golden.):

Layer	Original file	Exact name	Verifier
UNIT	tests/unit/control-plane/capacity/execution/living-execution-lifecycle.test.ts	advances only canonical terminal lifecycle metadata while preserving every frozen assignment field	api.golden.execution-canonical-terminal-lifecycle-unit
UNIT	same file	canonical lifecycle advances preserve first execution and terminal clocks without manufacturing either during lease preparation	api.golden.execution-canonical-lifecycle-clocks-unit
REAL owning native SQL	tests/unit/control-plane/providers/assignments/lifecycle/architecture/terminal-report-persistence.test.ts	native terminal transitions persist canonical lifecycle metadata with exact frozen authority and immutable replay	api.golden.execution-canonical-terminal-lifecycle-native
REAL owning native SQL	same file	native execution start records the original canonical running clock once and closeout cannot rewrite it or frozen authority	api.golden.execution-canonical-start-clock-native
REAL owning native SQL	tests/unit/control-plane/capacity/workdays/lifecycle/architecture/terminalization-persistence.test.ts	native workday stop advances canonical terminal metadata without changing admitted authority or replaying settlement	api.golden.execution-canonical-workday-stop-native
REAL owning native SQL	tests/unit/control-plane/providers/assignments/architecture/cancellation-persistence.test.ts	native operator cancellation advances only canonical terminal metadata and retains exact failed history on replay	api.golden.execution-canonical-operator-cancel-native
REAL owning native SQL	tests/unit/control-plane/capacity/execution/architecture/initial/polling/dependency-poll-native.test.ts	native claim advances only canonical leased status without inventing execution clocks or changing dependency authority	api.golden.execution-canonical-claim-native

All seven bindings are in existing guarantees/verifiers/golden.verifiers.yaml and guarantees/agent/golden/scenes/component-boundaries.scene.yaml, scope local-component-tests. They are NOT managed golden proof, genuine model-generated usage, separate PostgreSQL concurrency, or physical teardown. Old cases and negatives retained; full expected objects now allow ONLY documented lifecycle metadata changes and still assert EVERY frozen authority field. Failed historical evidence remains intact.

Implementation touches seven owning files: assignments/assignment.ts (pure lifecycle metadata advance); original living execution projection; start-window service; lease service; recovery service; operator cancellation; workday terminalization. Original locked transactions/CAS/version/token/expiry/settlement guards retained. Running records first startedAt, terminal records first finishedAt, lease invents neither. Returned maps to canonical blocked. Exact canonical JSON CAS is used at projection/start/workday transitions; no read-time reconstruction or backfill.

Actual RED reports, zero pending/todo, retained:

/tmp/api515-canonical-terminal-red-20261008.json: 21 total /17 pass /4 genuine fail; SHA256 64312bb87410714ee61a91954f7142ee0d71a5a995641c62cdc6ad63b5b85762.
/tmp/api515-canonical-workday-stop-red-20261008.json: 6/4/2; SHA256 2aae71561491050985ac9e0f3aca047f80964a110d05f7170ceb89b47dd3df23.
/tmp/api515-canonical-cancel-recovery-red-20261008.json: 18/15/3; SHA256 fd9062c9187a992e4eeb57188064d04194be794a9ce3edb0bd594e914c128d68.
/tmp/api515-canonical-start-red-20261008.json: 14/13/1; SHA256 6cfdd285733a30f474abf077fe83289bdbdf83622e8f6afd5b3aea961d3db3be.
/tmp/api515-canonical-claim-red-20261008.json: 6/2/4; SHA256 2b1b4c0fb3450d546f99564071ef1835668c4247eeaf2bf9bc3c42fc90f5116a.

Passing focused observations OVERLAP, NEVER SUM:

original six-file terminal batch 48/48, /tmp/api515-canonical-terminal-batch-green-20261008.json SHA256 41c686738b150246b495ee4b9b9f7cfe3462e0f237a1a1ccb6d49bbc8e3793fa.
original three-file start batch 28/28, /tmp/api515-canonical-start-green-20261008.json SHA256 1001acce15a4002ad49c16d0db30bf666c8ae7b7f9dfab6f97e3320cad37fbce.
original four-file claim/public-auth/token/identity batch 23/23, /tmp/api515-canonical-claim-green-20261008.json SHA256 e2924ce655ed9bb0eb20d2d02c5f2317f1f90cec2e2519c150fa85906b1ab3d1.
Original npm run check:file-lengths and npm run build:dist (strict source build) PASS; git diff --check PASS. Supplemental node node_modules/typescript/bin/tsc --noEmit --strict --project tsconfig.json FAILED with 254 diagnostic lines outside changed files; /tmp/api515-canonical-lifecycle-strict-20261008.log retained. Its baseline cause was NOT independently established; earlier wording “existing unrelated” is NOT a proven baseline comparison or waiver. No strict test-config success claim or disabled checks.

Fresh COMPLETE original suite is currently running on held b804:
PATH=/tmp/sdk-native-node2412-PjB5qe/bin:$PATH node /tmp/api515-canonical-lifecycle-complete.ts
Wrapper invokes original npm run build:dist then node node_modules/vitest/vitest.mjs run --config ./vitest.control-plane.config.ts --reporter=json --outputFile=/tmp/api515-canonical-lifecycle-complete-20261008.json, unfiltered, original timeouts/concurrency, actual original disposable PostgreSQL/TreeDX bindings, all 127 exact installed checked TreeDX client files verified before/after. Separate log /tmp/api515-canonical-lifecycle-complete-20261008.log. NO completed result/1989-count claim yet. All seven participating owner heads/tracked bytes captured before; must independently remain exact after. Fresh required Actions and 800 component bindings remain pending, not passing evidence.

Human API-only exploratory exception: fresh tests may cross a HISTORY-ONLY staging merge if independently identical tested source bytes. No altered source/dependency/other-owner waiver, no prior-invocation receipt reuse. Golden remains OPEN. Deployment original five-second cold Docker prerequisite still FAILS; privileged physical sandbox closure report remains absent. No timeout extension, synthetic closure, new Book/proposal/model/campaign.

ENTIRE preceding Issue body preserved unchanged below.

Canonical lifecycle batch — genuine REDs retained, 48 focused checks pass

Test-first local staging commits 8b24fd9 (provider terminal), 854aa8e (workday stop), 15d4554 (operator cancellation/recovery and existing race custody) preserve all old assertions/negative observations. No local feature branch, worktree, tag, push, architecture change or old-row repair.

Actual original focused results:

/tmp/api515-canonical-terminal-red-20261008.json:21/17pass/4fail/0pending/todo; unit and native canonical metadata failures. SHA25664312bb87410714ee61a91954f7142ee0d71a5a995641c62cdc6ad63b5b85762.
/tmp/api515-canonical-workday-stop-red-20261008.json:6/4pass/2fail/0pending. New native stop + stronger original full snapshot assertion fail before stop repair.
/tmp/api515-canonical-cancel-recovery-red-20261008.json:18/15pass/3fail/0pending. Native operator cancellation and both old native recovery transitions fail BEFORE owning writer repair.
/tmp/api515-canonical-terminal-batch-green-20261008.json:48/48pass/0fail/pending/todo, complete original six files (living-execution-lifecycle, cancellation-persistence, recovery-persistence, terminal-races, terminal-report-persistence, terminalization-persistence). Native calls use original service/repository/SQL/transactions, retained actual fixture settlement, and controlled clocks/usage; not production model charge or physical teardown.

Shared small advanceAssignmentAttemptLifecycle in original owning assignment repository changes ONLY status/startedAt/finishedAt and preserves first recorded clocks. No read-time reconstruction, schema/model/storage/runner/parallel policy. Provider terminal projection, workday stop, operator cancellation and recovery writers now use it alongside their existing fenced transitions. Complete frozen fields/ordinal, concurrent winner, financial rows, interruption rollback and retained replay exactness remain asserted. Diagnostic cleanup preserves malformed bytes rather than making them executable. New bytes not yet fully verified or delivered.

Additional original bindings:

UNIT "canonical lifecycle advances preserve first execution and terminal clocks without manufacturing either during lease preparation", tests/unit/control-plane/capacity/execution/living-execution-lifecycle.test.ts, api.golden.execution-canonical-lifecycle-clocks-unit / execution-canonical-lifecycle-clocks-unit.
REAL native "native workday stop advances canonical terminal metadata without changing admitted authority or replaying settlement", tests/unit/control-plane/capacity/workdays/lifecycle/architecture/terminalization-persistence.test.ts, api.golden.execution-canonical-workday-stop-native / execution-canonical-workday-stop-native.
REAL native "native operator cancellation advances only canonical terminal metadata and retains exact failed history on replay", tests/unit/control-plane/providers/assignments/architecture/cancellation-persistence.test.ts, api.golden.execution-canonical-operator-cancel-native / execution-canonical-operator-cancel-native.
Existing recovery native bindings/UNIT classifier retained; no extra case counted.
Newly authored REAL native "native execution start records the original canonical running clock once and closeout cannot rewrite it or frozen authority", terminal-report-persistence.test.ts, api.golden.execution-canonical-start-clock-native / execution-canonical-start-clock-native. Actual start writer unchanged; focused complete file now running to establish its RED before repair. Uses original 3sec outer deadline, controlled 1sec reserve, real owning persistence; no live allowance extended.

Original source build:dist strict declaration build and file architecture checks pass for initial terminal/stop repair. Supplemental whole test/source strict tsc --noEmit --strict --project tsconfig.json FAILED (254 log lines), existing unrelated test diagnostics; no changed-file diagnostic observed. /tmp/api515-canonical-lifecycle-strict-20261008.log retained, NOT waived or a whole strict pass. Fresh full original runtime suite/build and actual scene verification on final held candidate still required. All original timeouts, concurrency and runtime permissions unchanged.

API PR519 old c9 required scenes remain running; never treat that CI as verification of these new bytes. Deployment cold native prerequisite + missing privileged physical-absence receipt still block SDK launch. Keep working on safe owning repairs, no checkpoint stop.

Canonical terminal attempt lifecycle regression — test-first, not a golden pass

Fresh complete supported assignment readback of retained workday workday-28fe5e2a-7676-4419-870f-68abdbcce872 exposes all 12 failed roots with canonical assignmentAttempt.status=created and ordinal1/rootattemptCount1; hasMore=false. Receipt /tmp/sdk515-repaired-api-retained-assignments-20261008.json retained unchanged. docs/agent.schema.yml:2239 explicitly permits lifecycle status/timestamps to advance while authority/context/build/limits/workspace remain frozen. No historic failed row or usage was repaired, no DB/governance mutation or model launch.

On original local staging base c9eb1bb, authored two new cases plus original component scene bindings BEFORE product repair:

UNIT tests/unit/control-plane/capacity/execution/living-execution-lifecycle.test.ts — "advances only canonical terminal lifecycle metadata while preserving every frozen assignment field" — api.golden.execution-canonical-terminal-lifecycle-unit / execution-canonical-terminal-lifecycle-unit.
REAL owning lifecycle service + original native PGlite transactions/repository/persistence/public settlement tests/unit/control-plane/providers/assignments/lifecycle/architecture/terminal-report-persistence.test.ts — "native terminal transitions persist canonical lifecycle metadata with exact frozen authority and immutable replay" — api.golden.execution-canonical-terminal-lifecycle-native / execution-canonical-terminal-lifecycle-native.
Original golden.verifiers.yaml and component-boundaries.scene.yaml scope local-component-tests; NOT managed golden, provider-generated usage or physical teardown. No new fixture/runner/schema/policy. Controlled complete assignment and clocks/usage are inputs. Completion/failed/cancelled/returned->blocked metadata exact; replay and exactly-one retained charge asserted. The two older whole-attempt expectations are now stronger whole-object equality with ONLY documented status/finishedAt changes; no frozen field or negative assertion dropped. Returned root has no canonical returned enum; its unfinished execution is blocked, independently of the node's next-attempt readiness.

Focused COMPLETE two-file command planned:
PATH=/tmp/sdk-native-node2412-PjB5qe/bin:$PATH node node_modules/vitest/vitest.mjs run --config ./vitest.control-plane.config.ts tests/unit/control-plane/capacity/execution/living-execution-lifecycle.test.ts tests/unit/control-plane/providers/assignments/lifecycle/architecture/terminal-report-persistence.test.ts --reporter=json --outputFile=/tmp/api515-canonical-terminal-red-20261008.json
Not whole-owner prerequisites or scene permission. All other original tests retained. Source still unchanged; tests unexecuted at this update. New source would invalidate previous API candidate prerequisites; the exploratory source-identical history-only merge exception does NOT waive new source tests.

API main PR519 prior exact c9 candidate still executes original coded scenes; not evidence for these newly authored bytes. Deployment full prerequisite remains failed cold Docker 5-second case; privileged physical sandbox-absence report remains missing. No SDK launch permitted yet.

Readback evidence: supported API checked-staging rebuild SHA256 f42e0c77fb9efb5b00c3fc73df21a1886c2623a8a67df880ba9125cf9a220007; all127 TreeDX client files inside selected API exact checked archive receipt SHA256 fc3de290d9528eee4f0c68d0e7272aad08eff8beacb31d3c933fd64e1f75a738; all12 original workspace IDs independently show CLOSED receipt SHA256 c1748ab6b23955e6276cfb02849b101afba170605e393ea5bf1e2b65f43ae979. No close/delete/rewrite, whole installed/loaded dependency or physical sandbox absence claim.

API repaired runtime and actual failed-run TreeDX closure readback

Supported checked-staging rebuild completed exit0/oktrue at API c9eb1bb. API service947 and operations-runner813, declared TreeDX dependent495 all ready; Agent provider630/sandbox424 unchanged and manual provider reaction NOT invoked. No UI rebuild, model probe, campaign, tag, deadline or allowance change. All seven primary source HEADs/trees/tracked-byte digests independently remain clean/exact. Stale historical session repository commit metadata was NOT treated as source proof. Native Docker inspection instead showed API service running original source entrypoint with the registered /home/adrian/Projects/platform/packages read-only mount. Independently read all127 declared TreeDX client files inside that API container and compared each untrimmed SHA256 with checked archive d6de27b42704b4c899562f290950561132fd0d48f38a95e6624eb853e32691cb; all exact. This proves the represented selected client payload, NOT universal tool/cache/compiled/whole dependency closure. The TreeDX dependent initially returned connection-refused while starting, then reached readiness within the ORIGINAL bound; no timer extended or retry launch.

The original supported CLI independently read ALL12 exact retained failed-run workspaces after rebuild. Every response oktrue/CLOSED with exact workspaceId/repoId/project receipt identity. Summary /tmp/sdk515-retained-treedx-checked-package-summary-20261008.json; each native response/error independently retained with wx600 in /tmp/sdk515-retained-treedx-checked-package-20261008-1 through -12 .json/.err. No close/abandon/delete/governance/failed-history mutation and no denied read relabeled absence. Earlier permission-denied and failed-run evidence remains retained. Supported rebuild receipt /tmp/sdk515-api-checked-staging-rebuild-20261008.json/.err; selected client receipt /tmp/sdk515-selected-treedx-client-readback-20261008.json. Scripts are local operational evidence capture, NOT alternate test/acceptance harnesses or prerequisite receipts.

SDK relaunch remains blocked: fresh complete Deployment native suite has one real original5000ms cold Docker failure; privileged absence report for the four exact owned sandboxes remains missing. TreeDX staging-to-main remains blocked by original4500ms p99 release profile failure, not rewritten as a success. API main PR519 required Verify37802154331 still running; native TreeDX server+client steps passed, verify:direct in progress. No main merge or old receipt reuse. Current exploratory exception remains API-only identical tested bytes across history-only staging merge; strict golden criteria and remaining179 unbound requirements stay open.

API checked staging delivery; SDK relaunch remains blocked

PR API #518 merged with ordinary history-preserving merge to staging c9eb1bb. Independent fresh protected-ref fetch, empty source diff against tested 5c2006b, identical tree 74e79e41be621f816d68100ea4f29ce435464aac and tracked-source SHA256 b577571b0b0911be65ce6fcc1bda2693e1263844c60075d2d1e0c17aef099b03 establish the human-approved API-only exploratory history exception. All seven owning primary checkouts remain clean; no local feature branch, worktree or tag.

Fresh required Verify run 37791771305/job113360742369 passed. The original complete API prerequisite is 1982/1982 with zero failed/skipped/TODO; independently downloaded, advertised-digest-verified scene artifact11560392485 has exact793/793 case identity/source/digest/binding readback, run actions-37791771305-1, scope local-component-tests, with its own fresh complete1982 prerequisite. This is NOT SDK managed golden acceptance or total semantic coverage. Artifact ZIP SHA256 0c68896aefe1f224c62fab8d19a7f50e36ddfd2d27c78c4e3ea91944de2aa3e2; report SHA256 1e2d299a186e50931951a1de049ac4e85737317094f5e2442b23c41b63a337b6. Independent source artifact11561505916 digest e626acbb4e0ad54a983c4d9aa9b62c40ff8f0dae2fbf149ebf13d6e594dc6b7a checked, including exact native TreeDX archive d6de27b42704b4c899562f290950561132fd0d48f38a95e6624eb853e32691cb. Archive/SBOM proof does not imply loaded-runtime closure.

Temporary remote codex/sdk-source-closeout515 was deleted only at exact5c after verified ancestry into protected stagingc9. Independent ls-remote confirms absent and protected staging/main unchanged. Its commits remain recoverable from staging and PR518; no history rewrite. Staging-to-main API #519 is open at exactc9/base04392551dc97f0cead9099dcde1387f4240bedb0: authorization/metadata passed, required Verify37802154331/job113396858404 still running. No main merge or check waiver claimed. PR attachment attempt reached the existing100-attachment limit; none removed.

One supported CLI dev rebuild api.service --session dev-5007e344-493 --json is running on checked clean stagingc9. The original declared dependency path includes API operations-runner and TreeDX restart; no UI rebuild or model/campaign change. Native output is retained without overwrite in /tmp/sdk515-api-checked-staging-rebuild-20261008.json/.err. Readiness, selected-build bytes and twelve old workspace CLOSED identities are NOT established yet. No SDK relaunch: fresh Deployment native suite still has the unchanged5000ms cold Docker failure, privileged per-sandbox absence report is still missing, and TreeDX main profile has the original4500ms p99 failure. Earlier failed receipts and unverified requirements remain open. No new launch, tag, allowance/deadline extension, fabricated receipt or passing claim.

Read-only discovery incidents: oversized dev-status output truncated, subsequent exact session/target subset recovered; broad /tmp filename search encountered root-owned permission denials; one guessed CLI source filename absent. These are read errors, not product RED or test execution.

2026-10-08 — final required API verification and793 component cases PASS; checked delivery pending

Exact5c2006b380ed3202c4fc03b212871a97bf048fa0 required Verify37791771305/job113360742369 SUCCESS. Native server/all client SDK prerequisites, complete original verify:direct and all three supplemental PostgreSQL groups passed. Original scene invocation actions-37791771305-1 independently audited: own fresh unfiltered prerequisite1982/1982, zero failed/skipped/TODO; all793 exact selected case records pass, each original verifier/file/test-name/raw-source SHA256 matches held5c, zero signal/process errors/diagnostics. Scope local-component-tests, NOTmanagedSDKgolden. Tested merge d8a0028 tree74e79e41be621f816d68100ea4f29ce435464aac independently equals5c tree.

Scene artifact11560392485 /tmp/api518-scenes-20261008.zip SHA2560c68896aefe1f224c62fab8d19a7f50e36ddfd2d27c78c4e3ea91944de2aa3e2; reportSHA2561e2d299a186e50931951a1de049ac4e85737317094f5e2442b23c41b63a337b6; started14:39:07.613Z/completed15:26:25.252Z. Source artifact11561505916 /tmp/api518-source-20261008.zip SHA256e626acbb4e0ad54a983c4d9aa9b62c40ff8f0dae2fbf149ebf13d6e594dc6b7a; official TreeDX archive d6de27b42704b4c899562f290950561132fd0d48f38a95e6624eb853e32691cb exact byte-identical to checked native6d client archive. SDK archive6a6db7fbe4c750c1e7c81c52d02b47ee1649ba4ec19882eeb90da38fba415307; API archive1b6084135190c576b3bedea5bc75ff849644b1903f555a738a90faaac09d7af4; CycloneDX SBOMf84ef9722d210b2c8a74303e83e1910d1f1dbf8080eb24bde82430a6da62a7c8 contains sole SDKrc122 andTreeDXrc18 components. Neither SBOM nor archive alone substitutes whole loaded runtime custody. Connector downloads returned non-local file references; authenticated gh binary fallback downloaded these SAME exact artifacts and independently checked their advertised SHA256s. No failed-job CLI diagnostics fallback.

Latest metadata validate113371910948/authorization113371906200 pass. Historical stale-description failure113360735664 retained, superseded by fresh exact-description validation—not erased or reclassified. Before ordinary merge, fresh protected-head/source check required. Human API-only exploratory history-merge exception applies only independently identical tested bytes, never changed source/dependencies or other owners. No new local branch/worktree/tag/runtime activation/SDK campaign. Prior d43 watchdog failure, all earlier fixture/oracle/read errors and entire preceding Issue body retained unchanged below.

Complete original suite PASS on byte-comparison candidate5c; remote proof still pending

Fresh original build:dist + COMPLETE unfiltered control-plane suite1982/1982, zero failed/pending/TODO, exit0/no signal/child error on5c2006b380ed3202c4fc03b212871a97bf048fa0. Command /tmp/sdk-native-node2412-PjB5qe/bin/node /tmp/api515-ci-watchdog-complete.ts retains SAME original command/env/30sec watchdog. Report /tmp/api515-ci-watchdog-complete-20261008.json SHA256014a885c0be433a81e7472f6fa9dd8e88d302266cf59b750c9573e526ab55103; log SHA2561e9b821b6650905f8fcc959fd9c38853b4e6a21fe9007682645468f30c804537.

Independent ALL7 tracked source inventories exactly unchanged across full invocation, all clean; API head5c/tree74e79e41be621f816d68100ea4f29ce435464aac/sourceSHA256b577571b0b0911be65ce6fcc1bda2693e1263844c60075d2d1e0c17aef099b03 /1387entries. Driver independently holds ALL127 original checked TreeDX payload files before/after. This changed test candidate did NOT reuse prior full results. One separate read-only report-print invocation had an extra delimiter; driver/report success remains authoritative, not a product/compiler RED.

New PR518 push validation113360735664 failed old captured description head; corrected first authorityfields now5c independently read back; fresh validate113361117522 and authorization113361116624 PASS. Original required Verify37791771305/job113360742369 pending, now through native TreeDX server/client and exact materialization. Earlier required31.360sec CI failure remains failed. No component scenes or CI/managed PASS on5c claimed, no merge/activation/new SDK campaign. Entire preceding body retained.

Required CI fails original native watchdog; exact-byte assertion cost repaired, no bound change

PR518 Verify37787866067/job113347180597 on d43b695 failed COMPLETE1982/1981PASS/1FAIL: SAME original native capacity candidate hydration test, 31.360sec under original30sec. All native TreeDX server/client prerequisites passed first; PostgreSQL supplemental steps, pack and793 component scenes not reached. Local1982/1982 receipt remains local only and cannot waive actual CI failure. Original failed Actions log/annotation and all preceding receipts retained.

Independent full connected GitHub job log read (565492 chars) supplies hydrationCommands: total native child27.428864304sec; npm ci7.550sec, real SDK development-prefix install6.554sec, all other positive/negative/prune/tree/SBOM/owning helper children completed. Truncated120000-char diagnostics omitted this failure; connected full log recovered it, no CLI diagnostic fallback. Earlier unfinished-job HTTP502/BlobNotFound are log availability failures, not product failures.

Cheap focused complete original two-file reproduction on d43b:14/14PASS/native17.630725sec, report SHA2560603886b2c271ad324bbe756681708a49fa79b9be83f6ead47ae91488464c081; does NOT relabel CI failure. Remaining archive and lockfile generic Buffer deep comparisons were replaced with native Buffer.equals on SAME untrimmed held bytes. ALL assertions, file sets, valid inputs, malformed/version/name/missing/duplicate/symlink/dist-file denials, actual npm pollution+prune+strict SBOM, exact retry and allocated cleanup retained. No fixture selection/filter/setup moved outside original callback; original30sec/test and15sec/child limits unchanged, no prewarming/concurrency/config/product change. SAME case/bindings/counts, not a new weaker test.

Changed candidate5c2006b380ed3202c4fc03b212871a97bf048fa0 (local staging clean, tree74e79e41be621f816d68100ea4f29ce435464aac): focused14/14PASS/native14.127905sec vs prior17.630725sec. Report SHA256d930ce84280379eb5c6c2acb8d724956444813349df5f4d936d8fb1789c9b149; log SHA25610d36fabfb415027d72317455fd82e2ecdadc65a5a227281edc33b19492d8aa3. Strict tsc original imports/bundler/ES2022 with strict:true/noEmit PASS; original file-length/architecture/diff checks PASS. Source-only parenthesis typo corrected before any execution, not a compiler/test failure. One Git remote-tracking ref was absent after fetch (restricted configured refspec); exact ls-remote independently confirmed d43b, no authority inferred from failed guessed ref.

Fresh COMPLETE original suite and required CI needed on5c; native CI timing repair not yet proved there. No merge/SDK launch, no oldreceipt reuse, no deadline/allowance change. Entire preceding body retained unchanged.

Final corrected API candidate: complete native prerequisite PASS; remote verification pending

Candidate d43b695, tree 5e0885a3fd1678bcf4041bc133761e420c796307. Fresh original build:dist and COMPLETE unfiltered control-plane Vitest passed 1982/1982, zero failed/pending/TODO, no signal or child error. Command: /tmp/sdk-native-node2412-PjB5qe/bin/node /tmp/api515-final-hydration-complete.ts (original node node_modules/vitest/vitest.mjs run --config ./vitest.control-plane.config.ts --reporter=json --outputFile=/tmp/api515-final-hydration-complete-20261008.json). Actual native disposable PostgreSQL/TreeDX bindings; no mocks substituted for their owning tests. Report SHA256 918af04e8715d34b17c2e4ee0a504260caeefadf0c6c75af45ed3c10f0713ef9; log SHA256 bff8f617f17803497db5c85130b63322c9314ece329bfb40b7cd3d6e8c0c93b4. Final focused regression and historical failed evidence remain below, not overwritten or relabelled.

Independent all-seven owner HEAD/tree/index-mode/tracked-byte inventories identical before and after this complete invocation; all clean. API tracked SHA256 5437ac89339a8834728cb2839827e0dbc731a7a83691ebdb489010653a22aec3 /1387 entries. Driver independently held all127 installed TreeDX payload files equal to the exact checked original archive throughout. This proves this candidate's complete suite, NOT managed SDK golden, loaded runtime, global installed closure or durable provider/sandbox teardown.

PR518 exact final head: required Verify run37787866067/job113347180597 pending at observation. Validation113347170002/run37787862028 initially failed because the push event captured the old description head before metadata update; actual log says Exact head ref is stale. Corrected description triggered validate113347377416/run37787921822 PASS and authorization113347378570/run37787922045 PASS. No test or product failure is inferred from that metadata race. One Verify log request returned HTTP502; not a workflow failure or permission for CLI diagnostic fallback.

No merge/activation/SDK launch from these local passes. Deployment fresh native1251/1252 failure and four owned sandbox physical-absence report remain blocking; TreeDX required mirror profile p99 latency failure remains retained. All793 component mappings are obligations pending this head's actual owning CI, NOT managed acceptance. Entire preceding body retained unchanged.

2026-10-08 — full held API1982/1982, then one genuine helper invariant regression fixed test-first

Complete original build + UNFILTERED vitest.control-plane.config.ts on 11ec672:1982/1982PASS, zero failure/pending/todo. Report /tmp/api515-single-hydration-complete-20261008.json SHA256916509d0cafbe291878e7426e3d90c2b82c5c045caac04f42a0104df3c7344d3; log SHA25660eec04c4d0adcc7e06cb94932b8382f5c71634460c4b83cc72ca5c17bebb406. All7 owner HEAD/tree/index-mode/tracked-byte hashes independently identical during/after complete invocation; API sourceSHA008d786a3b037ff2e8e8e469c3572e2b72a622f8d9189b1239a80c075f216cc1. All127 installed client bytes exact against checked artifact before/after. Original local native server fixture unchanged; exact6d engine proof belongs required Actions, not this local receipt.

Audit then found converted helper checked dist existence rather than original directory invariant. SAME native case strengthened with valid-name/version TGZ containing ordinary file named dist; actual childexit0 proves genuine new helper failure. First commit3494c109e8dca9b643fe7bdd4be7540f70321624; focused14/13PASS/1FAIL report /tmp/api515-hydration-dist-directory-red-20261008.json SHA25699cea2e5fddc7a8939d2a3d1427564d46ce72523921da379fd72605928097755. Owning one-line fixd43b6952639413ee37d143aabee6904672f706b0 restores directory requirement before changing any candidate bytes. Focused14/14PASS/native15.742sec under ORIGINAL30sec; reportSHA08ad17d4387f06513b1dd79fece4c2fa66f2a160149951a5dbbcdf6dc90e786b, logSHA0b69f0fa545bb003541931769355fa7a7b15d7c5645c8dc1b9088f08538953c3. No old assertion removed, no new case count, no allowance extended.

Final local staging CLEAN d43b695/tree5e0885a3fd1678bcf4041bc133761e420c796307/sourceSHA5437ac89339a8834728cb2839827e0dbc731a7a83691ebdb489010653a22aec3. Existing temporary remote branch/PR #518 updated with independent exact ref/body readback6768chars. Fresh full original local suite /tmp/api515-final-hydration-complete.ts running; FINAL-head native Actions/scenes still required. Previous11ec passing receipt retained but NOT reused for finald43b. All other6 source hashes unchanged. No new branch/worktree/tag/live activation/model/campaign/UIwork. SDK acceptance remains blocked by actual Deployment native failure and missing independent physical closure; TreeDX actual latency/main gate remains unwaived.

2026-10-08 — single native dependency hydration repair committed and checked delivery running

Local staging CLEAN at 11ec672 (tree f25b346018a4101f2e08687eb8ff4ab3162170cb); test-first commits e1ffc6a and 0f4b25d. Existing temporary remote branch reused, no new local branch/worktree/tag. PR #518 #518; automatic attachment attempted but app100-identity limit rejected it, no existing attachment removed.

Fresh final complete focused two-file command (pinned Node24.12, original vitest.control-plane.config.ts): node node_modules/vitest/vitest.mjs run --config ./vitest.control-plane.config.ts tests/unit/control-plane/release/provider-prerequisites.test.ts tests/unit/control-plane/treedx/upstream-operation.test.ts. 14/14PASS, native hydration15.375sec within unchanged30sec watchdog. Report /tmp/api515-single-hydration-final-focused-r2-20261008.json SHA2569491f8daef6546135b05ddd17274f8f3c6a39846d8baaad738ae8fcd64b8f4a2; log SHA256d9126302d5c545d47c5f12908f802c242a9964cfe577151e4a6411dd5f84668f. Strict tsc of helper/edited tests with existing TS import semantics, original file-length/architecture and git diff checks pass. File-set equality and native Buffer.equals preserve EVERY untrimmed byte oracle efficiently; measured child commands ~14sec vs former31sec test. No timeout/allowance change. One new archive fixture placed its controlled source symlink inside scanned archive-root, causing a valid earlier denial but wrong expected message; corrected source placement reaches actual archived-link denial. That13/14 failure retained as fixture/oracle failure, not product RED.

SAME owning native custody case now rejects wrong name/version, absent/multiple archives and actual archived symlink BEFORE changing SDK/TreeDX payload; independently retains archive bytes, original inputs, prior invalid-tree observation, all127 client bytes and exact retry, normal dependency-tree/SBOM checks. All old cases/assertions preserved. Original existing component bindings remain local-component-tests; new UNIT mappings recorded below. Strict TS replacement deletes superseded Bash helper; original Verify, all3Dockerfiles, candidate-seal/promote use one hydration path and existing checked archives. Original manual runtime references converted without new publication; no tag/runtime release invoked.

Fresh COMPLETE original local API suite on held11ec672b now running after original strict build; driver /tmp/api515-single-hydration-complete.ts invokes unfiltered original config with original disposable PostgreSQL/TreeDX bindings and exact127-file client custody. Native local engine fixture is the existing older server fixture, NOT falsely labelled new6d engine. Required PR #518 Actions will verify the exact6d native engine and all SDK suites plus original component scenes. Neither full suite nor scenes claimed passed yet. API history-only merge exception DOES NOT waive this changed source/dependency candidate. SDK launch remains blocked by real native Deployment failure/missing physical sandbox readback; TreeDX performance-profile/main failure unwaived.

2026-10-08 — checked earlier repair promoted; new native dependency repair remains unverified

API PR #517 ordinary-merged after required validation, authorization, complete native Verify and original coded component scenes passed: run 37774066456/job113300415532. Main merge 0439255 independently fetched; staging remains a01e2c0. This verifies the earlier source/closeout repair only, not the changed dependency candidate.

The first provisional native TGZ installation was invalidated by npm prune restoring older registry bytes at the same rc.18 version: focused14/13PASS/1FAIL retained in /tmp/api515-native-treedx-adoption-focused-20261008.json. Extraction after pruning gave focused14/14PASS in /tmp/api515-native-treedx-adoption-focused-r2-20261008.json, but did not align Docker or candidate sealing. Expanded SAME existing unit/native cases now require all three Dockerfiles and original sealing/promotion to consume the same archives through the existing hydration path converted to strict TypeScript; no new package installer/publisher/runner or architecture.

Single-path test-first observation /tmp/api515-single-hydration-red-20261008.json:14total/10PASS/4FAIL, two actual missing entrypoint bindings and two missing planned replacement-helper reads, not a managed runtime failure. Initial typed helper + entrypoint repair yielded14/13PASS/1FAIL: the native hydration test exceeded its original30sec watchdog (33.55sec, then31.71sec). These failures remain retained; watchdogs, native child15sec bounds and old npm/SBOM/strict assertions unchanged. Measuring command cost and repairing execution efficiency before another complete suite. Native archive identity/path/entry-type denial and same exact payload retry assertions added to the SAME integration case and its original scene mapping; no extra case count or passing whole-owner receipt.

TreeDX original latency profile also failed repository_read/searchRepositoryFiles p99 4642.745ms vs unchanged4500ms; #86 records its actual run/artifact. Main TreeDX promotion and Deployment's current native failure remain held. No SDK campaign, no golden pass or deadline extension.

2026-10-08 — actual dependency-custody RED; native client/server adoption regression authored before manifest/workflow repair

Fresh complete original API suite on clean a01e2c0 plus exact127-file checked TreeDX overlay: 1980total/1979PASS/1FAIL/0pending/todo. Original native capacity hydration test rejects npm tree: declared rc.17 versus installed rc.18 plus four extraneous dependencies. Strict original build passed; this is an actual dependency-adoption failure, NOT authorization to weaken npm/SBOM/receipt assertions or reuse old passing checks. Report /tmp/api515-checked-treedx-complete-20261008.json SHA256 1f9646d8eb9afbab046500c9463b18ba693d93bfcce4d9164400eafb1c4c6d5a; log SHA256 7f4e2cd2c657e1647776b5dddcb25e58de13bc2fd8138e631bab3e417ac2a4d4.

TEST-FIRST source changes, product manifest/workflow still unchanged at this checkpoint:

UNIT new tests/unit/control-plane/release/provider-prerequisites.test.ts: capacity execution materializes the declared native TreeDX client from its sole pinned verified server checkout / api.golden.execution-treedx-package-unit / scene execution-treedx-package-unit. Exact root declaration/sole override/lock entry; same native checkout ref6d358bb2e536af24918f3c33acb2072b9093a603; full native SDK verification before original npm pack/install/prune before API verification; archive retention in existing source artifacts. No second source pin or package publisher.
UNIT new tests/unit/control-plane/treedx/upstream-operation.test.ts: derives exact current workspace metadata and closeout scope from official capabilities while retaining the exact repository / api.golden.execution-workspace-capability-unit / scene execution-workspace-capability-unit. Exact get/close declared files:read + same_actor annotation and same repository; not a new filter or runtime permission policy.
Existing REAL npm/native-child extraction/hydration/SBOM case api.golden.execution-sdk-closure-native strengthened in same original provider-prerequisites file: held official TreeDX package transport as controlled native fixture input, original workflow materialization, all represented package bytes retained, sole API/SDK resolution, existing SDK hydration/pollution/denial/prune/SBOM assertions all retained. This fixture does NOT fabricate an exact native Git checkout; real CI supplies and verifies that authority. Two new UNIT scene bindings authored existing local-component-tests harness, NOT scene/managed PASS.

First focused complete two-file run:14total/9PASS/5FAIL. Four failures concern desired declaration/workflow/native closure; new package UNIT actual rc.17!=rc.18 fails. Native old tree fails before new materialization assertions, which remain unreached. Fifth was a draft oracle mistake expecting API treeDxOperationScope to remove the identity annotation; existing scope forwards exact official declaration, no canonical requirement for that extra filter. Corrected only this new draft assertion/name to exact official inventory, original assertions retained; draft failure preserved here, NEVER product RED. Full suite and first focused reports retained. Future same complete two-file command: node node_modules/vitest/vitest.mjs run --config ./vitest.control-plane.config.ts tests/unit/control-plane/release/provider-prerequisites.test.ts tests/unit/control-plane/treedx/upstream-operation.test.ts. Not complete-owner prerequisites or managed acceptance.

Smallest repair planned: existing root TreeDX dependency rc.18 and sole override; original native server checkout also supplies its verified TypeScript SDK through original npm pack/install/prune commands; original exact checkout pin becomes6d358bb, no second source field/schema/helper/runner/policy/tag. Full source/artifact custody and fresh full verification required afterward. No live rebuild or campaign from failing dependencies.

TreeDX staging mirror-federation amd64 profile job113317579245 in run37778084755 separately FAILED searchRepositoryFiles p99=4642.745ms >4500ms. Actual artifact11552890371 ZIPdigest8c0a119d678cf9cc63745ffa51b776ecfd01ddbafdb2cae752135062c5e8be1f. Server/all-language SDK checks passed but this profile remains failed/unwaived; no main merge, rerun or budget extension. Deployment cold5sec FAIL and missing privileged sandbox absence still block SDK. Full objective OPEN.

2026-10-08 — checked TreeDX dependency adopted; SDK remains blocked pending fresh API and Deployment/cleanup proof

TreeDX PR89 checked ordinary merge is staging 6d358bb2e536af24918f3c33acb2072b9093a603; local staging CLEAN, exact tree 4436950213a90c781a930f18d65c8665eecd0277 identical to tested 4f16514 repair. Fresh complete original server + all-language SDK scripts on staging exit0, log /tmp/treedx86-declared-workspace-staging-complete-20261008.log SHA256 85cc30b9fd0f77f2ca08a0c8f479a9522a38a89289319e411551d5d4877201ce. PR88 staging→main has current exact refs independently read back; full required checks still running. No tags/registry release.

Original Actions candidate-package job113313939605/run37778084875 PASS produced artifact11551461425; independently downloaded ZIP SHA256 b80974093d14152a932febec692571a2f9b160b6a9ee99fd9daa7080facdb154 equals GitHub digest. Npm archive SHA256 d6de27b42704b4c899562f290950561132fd0d48f38a95e6624eb853e32691cb; ALL127 original package/build files independently exact against held source and ALL127 installed files exact after supported npm --ignore-scripts --no-save --package-lock=false. Prior API TreeDX fresh inspection was rc.17, now preserved recoverably /tmp/api515-prior-treedx-rpSGFC/treedx. Installation reconciled65 dependency packages/13added/8removed; it is NOT identical old dependency custody. API tracked source/lock remains clean at a01e2c0. User history-only API source exception does NOT waive fresh verification after this dependency change. Original strict build:dist PASS; COMPLETE original unfiltered Vitest control-plane suite now running with existing labelled disposable native PostgreSQL/TreeDX fixtures, original owner scopes, original token-provider renewal and authority, no fake endpoints/skip/deadline changes. Launcher-only missing explicit POSTGRES_USER assertion failed before build/test and corrected to original official postgres default; not product RED or a test repair.

Prior live workspace denied-read observations remain retained, not replaced with CLOSED/absence. No supported live rebuild after dependency adoption yet. API517 main full Verify currently executing coded component scenes. Deployment fresh1251/1252 default5sec cold Docker FAIL remains fatal; no rerun or watchdog change pending human choice. Four-sandbox privileged readback still absent. All managed SDK/golden acceptance remains OPEN/UNPROVEN; no new campaign launched, no old passing prerequisites substituted, no UI changes.

Checked API delivery, actual live readback, and new TreeDX scope regression

API PR516 required Verify37764542272/job113268837683 completed successfully. Independent ZIP SHA256cb297a9028eb4c5bbba3ca1cada97515aa685e65f49b9fedc1333984d69a16a2; original report actions-37764542272-1 is local-component-tests, 1 passed guarantee/0 failed blocked skipped. Independently read ALL791 scene evidence files: exact verifier/name/file, passed exit0/no signal/processerror/diagnostic and every untrimmed source SHA256 match held local API bytes. Fresh COMPLETE prerequisite1980/1980,0failed/skipped/todo, before selected scene execution through original harness. Component proof NOT SDK managed/golden proof.

Ordinary checked staging merge a01e2c0 preserves tested1241848bc8462c8ca60c64f355b96f33878ad53b exact tree a3fe277592d6beb102271d1fa30070201faa0c7b and independently measured1387 tracked entries/source SHA256cbb5fc812d9e13e9809f48a02c778df824d5fda10c72a22f1701df419f4f879f. User explicitly permits THESE fresh API checks across ONLY this history-only exploratory merge. No changed-dependency/other-owner/strict-golden waiver. MainPR517 required Verify still running; stale historical exact-ref PR-description failure retained and fixed first current promotion fields, fresh validate/authorization PASS. No tags.

Original supported dev migrate api.service completed applied=true/pending[]/unexpected[]; receipt SHA25661b7724485abf8715a18fc3c790bab6213ef9b28b82f2dd086ab39a60804bf7b. Supported API rebuild completed API945/runner811 and dependent TreeDX493 ready; receipt SHA256089103e1756cbd48868ddd893534e25f07330d8dcabc068fb0092a49ec8708f6. Actual supported old SDK workday show now statusfailed/codeworkday_closeout_report_missing, preserving previousError and unreportedEndedPlan; readback SHA256c6418d4a1732884819068e31cc7e8bb2d82caf9d89a3f7c5331a6b780cb3774f. No fake report/reopened productive clock/charge change. The during-rebuild metadata verification failure and post-rebuild actual treedx_permission_denied observations retained separately, never absence/closure.

Owning TreeDX declaration defect found: adopted getWorkspace/closeWorkspace advertise ONLY workspace:same_actor, while current server enforces files:read. TreeDX86 now contains original UNIT + real SDK/native-engine HTTP integration + existing shared workspaces.create_get_close conformance mapping; test-first8536efe actual40/38PASS2genuineFAIL, log SHA25658074b5dd777573f6cd32f8abf63adfacfa909f390b2fef0fc4286d08cfb6c34. Earliest OpenAPI annotation repair4f16514a5efe790c8edd0bbc6648dbad0c3d7232 plus original generated inventory/spec/digests only; no newcapability/privilege/architecture/policy/harness. Original full server + ALL SDK scripts exit0; TS40/40/nativeengine, API270/OpenAPI4/storageAPI8/Rustall0fail/ignored/filtered, Python33/SDKRust3+47/Elixir32. Log SHA256a53c644886f614c88be3d1154c3a0d67953db28a90baba7145631ee5a06ce176. Required PR89 Actions running, exact checked consumer archive adoption pending. No new local branch/worktree/tag; reused temporary remote codex/workspace-cleanup86 only, clean after checked main.

Deployment fresh attempt5 remains FAILED1251/1252 original5sec coldDocker fixture; no oldpassreuse/watchdog change/rerun or inventedcause. Pending human choice on preserving entire cold-path5sec vs separately bounded setup; no answer assumed. Four-sandbox privileged absence report still missing; revoked public rows/denied metadata NOTphysical closure. Existing Agent SDK teardown scene strict/unproven. No new SDK campaign/proposal/model activity; whole golden OPEN.

SDK retry prerequisites and cleanup regression — 2026-10-08 11:54 UTC

SDK full original560/560 PASS after cheap original canonical-file10/10 investigation and a complete sequential rerun, samef43bd785 bytes/config/15sec watchdog. Original parallel559/560 failure remains FAILED; case16714ms, isolated9151ms, complete rerun8983ms. No assertion/timeout/product change. Report /tmp/sdk515-paging-next-sdk-full-r2-20261008.json SHA256c08a6cf99042b6bbca30e1b9946b2e98a37e04bfdd7f21c92b24ca8fd4563a3c. Fresh Agent900/900, CLI357/357, Reviewer174/174 and original full TreeDX server/allSDK scripts passed as recorded previously. TreeDX now has a new genuine regression/repair candidate, so its previous receipt does NOT qualify that changed owner.

Deployment original fresh run37724744422 attempt5 FAILED1251/1252: original development-component-status-native.test.ts/component-image-11 five-second case exceeded5000ms; native docker run5982ms, create5870/start6015ms. No scene admitted. Daemon after-failure overlayfs/AppArmor/unpacked/version29.4.2 facts do NOT prove cause. Prior attempt4/3 passes are history, not reused for this invocation. No unchanged rerun or timeout/prewarm/storage/vendor workaround adopted. Fresh SDK admission remains blocked by this failed prerequisite.

Checked CLI mainPR287 required37770948010 and validate37770981468 PASS, ordinary merge c8bb65867034fb18cfcf570c9e1f221ca574c62e independently fetched. Staging remains cleaneac0c33. Checked Agent mainPR372 Verify37770135105/job113287406390 and validate37770172560 PASS, ordinary merge1dbc7a72677d794b873f6ec6435f7dc2689a4be7 independently fetched; stagingfefd0fbf clean. Temporary used remote branches already removed after ancestry. No tags/releases/new local branch/worktree. API516 current verify37764542272 still original coded component scenes; complete native prerequisites passed, source1241848 unchanged. Latest human history-only API merge byte-equivalence exception retained; no merge/migration yet.

Retained SDK workday28fe5e2a-7676-4419-870f-68abdbcce872 exact supported --workday one-page inventory12FAILED/0active; no filtered history removed. Actual complete usage24rows=12aggregate+12informational diagnostics; ledger12actual settlement rows, each represented canonical UsageSettlement, not independently proved whole Lease/Reservation/Settlement semantics yet. Public old teardown.verified does not prove physical closure. Operator TreeDX workspace read independently DENIEDtreedx_workspace_revoked, not absent/CLOSED; physical four-sandbox root read script still awaits authorized user execution. No credentials printed or permission bypass.

Owning TreeDX #86/PR87: original direct/native workspace revocation test strengthened and committed FIRST0a6da019474a03cbfc515dc196b55aad76ef63aa; genuine owning metadata RED log8426b5475f774e34f8a68899f7550e5aac08f7b57c0a4be8749ed8d7e05ea456. Added current-capability/foreign-repository/still-revoked file denials FIRST02ceb5a, genuine scope RED log652bf0f11d6aee5dc9ee50e5e63e650930c1872954be156a3e570fb1ab516034. Smallest repairb93f6673be33abff510d1f8a437785a4ce453d22 ONLY original Workspaces.get requires exact owner/read capability/repository and returns unchanged metadata without productive policy mutation. File/write/exec revocation unchanged. Original native revocation/capability-matrix/repository-controller complete11/11PASS; original complete server and ALLSDK scripts fresh execution on exact new candidate complete0 (log digest follows exact readback). No new TreeDX scene harness. Original Agent sdk-runtime-golden teardown scene still demands exact native CLOSED resource/readback; NOT executed/passed new managed run. Full acceptance still OPEN. No UI work, policy/model/cap change, new SDK proposal/workday/activation or fabricated receipts.

Checked SDK/Agent merges and CLI candidate-custody correction — acceptance remains open

SDK PR383 passed full original Verify37767748480 and protected staging Verify37768823430, merged f43bd785c3d1caf4260c3e1f9d8d41b26b1cdb9b. Main PR384 passed verify37769105065 + validate37769105059 and merged4024720b3ea465a606c42e85fbf8ea48bd47bbcb. Remote temporary SDK branch deleted after preserved ancestry. Agent PR371 full required Verify37767807801 and validate37767807909 passed; staging mergefefd0fbf1010b6b670359a251decfc01bf706926, temporary remote branch deleted; main PR372 pending its own required checks.

CLI PR286 head0db75c46280d65ef2bbb442bf10db5d4bbdac9c4 pins original exact SDK installer to f43bd785. Checked artifact11547202736 from successful protected SDK run37768823430 independently verified ZIP SHA256 b6f2be9fa8a2df2e7e89cdf33f415209245d267a8e89f1c0132cf382ea2bf23d. Original extracted package + original npm dependency installation used; former generated SDK retained recoverably /tmp/cli274-prior-sdk-t6usXH/sdk. Prior CLI Verify37768904943 retained357/356pass1source-custody failure: original generated docs had not been committed. 0db75c4 commits ONLY original generator output docs/command-reference.md + schemas/command-tree.json; custody test/assertions unchanged. Focused COMPLETE assignment-pages + native source-custody4/4,0fail/skip/todo: PATH=/tmp/sdk-native-node2412-PjB5qe/bin:$PATH NODE_OPTIONS='--import=./tests/support/os-custody.mjs' node --import tsx --test tests/unit/command-boundary/observation/assignment-pages.test.ts tests/integration/source-custody.test.ts. /tmp/cli274-workday-filter-green-20261008.tap SHA256690ca528f19989791c4fb4e967493552ea73efc6627cc45ee155238a6dfe0ead. Complete original CLI verify:direct running with original Platform authority; no waived failures.

Supported exact-workday public read now completes original40-page bound in one page: workday-28fe5e2a-7676-4419-870f-68abdbcce872 EXACT12failed/0active; four actual sandbox IDs remain to verify physically, zero inline usageSettlement observed (not proof of absent accounting or zero actual charge). Protected raw receipt /tmp/sdk515-retained-run-scoped-20261008-*; assignment JSON SHA256 dd2f0914d6e61b76999f1d3b606f56632f4582726aa4533b96299c7ad9fda377. Older incomplete40pages and failed campaign retained unchanged. No new SDK launch yet. API516 complete native suites passed, coded component scenes still running; original0046 live migration remains NOT applied until checked merge. All7 fresh complete suites needed after final candidates stable, no old invocation receipt reuse. No UI edits, local branches/worktrees/tags/automation, fabricated report/usage/PASS or issued-clock refresh.

2026-10-08 — Workday-scoped reader repairs committed; checked source repair merged

Agent PR370 checked merge64865b9a355d647ee9c06ee1017c76f94902e977 preserves c8da732b84dbd7a12fad0012d0260653b22f32f2. Its Verify37764608588 and corrected submission validation pass; original validation failure retained. API516 still running original component scenes after complete verification/PostgreSQL checks. Deployment37724744422 attempt4 all three jobs pass including disposable installer/native suite and coded sandbox scenes.

SDK regression-first7f4eb186 then repair86e14866a63ac640115d0face764b6342dad587e; PR383 opened. Focused33/33 plus full existing npm run verify:direct560/560 pass (/tmp/sdk376-workday-filter-verify-direct-20261008.log SHA25619863a1d8ee5fee14009a897fa8c4642a00e0d656b93b64d62b4e0ced74a9e9a). Agent regression-first0e6d204 then repair90eb7779f609a7597b2307ca1d569e05e7680489; PR371 opened. Focused12/12 and complete original suite900/900 pass (/tmp/agent368-workday-filter-full-20261008.json SHA25671c31f8f7877057be2c64224c2f20639068a6d93c170412b523de5a774d2f4d6). Local suite crossed ordinary commit metadata only; required exact-head Actions remains delivery authority, no next-campaign prerequisite reuse asserted.

CLI regression-first308a719 then existing exact-SDK installer Action pin c0041d8feb6a6ce8df1187247e9a68de88c924e4; PR286 opened. No CLI hardcoded route or new parser/schema. Its native tests remain blocked on checked SDK artifact, not relabeled passing. Original independent public API/native SQL filter tests source-read complete and unchanged. All new original component maps retained; full SDK managed acceptance still OPEN.

My additional command mistakes retained: SDK verify:local absent (corrected to original verify:direct); premature read of still-running Agent report was missing-file diagnostic, not suite failure; I mistakenly passed --help to read-only retained-run script, which performed one public read then refused wx overwrite with EEXIST, preserving all original pages. No mutation, test/run receipt or product RED claimed for those errors. Guessed absent source paths/read-output truncations do not prove defects. PR attachments hit the app's100-identity limit; PRs exist remotely but could not attach, no unrelated artifacts removed.

Next: finish required Actions, merge checked repairs, install exact SDK into CLI through existing artifact path; supported API0046 migration/rebuild, independently close failed SDK resource/finance inventory; fresh complete all-seven prerequisites before new exploratory SDK campaign. Previous failed campaign remains failed, research14400 exception remains only exploratory, no deadline/model/architecture change. No tags/local feature branches/worktrees or new heartbeat.

2026-10-08 — source and Reporter closeout repairs submitted for native verification

Tests-first commit 6d37a17 and repair commit 1241848 are on local staging (tree a3fe277592d6beb102271d1fa30070201faa0c7b). Temporary remote PR #516 targets staging. No local feature branch, worktree, tag, or live database write.

Required Actions run https://github.com/treeseed-ai/api/actions/runs/37764542272 has passed the complete original native TreeDX server prerequisites; remaining original native client/API/PostgreSQL and coded-scene checks are running/pending. Local focused source tests remain 77/78 with the missing disposable TreeDX case explicitly blocked, not waived. Local closeout/migration focused complete files pass as recorded below. Data-only original migration 0046 is NOT applied live: only checked delivery followed by the supported API development migration/rebuild may correct the old false-ended row into explicit failed/closing history. No fake report or charge and no repaired campaign pass.

PR attachment was attempted but the app rejected its attachment count (>100); GitHub PR exists normally. Full SDK acceptance and physical failed-run reset remain open.

Checked repair and retained unreported closeout history — 2026-10-08

Tests committed on local staging FIRST: 6d37a17 (seven source/stop UNIT/native cases and original scene mappings); implementation remains pending delivery. Stop RED /tmp/api515-stop-closeout-red-20261008.json SHA256 5f0cc10be729880e67b068c33c6a96957b63a3eb61b921fe7cb825852fd35b2a. Widened stop/lifecycle/cancellation repair52/52; subsequent closeout/cancellation/recovery/migration24/24. The reporting-node predicate exposed four older fixture mismatches: cancellationDatabase supplied an acting canonical attempt while retaining reporting SQL kind; fixture kind now matches that existing acting input. Every old unknown-usage, lease preservation, exactly-once settlement, interruption/retry and orphan negative is unchanged and passing; prior failures retained.

Required data-only original migration 0046_repair_unreported_workday_closeout.sql: exact invalid non-conversation ended-without-report rows become FAILED/CLOSING (not completed, no new admission/report/clock/charge). Prior erroneous plan and error retained in existing error_json; summary, completion clock, assignments, finance and audit histories unchanged; valid ended/report rows unchanged, repeated migration byte-stable. Native regression in ORIGINAL workday-closeout-persistence.test.ts: native migration retains unreported ended history as an explicit failed closing workday without fabricating a report or changing valid runs / api.golden.unreported-closeout-migration-native, original component scene matching step. First9/8PASS/1missing migration file is an unimplemented-artifact observation, NOT a new executed product RED; actual defect established by SDK and stop UNIT/native missing-report failure. Original component bindings remain NOT executed; actual stopped/campaign scenes still required. Applying this migration must use supported dev migrate api.service scoped manager operation AFTER checked delivery, no direct live SQL or DB editing.

API original strict whole-test tsc remains failed (existing broad diagnostics); five introduced test-only diagnostics corrected with typed owner/schema/Reflect read and no check disable. r2 has zero diagnostics in all edited source/test paths. Original distribution build and length check pass; complete native CI is still required. Whole golden open. All earlier history follows unchanged.

Operator stop genuine canonical closeout RED — 2026-10-08

Complete original three-file focused command: node node_modules/vitest/vitest.mjs run --config ./vitest.control-plane.config.ts tests/unit/control-plane/capacity/workday-stop-reconciliation.test.ts tests/unit/control-plane/capacity/execution/graph/architecture/workday-closeout-persistence.test.ts tests/unit/control-plane/capacity/workdays/lifecycle/architecture/terminalization-persistence.test.ts --reporter=json --outputFile=/tmp/api515-stop-closeout-red-20261008.json (pinned Node24.12). 15 total,13 passed,2 genuine failed regressions, BOTH exact missing reportRef canonical error reproducing actual SDK stop failure. New UNIT operator stop retains canonical closing authority without inventing an ended report and permits an unchanged closeout retry / api.golden.operator-stop-closeout-unit; real public-service/original repositories/lifecycle/native SQL integration native public operator stop retains the closing Reporter node and canonical reads until its exact completed report and settlement / api.golden.operator-stop-closeout-native, original component scene step IDs omit api.golden. Native report/result and integration audit are controlled inputs, NOT native publication/model/physical closure. Original managed campaign and stopped.scene remain actual acceptance obligations, not executed again. Original phase deadlines, usage checks, exactly-once release, retained failed history and teardown assertions unchanged. Desired original lifecycle: stop ordinary admissions, retain running/closing and required reporting node, preserve ordinary failure/lease grace, end ONLY on actual exact report plus settlement; operator outcome remains cancelled at that point. No new authority/model/storage/runner.

Source repairs focused API78/77PASS/1missing environment; Agent widened76/76PASS after explicit positive fixture Git-context correction (including later cycles), all old negatives retained. None constitutes complete owner prerequisites or managed PASS.

Source-custody regression evidence — 2026-10-08

API complete four-file focused invocation r1: 78 total, 72 passed, 6 failed. Three genuine source authority failures, two introduced fixture errors (null workItemId; nonexistent original-DDL execution_mode column), one missing disposable TreeDX environment. Fixture-only corrections retained r1; r2: 78 total, 71 passed, 7 failed. Five new regressions now reach genuine owning failures (frozen Proposal context UNIT/native, canonical identity UNIT/native, missing exact-context denial UNIT); original predecessor UNIT additionally exposes leaked queued gateway mock from the early failing new test and will be isolated, not relabeled product RED. Existing native electorate test still lacks disposable environment. No acceptance launched. r1 SHA256 3e8ef4f828c264dd69688d076cc2c1b1c1db7568d61a7ebdaa369b42e807dab2d (correction: exact measured digest is 3e8ef4f828c264dd69688d076cc2c1b1cdb7568d61a7ebdaa369b42e807dab2d); r2 /tmp/api515-source-custody-red-r2-20261008.json SHA256 f7d85e3b9d2411c695603955bb36013d5fa060fc7c58b7856a96e7f2d97accd2. Exact complete commands retained below. API582f1d02 implementation unchanged during both observations. All original assertions retained. Component scene mappings declared, not executed or managed PASS. Earliest repair reuses frozen planningSourceByProposalId and original readExactProposal; signed source must match issued repository/commit/branch/ordinal, transport exact commit, no post-issuance source authority.

Authored focused source-custody regressions — execution pending

API staging582f1d02 unchanged; original product/checkers/fixtures unchanged so far. Added5cases, original older assertions retained:

UNIT ready-execution-node.test.ts — "retains frozen selected Proposal Git context for workday planning without following later proposal versions" / api.golden.workday-planning-source-unit.
REAL native SQL/committed Git Proposal/official HTTP client/workItemContext: governance/proposals/architecture/proposal-decision-denial-native.test.ts — "native workday planning reads frozen Proposal source bytes and denies moved or denied content without changing SQL history" / api.golden.workday-planning-source-native.
UNIT workspaces/source-workspace-service.test.ts — "signs the exact canonical Git repository identity rather than its database row id for source-read planning" / api.golden.source-canonical-identity-unit.
SAME UNIT file — "denies missing exact canonical source context before pinning or upstream lookup instead of adding authority after issuance" / api.golden.source-exact-context-unit.
REAL original admission/account/lease/native SQL/source authorization: execution/architecture/initial/leasing/dependency-lease-native.test.ts — "native source authorization retains the admitted canonical repository branch and ordinal through exact repeated reads without changing finance" / api.golden.source-canonical-identity-native.
All five original golden.verifiers/component-boundaries bindings added; local-component-tests, not managed whole acceptance.

Agent original golden-grant-readback.test.ts added UNIT "denies source read authority without its frozen exact Git context rather than accepting a later provider pin" / agent.golden.source-context-required-unit, original component binding added. Existing actual SDK campaign/live graph and context custody gates consume verifyAssignmentAuthority; will require every declared sourceRead to have an already frozen Git context, not a later source pin. Checker repair not yet made. Existing positive verifier fixture currently omits this authority and requires explicit fixture correction, never removal of genuine denials. Existing native source attachment adversarial/Unix HTTP integration remains retained; API native above exercises the actual producer, not a controlled Agent API reply as managed proof.

Future focused complete files (NOT acceptance prerequisites): original API Vitest control-plane config ready-execution-node/source-workspace-service/proposal-decision-denial-native/dependency-lease-native; original Agent Vitest golden-grant-readback plus original source attachment/source workspace files. Tests will run before implementation. No compiler/run/PASS claim yet; this is uncommitted test-first authoring.

Actual native records additionally show all four are TreeDX planning workspaces with empty Git context, sourceRead treeseed-ai/sdk. Existing frozen planningSourceByProposalId points at original selected Proposal c62578facaf10c796005256034d2885c257418ad / SHA f7d9a4... / version1. Earliest loader can reuse that supported existing Proposal authority rather than create another source field or resolve moving source after issuance. API source mode currently recomputes a branch from row metadata rather than using the immutable issued workspace.branch; the real-source test also asserts retention of that one authority.

SDK exploratory source custody and workday closeout repair

Continuation of API #498, whose complete historical body remains unchanged (261655 UTF8 bytes; no room for decision-complete mappings). Central Platform #634; Agent #368. No new branches/worktrees/tags or UI work.

SDK exploratory 57480afc — actual failed attempt; repair active

The authorized fresh API checks were used only after independently proving tested ec0cd56, CI virtual merge 0075f1d and staging 582f1d0 have identical tree 4b91a68da397d16c4de149b28dd5799105782a03. All other six participating owners completed fresh full suites before this invocation. All seven exact indexed source inventories were independently unchanged at invocation closure 2026-10-08T10:08:55.509Z; no prerequisite receipt is reusable for another campaign.

Original native case "Frozen SDK campaign drives planning acting review and terminal golden gates" / agent.golden.live.campaign admitted workday-28fe5e2a-7676-4419-870f-68abdbcce872 from new campaign sdk-exploratory-20261008-57480afc. Original run start09:44:10Z/duration3600/planning100/3/turn180/concurrency3/model and caps unchanged. Manifest /tmp/sdk-exploratory-operator-57480afc-20261008.json SHA256 bc97eff887ca9ba33a0ecc39e240896920610ec5e3b4cba75dc39f32183c49ee; write-once native freeze /tmp/sdk-exploratory-freeze-57480afc-20261008.json SHA256609263986e69734d6f99257887e92bce37bb5e483137c70e3b0d9a5fa8252000. Report /tmp/sdk-exploratory-campaign-57480afc-20261008.json SHA25607eb7e997c56d110b0c9c83e35acb6f7b4dfb960f1cf8ffb587bcc95a8508165: one actual failed test/zero passes, exit1, ACCEPTANCE_CAMPAIGN_STOP_FAILED. Aggregate reporter did not expose the primary inner cause.

Supported raw workdays.list retained cancelled row completed09:48:37.445Z. Canonical workdays.show/events.list and one bounded original stop retry reject reportRef: "An ended workday requires its exact TreeDX closeout report." No fabricated report, repair of stored rows, relaxed canonical schema or campaign retry. Complete supported running-assignment query returns zero/no next page; this is NOT physical resource/usage/settlement closure.

Known-run assignments first page retains12 failed/released rows (page hasMore, not whole inventory). Four original planning assignments Architect/Researcher/Reporter/Reviewer failed agent_kernel_failed "Source authorization changed assignment custody." Their immutable canonical attempts have sourceRead=["treeseed-ai/sdk"] but no Git contextRefs; each persisted original source pin has database repository id c1b4c4b8-083e-4789-bdcc-410bc6618ef6 and exact SDK commit dff6758d0cdebe42da6d0b936e4c862dd6d63b2d. Source-only trace confirms API signs database repository id while Agent requires canonical owner/name, and workday-bound context loading drops the already-frozen selected Proposal's work-item source refs. Precise actual returned source authorization was not independently retrieved; no fabricated grant claim.

API stop source unconditionally overwrites appliedPlan.state=ended after existing closing lifecycle, without requiring its actual Reporter reportRef. Both owning regressions/real integration/component bindings plus managed existing campaign/readback gates must be aligned BEFORE repair and fresh acceptance. Failed history, stop invariant, negative authority assertions and original bounds remain retained. Physical cleanup, all-attempt charges, full SDK golden and remaining179 bindings remain OPEN. Research cap14400 vs7200 remains explicitly unverified; no cap/allowance raised. UI deferred.

Test-first owning work

Planned focused UNIT: original ready-execution-node.test.ts workday-bound selected Proposal context; original source-workspace-service.test.ts exact canonical repository identity and missing source context denial.
Planned real integration: original proposal-decision-denial-native.test.ts native SQL, committed Proposal bytes, official read transport and workday-bound source loader; original native admission/lease fixture and real source authorization/public Agent source consumer where supported.
Existing API golden verifiers/component-boundaries scene bindings will map each exact case before execution. Original Agent native campaign/readback gates must additionally prove actual frozen source before preparation/attachment, unchanged authority, failure history, all-attempt settlement and durable closure; component transport cases alone are not managed proof.

Stop repair separately needs exact mandatory Reporter reportRef, existing active→closing→ended lifecycle, public readback/events and all original assignment/finance cleanup invariants. No fake report, invalid historical-row repair, new runtime/schema/parallel policy, model/cap/deadline change, or weakened authority negatives.

Current local API staging 582f1d0 CLEAN; origin treeseed-ai/api. Source custody unchanged through failed invocation; all next acceptance prerequisites must be new on repaired candidates. No new regressions authored/executed or product repairs yet. Next precise maps and genuine RED/PASS evidence belong in this body and Actions artifacts.

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.

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: treeseed-ai/sdk#387.

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.

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

PR #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.

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.

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.

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.

2026-10-10 — exclusive archive prerequisites on the next held candidate

The third failed #529 run 38011997784 remains failed: 374 files, 2018 passed and one failed assertion. Its archive command reached the original 25-second work bound while the second Vitest worker ran PGlite accounting/persistence cases. No scenes ran. The complete suite took 874.24 seconds with 1575.63 summed test seconds; serializing every file would risk the unchanged twenty-minute full-suite boundary.

Focused regression c02c5794 precedes repair b145c816bf48cd523ac160f94873d27e464556a8 (local detached, not pushed). Existing native Vitest projects now give the archive file exclusive first-phase ownership, followed by the original two concurrent database workers. All 376 current test files are discovered exactly once; no test, thirty-second assertion bound, twenty-minute prerequisite bound or production dependency is removed. Native fixture proof executes the actual unchanged configuration, proves archive termination before subsequent work and proves both later workers remain simultaneous. The original archive subprocess helper is extracted intact and reused, not duplicated.

Focused actual production API/SDK archive installation, subprocess interruption/cleanup and resource ownership checks pass 6/6 in 13.19 seconds; strict checks for the changed TypeScript files and source architecture checks pass. Existing component wiring contains 832 refs with zero plan diagnostics. Controlled native worker fixtures do not prove native PostgreSQL concurrency; fresh full suites and existing PostgreSQL supplements still belong to Actions. No fourth CI invocation has started. The next candidate will batch this resource repair with the checked executing-Reviewer dependency preparation repair, so known prerequisite gaps are fixed before another full run. SDK launch and binding completion remain blocked.

Final fourth candidate submitted after prerequisite fixes converged

API #529 now holds 6ebbebe9ede0f3cccb6e61e3c33f8dba85d47700 (ordinary fast-forward from retained 6f48e960): resource regression/repair c02c5794 → b145c816, checked-Reviewer pin regression/repair 22e33b38 → 6ebbebe9. Final focused publication/pin contract passes 6/6. Fresh protected fetch confirms staging 789a94e99cb18bea28017af4463f1fcea5695418 and main 93563a71831659860bfd04fc4e366bae73b9c384; no protected history is rewritten.

The batched Actions 38025646915 is running. Expected final inventory is 376 files / 2021 tests and 832 component refs; full/native PostgreSQL/fresh Reviewer prerequisite and scene evidence are pending. No passing receipt or managed readiness is inferred. Reviewer #111 is now merged at 9dc625e2186e6d618cea30a17afd79fe64a95998 with required 38024840189 fresh 196/196 and 110 steps, exact tested tree 4ff193dd1552dadd97381944c0c4ea3b84d5f6b2. All historical API failures remain retained; no blind rerun or deadline change.

Fourth candidate failure preserved; nested native preparation repair held (2026-10-10)

API PR#529 exact6ebbebe9ede0f3cccb6e61e3c33f8dba85d47700 run38025646915, tested merge47e7513522306bf6736983af09fee9822283874e: complete376files2021/2021 tests and native PostgreSQL3+17+28 supplements passed; all original native TreeDX languages passed. Exclusive archive scheduling repaired prior resource contention. Later nested Reviewer setup-beam failed ETXTBSY replacing same active OTP27.3.4.18 binaries, not an unexplained mirror outage. No fresh scene prerequisite receipt or scene execution. Full failed log SHA256dae55e1a9f86c19e548328727640cdf3653698fd40ac42cba7a680cfb2184a2f; original native artifact11659329876 ZIP4a11353db822f0bdc664cf0432cddbc2ca82646b2a0a221e6d15dc8f278d825d retained. API completed before cancellation was attempted; it was not canceled. All historical failures remain failed.

Reviewer#112 regression-first983351c2b78db78c2e91646f24237976227cf669 measures exact declared OTP/Elixir before reuse, refuses unhealthy/mismatching configured runtimes, and passes explicitly declared SDK artifact identity into held repaired SDK helper. Its own native CI must pass before replacing API workflow pin. Do not rerun the known failed candidate, weaken prerequisites, replace live native binaries or extend deadlines. Native CI/current managed acceptance remain pending.

Checked native delivery — 2026-10-10 07:18 UTC

PR #529 delivered staging a5451539929c33d00bbdf2b42337a34425555be0 by ordinary merge, preserving focused-regression-first history. Required 38030377567 passed all native TreeDX server and SDK language prerequisites, initial376files/2021assertions, native PostgreSQL3+17+28 supplements, then fresh complete API2021 and held executing Reviewer199 before832 component steps. Zero failures/skips/todos/diagnostics. Reviewer77f8 remained held during the invocation. Tested merge 800ed5dd88c3777db0de294df76c69af9d0303b5, tree c7df450c18d6d8fc91f32e99c9ba1d0004a17f3d equals merged staging tree. All current authorization/validate/verify checks passed. Artifact11663287889 ZIP SHA256 426f862d24e4a38c2e4d8ccc7fd92fabc3ffd28733908d15feafabc8180fc93c; report a23170effdd3436275e0332130c06f42bf0762e38891fab8f09055da826c1e80; API sourceDigest e8af557d52f6ff77827b2cb267b285d13fe945e4625d78c443ef22f561f275b5. Native prerequisite artifact11662703619 SHA256 fbdd4b7cc85c7d7a5769663bf52aed1640ad25514737b917c6c857da42bb7c63. Clean primary staging fast-forwarded; historical local main retained; only this delivery's temporary remote branch deleted under exact head lease. Earlier failed runs remain failed. This proves the bounded producer-inventory/package/resource-ownership component delivery; it is not a managed SDK or golden acceptance pass and does not complete all API-owned semantic bindings.

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

2026-10-11 07:13 UTC — complete normal SDK assignment/reservation producer proof

Authorized strict implementation continues through SDK #393. Owning scope: API acceptance inspection and its existing unit/native PostgreSQL cases; no API product rewrite, SDK product fix, new model/storage/runner or changed proposal semantics. The current normal SDK case reconciles full assignment/event/usage/ledger inventories but does not join every issued canonical attempt to the complete native/public reservation inventories. This is an acceptance-verifier completeness defect; no API runtime defect is yet demonstrated. Criterion 179 and related accounting obligations remain unchecked until adequate native and selected proof is delivered.

Hold fresh staging 7e9d932136e2d672b2afd01dbb7c088e76f3df16. Extract the existing canonical native/public assignment assertion into the existing execution-inventory assertion module, preserving its behavior and using the same assertion path from the normal SDK case and original competing-claims PostgreSQL test. Add a focused semantic regression that shows matching assignment views are insufficient when reservations are missing/foreign/duplicated/stale; then require exact native reservation and public inventory joins, canonical reservation identity/scope/amount and original assignment lease/node authority. Capture/replay complete reservations through the existing native read-only transaction and owning reservation repository, joined to supported public assignment reservation references, retain failed observations and unchanged retry, and strengthen original independent PostgreSQL connection coverage. Keep genuine cold start/default priority allowed; retain stronger sample requirements for the separate later architecture case. No fabricated attempts, usage or terminal results.

Fresh complete API and executing Reviewer suites, native PostgreSQL supplements and applicable component scenes must pass on the held final source in existing required Actions. Focused tests cannot substitute; unavailable local native PostgreSQL remains unproven rather than skipped. Package actual selected assets and verify installed custody; only the integrator changes shared SDK scene/bindings after owner proof converges. Preserve existing Issue evidence and all failed observations. Delivery remains ordinary PR/Actions/staging/read-back; no managed campaign is authorized by this proof change alone.

2026-10-11 07:34 UTC — reservation-proof regression and repair candidate

Focused RED commit d971fccf13e9cebbf8e09ed8d17aa66288591114 reproduced acceptance of matching assignment views with an empty reservation inventory (2 passed, 1 failed, zero pending). Repair a89d0563 keeps original canonical bytes and joins each assignment to exactly one owning reservation, including replay identity, team/project/workday, provider/member/class, ready-node revisions, lease projection, reserved amount and raw numeric/clock validity. Existing owning reservation serialization validates its existing state contract; no duplicated state model or new resource. Focused original native-inventory cases now pass 3/3; strict build and file policies pass. Expanded failed observations remain retained. Local native PostgreSQL is unavailable and remains unproven pending required Actions.

Contract correction: supported CLI has no capacity reservations command. No such command is added or shipped. Managed proof uses original SQL inventory and existing public assignment/attempt reservation references; the original real PostgreSQL integration independently compares the owning CapacityReservationRepository inventory and verifies foreign-owner/changed-amount denial followed by exact restoration. Unit, real integration and existing managed normal/architecture cases share the original assertion. No managed SDK run or criterion179 completion is claimed.

2026-10-11 07:58 UTC — native fixture failure retained and corrected candidate

API532 initial Actions38121670804 failed before any component scene:379files,2026assertions passed/1failed. The foreign-team corruption fixture hit the original fk_capacity_reservations_team23503 because that team was not seeded. Classified as an implementation defect in the owning integration fixture; no production defect or passing native observation is claimed. Ordinary follow-up 297f0b3331bf42c7b7720f927c74f9f24b3c912f seeds the valid foreign team so the intended ownership verifier is reached. Constraint, original denial, observations, exact restoration, watchdogs and all original regressions remain. Focused native-inventory3/3 and strict build pass; native corrected fixture remains unproven pending replacement required Actions. Do not reuse failed invocation prerequisites.

Focused command: pinned Node24.12.0 node node_modules/vitest/vitest.mjs run --config vitest.control-plane.config.ts tests/unit/control-plane/capacity/execution/architecture/native-inventory.test.ts --reporter=json --outputFile=<retained-json>; npm run build; git diff --check. Complete entrypoint remains unfiltered node node_modules/vitest/vitest.mjs run --config ./vitest.control-plane.config.ts; required workflow retains native PostgreSQL supplements and fresh executing Reviewer before component scenes. Criterion179 remains unchecked; selected integration and managed acceptance remain blocked.

API#532 exact native delivery — 2026-10-11 09:19UTC

PR532 source297f0b3331bf42c7b7720f927c74f9f24b3c912f/treec685435b81b0dc339bc41d500a1c1a98514b6005 ordinary staging merge de8208a; exact parents7e9d932136e2d672b2afd01dbb7c088e76f3df16/297f0b3331bf42c7b7720f927c74f9f24b3c912f and tested tree independently read back. Required Actions38123161155/verify114421907364 passed original native TreeDX server/allSDK-language prerequisites and PostgreSQL supplements, then fresh2027API+200executingReviewer assertions (zero failed/skipped/todo) before838/838component steps. Executing Reviewer108f153b18896e62cd0fb7507c2fa78c4ffaec36 and native TreeDX6d358bb2e536af24918f3c33acb2072b9093a603 are exact existing workflow pins, not current managed invocation substitutes. All838 assertion receipts/184source-file digests and shipped schema/inventory assets matched testedmerge2ec60a443c3f548cab28452009d75f63e73fdac5. ReportSHA256e42d2bdfcd02019143840ed7b5766fdc3fc6a4f518b5805cc0a33849a59003ab; identical source/runtime CIarchive01f2f5ba6f628db21bca2bd0df7f333d8ddcc06fc768a4b0827e3f7db089066c. All4ZIPdigests verified. InitialFK23503fixture failure retained and corrected without changing constraint/watchdog/assertion. Latest metadata validation114435956773/AGPLauthorization114435956355/requiredverify passed before ordinary merge; protected head freshly fetched, exact body/readback checked, clean primary staging fast-forwarded, historical local main preserved, owned remote branch lease-deleted/absence verified.

Actual six-owner scripts-disabled production install and installed asset inspection passed using freshAPI297archive24e056fd70abdd82d7308c7f1f89fbaa73b782dac75ac49fd746fb921e48ad78; dependencies removed after immutable source/archive readback. Agent#404 and#405 mappings are integrated, but179 remains unchecked: original canonical Lease/Reservation producer and transactional lease semantics are still unproven. UsageSettlement already has its original producer and is not classified absent. SDK#393 retains the full checklist and independent SDK CLI-envelope defect/reopening; no managed campaign, release, tag, publication or deployment was performed.

Current strict acceptance checklist: treeseed-ai/sdk#401. Criterion169 API533's failed prerequisite run and unchanged retry are retained there and in its PR body; no passing claim or managed activation.

Native identical graph reconciliation delivered —2026-10-11 14:17:52UTC

API533 source45fc5516bf4b48a9742249a953e8a7f20db5c31f ordinarily merged to stagingaa3c237bfc14876dd7fb672be33b0d94a14341a1. Base de8208a/tested06cf357842ceae152afbdbd9b4a3c2ab81b6d436/tree4f715a8d1d2d46af66dbc2920ca4b2af36955b75; exact parents/tree/read-back verified. Verify38138452136 attempt2 passed fresh2027API+200Reviewer then838component steps, zero failed/skipped/todo. All838 assertion receipts/184 Git source digests/shipped assets audited; reportc3d06b477b734bb4890d5d3be286e5e6b16bb464e8322ae2f55c136ca59e6740, CIarchive01f2f5ba6f628db21bca2bd0df7f333d8ddcc06fc768a4b0827e3f7db089066c. Finalmetadata validate114490950576/AGPLauthorization114490950289 passed; strict protection preserved. Original attempt1 archive-install25s timeout/native artifact11702179990 retained; unchanged retry passed without deadline change. SceneZIP11705011754/packageZIP11704991789/sourceZIP11704832297/nativeZIP11705036788 remain Actions authority; full hashes in PR533 and current SDK401 checklist.

Original native classed Decision/governance case now compares seven authoritative SQL tables through independent connections and repeated/concurrent actual reconciliation against its original retained revision. Agent411 owns matching public preview/history/read-back assertions. Final six-owner current staging/source/actual installed plan byte-equality SHA64276f10148ddc227c699c068a64fed346f212a330a056e28a90a04c401423b8 closes criterion169 binding work; no managed SDK pass or readiness claimed. Local clean staging fast-forward; historical main/worktrees preserved; only own delivery branch removed. Native six-pair candidate94624b21 remains separate pending proof, not credited.

Current continuation SDK401:20completed/157open;111 delivered via Agent412/SDK403 with unchanged API533 runtime/native generic profile projector evidence. API534 original38146724925 failed before scenes:2027API passed,199/200Reviewer108 with production install ETIMEDOUT at original25s work budget. Failure/artifacts retained. Appenddef814a21bd8bef22f5d6cf9e52d4522725ecb86 consumes already delivered exactReviewer e60 production dependency closure without altered assertions/deadlines; fresh38149566833 runs all prerequisites/838steps.170 remains unresolved; no managed pass/readiness. Detailed receipts/checklist remain treeseed-ai/sdk#401 .

API534 replacement38149566833 failed before scenes:2025pass/2fail/0skip. Stale owning workflow assertion still expected Reviewer108 after e60 pin; my coupled-assertion omission is repaired by db1fa52. Actual install23423.222ms,pack776.492ms,ls390.562ms exhausted original25s before consumer. This latency remains failed/unproven; no budget/command/assertion relaxed. Cheap exact native archive/publication10/10 passed (install7704.940ms). New candidate requires fresh full CI. Criterion170 stays unresolved/outside177. Original failed jobs retained; owned local fixture processes/directories cleaned. Agent/SDK413/404 delivery and actual installed plan remain pending; currentstaging48mapped/156uncovered/204selected/260deferred unchanged.

Current2026-10-11 16:03Z:SDK401 checklist24completed/153open after113–116 native SDK404/Agent413 delivery; exact source/installed/staging plan52mapped/152uncovered/204selected/260deferred. API534 db1fa52 fresh38151785387 is still pending;170 remains unresolved and not counted in177. Failed38146724925/38149566833 retained; no managed pass. Full evidence: treeseed-ai/sdk#401 .

Current2026-10-11 16:47Z: SDK401 checklist25completed/152open; criterion20 delivered through Agent414 staging5440b5a658e854676e7916d2985ced3b63ce413d, fresh966Agent+200Reviewer→714component steps and exact actual archives/source/installed/staging plan53mapped/151uncovered/204selected/260deferred. API534 db1fa52 native38151785387 remains pending; original partial170 unproven/outside177. Current supported public reads:17healthy libraries,136raw definitions agree with independently read API inventories. Public proposals list returns0for15projects,1API,200SDK; no current17proposal freeze or capped SDK producer-completeness claim. Historical failures retained. Exact evidence/checklist: treeseed-ai/sdk#401 .

Original partial170 completed as binding work2026-10-11 16:53:25UTC: API534 ordinary staging5af63da12142c43083c216fca0ea6e048af85f6a/tree28b14b8cdd8e808e700cb153e18d4f4779c1a1fb matches tested mergedf5b4270c3c9f70afea475c3814f4ebe5ea4e078/source db1fa52. Required38151785387SUCCESS: fresh2027API+200Reviewer before838audited component steps and184nativeGit sourcefiles; native PG17.11 supplements3/17/28 pass. Source/installed/all-six-clean-staging planSHA76722a1c703e37054f00770f1ca7a95500b0bda2441b74b3e0d30882e5894579,53mapped/151uncovered/204selected/260deferred. Checklist25completed/152open unchanged;170 outside177, original partials11/12/184/192 remain. Final validate38157232122/authorization38157232097 passed before ordinary merge. Historical local main preserved; only delivery branch lease-deleted, absence verified. Failed38146724925/38149566833 retained; TreeDX native logs supplementary, strict managed reporting/launch remain unproven. Exact hashes/artifacts/semantic proof: treeseed-ai/sdk#401 .

Current mode custody delivery: API535 staging e4b50c2 and actual six-owner archive read-back passed. API536 candidate02bc00d38131ce14c496616824788efa1bf93cc8 repairs exact native Workday mode/parameters and raw-plan normalization after committed RED. Focused12/12 and strict/file checks pass; fresh Verify38173303094 pending. Agent418 dependent criterion4 also pending. SDK401 remains29/148; criterion4 unchecked, original failed observations retained, no managed campaign. Exact evidence: treeseed-ai/sdk#401 ; #536

2026-10-11 23:04:35UTC — API536 delivered; criterion4 complete

API536 source0e983f34e455d3b905042f9775f840b656bf560a, tested merge56251f1d18614b0edcdfa6f8bc321d15eb074b6d, ordinary staging9b7708b09b11e8ecfee06e4e0aac767b18a07dee/treee5076161db3db17fa4aee09b3527514e095e269d. Fresh protected heads/parents/tree read-back and clean staging FF passed; only this delivery's remote branch was lease-deleted. Verify38175982315: fresh complete2034API+200Reviewer assertions, zero fail/skip/todo/filter, before845component steps;845independent receipts across184native files; allsource digests/4selected archive assets match. Native PostgreSQL/TreeDX job prerequisites passed. Latest ready submission38182783208 and existing AGPL authorization38182783184 passed before merge. Archive SHA4f7e327983cadf5b524c0e36c481671de316101ff6590cecdf85df242ea6f147; report SHA8b8e99d1dedda6ac9b8d3f6b263e29fac145f6b7f4833b78ad776973bbccf070. Exact ZIP digests and original failures remain in SDK401.

Committed RED and original native case demonstrate single Workday mode/identity/parameters, raw native normalization denial and independently summed reservation-derived public totals. Real independent PostgreSQL observers, concurrent replay/denials and actual socket-end cleanup retain original failed history. Final focused13/13 and archive4/4 passed on unchanged deadlines. Failed38173303094, superseded38172770622 and submission failures remain preserved/uncredited.

Actual six-owner production-only/scripts-disabled archive installation pairs API536 with Agent419 and unchanged SDK405/CLI297/Deployment/Reviewer; existing native SDK override reused. Source/installed plan SHA5362876db1932672ebea7bf2626748fba37884ee7e5086dc7d72dd0bce3978b3 matches:59mapped/145uncovered/204selected/260deferred/464full. Installed mode guards29controlled denials, production tree, public CLI help, exact6source/staging/archive read-back and safe Deployment helper resolution passed. Diagnostic source-toolchain types are separate from actual production-installed execution. Receipts at /home/adrian/.cache/treeseed-native-verification/actual-six-owner-workday-mode-aidyuz7g; own node_modules/processes removed, all original artifacts/observations retained. Criterion4 complete; original177checklist31completed/146open. Compiled grants/remotes/provider instructions, current campaign authority, full binding readiness and managed SDK acceptance remain unproven. No SDK src change, managed scene/workday, release, tag, deployment, runtime selection or new worktree.

Criterion 50 implementation candidate — 2026-10-11 23:24:50 UTC; pending CI, no completion credit

Authority: the authorized strict plan and SDK #401; criterion 6e48b90ae52851e7b8fd728de8bb32610a60fc7c93dd445a93d3354aa00b652e. Held API base 9b7708b09b11e8ecfee06e4e0aac767b18a07dee; source candidate 653bfb133f715888e51ba212e8d48147022ad84b; intended remote PR branch codex/api-policy-custody-401.

Regression f6496a04 retained RED: nine existing assertions passed, one new assertion case failed on eight matching native/public policy contradictions. Native coverage committed in 7373ef80; 372be44f retained the legitimate slug-alias failure before correction. The final acceptance guard reuses the owning canonical alias resolver, binds the original native preflight receipt/digests/default revision/resolved policy, and compares original issued Workday authority without substituting later team defaults. Actual public preflight/start overrides preserve original team rows; version-checked replacement preserves the original Workday and start replay. Independent native PostgreSQL connections compare actual leased attempts, lease identity, reservation, counters/claims, graph rows, usage and ledger before/after policy replacement and stale-version denial. The original concurrency case and deadlines remain intact.

Local focused evidence: 21/21 policy/read-back/public-start unit/integration assertions plus 3/3 native PostgreSQL assertions, zero skips. The changed shipped assets and direct unit cases pass strict TypeScript. A broader native source graph reports the same 14 pre-existing diagnostics on held base and candidate; the compiler comparison retains exact diagnostic identities and demonstrates zero additions. File length/architecture and whitespace checks pass. Ten assertion references are added only to the existing component scene; normal SDK scene ordering is unchanged. No SDK source repair, managed campaign, publication, runtime selection or passing managed receipt. Disposable 512MiB PostgreSQL container removed and absence verified. Fresh full API/Reviewer suites and component receipts remain required in Actions before any completion credit.

Criterion 50 delivery candidates: API #537, source 653bfb133f715888e51ba212e8d48147022ad84b, tested merge 86efb046f39d90f4f6971e8bef2f428b3973aa6d, fresh Verify 38184186359 in progress; Agent #420, source dd5d54340db99ff948f1f83ea9acdd33af23bdfa, CI pending. Agent exact mapping regression RED 8/2, then 10/10 passed; strict assertion typecheck and file checks passed. Held source plan SHA256 894bdc98480a802a8a164f3618f84a41112645247b042215662ee216e3923f27: 60 mapped/144 uncovered; 204 selected/260 deferred/464 total retained with only uncovered-criterion diagnostics. This prospective mapping is not completion credit. Authoritative checklist remains 31 completed /146 open; criterion 50 stays unchecked. Original SDK scene remains 21 steps. No managed invocation; both disposable PostgreSQL checks cleaned their own containers.

2026-10-12 00:01 UTC — IMPLEMENTATION_DEFECT in the owning archive-inspection prerequisite: its unlocked dependency install could consume the fixed 25-second consumer watchdog. Retained failing API Verify 38184186359: 2038/2039 passed; no scenes. Repair 379c52661639180db9f1bf980232d69e49762ce0 preserves the original committed case and 25/30-second bounds, actual archive bytes, production-only/scripts-disabled install and scoped cleanup, and reuses the original dependency lock with npm offline cache. Offline without the lock failed ENOTCACHED; locked install 3.70s, archive suite 4/4 in 9.28s, real empty-cache denial 215ms; strict TypeScript and file checks passed. Fresh replacement Verify 38186223346 pending on merge a9718f1fe7fa19755b41a75287a18a788e3fef5d (tree 2963d8979ead277a312e6a8eece15d0040edee58, exact protected base 9b7708b09b11e8ecfee06e4e0aac767b18a07dee). Agent420 artifacts independently verified 989+200 tests/737 steps. Criterion50 unchecked, SDK40131/146. No managed campaign.

2026-10-12 01:16:27 UTC — criterion50 delivered; current checklist33completed/144open

API537 source379c52661639180db9f1bf980232d69e49762ce0/testedmergea9718f1fe7fa19755b41a75287a18a788e3fef5d/tree2963d8979ead277a312e6a8eece15d0040edee58 ordinarily merged to protected stagingceb6935ba0fef77093c94e2424cb618f498cf093. Fresh Verify38186223346 passed2039API+200executingReviewer assertions, zero failed/skipped/todo, before855componentsteps. Independently audited855receipts/187native Git source files/5shipped assets. ArchiveSHA72d3360e3bd30b71b1719df4823540fe55d073d118c3ef1c7f4e89a6e4dfbb9b; reportSHA7000b73c5d2e5b27a0d45916f7e4e13c3ac03e87fcf43699e3af0e1031c0f20f. Exact original artifact IDs/ZIPSHAs/complete command and failure history are retained in SDK401/Actions. Latest validate38191197400/authorization38191197420 passed after final metadata read-back and before ordinary merge. Fresh protected heads/parents/tree/protection verified; clean primary fast-forwarded; only owned codex/api-policy-custody-401 branch lease-deleted/absence verified, old local main retained.

Actual six-owner production-only/scripts-disabled install adopts this exact CI archive alongside delivered Agent420/SDK406 and unchanged CLI297/Deployment/Reviewer archives. Shipped original-policy guard passes35missing/changed authority denials with unchanged controlled public-producer data/installed bytes. Strict diagnostic TypeScript0errors; actual installed CLI help/production tree pass. All6archiveSHAs and candidate trees match clean protected staging; final source/installed plan bytes SHAe30ab7f5ca476107ebb75eaceccf92f236bc83d5b42e831f6cb09d7ddffdbf6a agree:61mapped/143uncovered/204selected/260deferred/464full, solely uncovered diagnostics. Full archive regular-file content equals the prior local candidate; distinct tgz SHAs retained. Original25s/30s watchdogs/assertions unchanged. Allowneddependenciesremoved, noownedprocesses remain; every failed observation, original watchdog/ENOTCACHED evidence and user resource retained. This completes50's executable binding; current campaign authority, SDK readiness and managed passing outcomes remain unproven. Hour24 MET; no campaign/release/tag/deployment.

Partial11 clock/native custody continuation: API #538, baseceb6935ba0fef77093c94e2424cb618f498cf093; held86ad181b58716e1a18f3a04d8aa52ba0b246e109; committedREDb1ac35c622c0057dc3bf73f313de37b3650164c4 before repair. Focused unit+independent native PostgreSQL6/6, no skips; existing component scene857expected. Fresh Verify38193390941 in progress. Full original command/digest/status and no-credit boundary in SDK401 and PR body. No SDK campaign; partial11 remains unproven. Original177 checklist33/144. Own disposable PostgreSQL/secrets removed; original failures retained.

Partial11 native/installed proof: API538 source86ad181b58716e1a18f3a04d8aa52ba0b246e109/testedmerge871b8f5f4ac5b7b663449ca03f5a038eb581964e/tree2b49429c43ba4617a7a9d452cd42d9587de60ce2. Verify38193390941SUCCESS; independent audit2041API+200Reviewer fresh complete assertions before857component steps, zero failures/skips/todos/blocked; all857receipts/187source digests/5archive assets reconcile. CIarchiveSHA4e60725e92c15a5c86b5a48de9b162e16b52605bceba530785dd6d87337ead27; reportSHA14053de49bc25de7fb1e3c8eef915835634542cdc412015dd04105ba404ebb00. Actual local packed/installed archive23f2c679175a10c4a3d1f492f65f15fdee7402fc55e5493939808e40cac5a512 compared withCI:all1658files/bytes/executable bits identical; compressed SHAs retained distinctly. Actual6ownerinstalledReviewer productiontsx helpers positive+5native/5publicdenials, source/installedplanSHA492a3120b3f52462deb43badb27f8cbd8ad59d3615d184add4c267854b1fab69 agrees61mapped/143uncovered/204selected/260deferred/464full. All8445installed-ownerfilesmatcharchives; temporarydependenciesremoved, noownprocesses. Agent421staged91e3cc9f7c84f97a066c87205c7a26f545360406. APIready; finalautomatedsubmissionchecks/stagingreadbackpending. Partial11stillopen; SDK401checklist33/144unchanged. Originalfailurespreserved; noSDKproductfix/campaign.

Final partial11 delivery: API538 merged staging9ea0acfb16a4855187d51163ffe3fc8bb8b247b4; originalbase+source parents and testedtree exact. Final validate38197494625/authorization38197494628 passed; verify/protections fresh before merge. Agent421 staged91e3cc9f7c84f97a066c87205c7a26f545360406. All6protected/source/archive trees and source/installedplan read back exactly; RED ancestry preserved. Both owned remote branches deleted; clean primary staging checkouts; dependencies/container/secrets cleaned. SDK401 records partial11 COMPLETE at2026-10-12T02:56:07Z, hour25MET; original177 checklist33/144, originalpartials2complete/3open, selectedsemantic57complete/147unresolved. SDK acceptance remains blocked; no managed pass.

SDK401 criterion118 path repair active: base9ea0acfb16a4855187d51163ffe3fc8bb8b247b4; RED9c7c839b(3/2/1),native/guardREDd3af66e0(17/15/2),repaird1b6478fa79a15a4ea737a3f72b344a196f1ab0a. Existing compiler/admission and managed native guard now enforce simulation Git writablePaths:['.']; production paths preserved. Focused20/20,changedstrict TypeScript/filepolicies/strictbuild/diffchecks passed. Full tsconfig diagnostic retained separately (existing broad errors plus new unknown-plan test diagnostic corrected using publicschema; no disabled checks). Fresh required CI and actual archive/staging proof pending;118remainsOPEN for full approvedbase/localrepository proof. No scene/campaign launched locally; SDKsrc unchanged. Current checklist36/141, semantic60/144; exact contract and failed evidence in treeseed-ai/sdk#401.

API540/Agent427:192done11:10:58;APIstage81148206;Verify38230021955:2048+200/858;archive8755fa25;8445installedfiles/6ownerplan/cleanup SDK401. Own branches deleted;primaryclean.37/140,63/141;12/118OPEN.188/190DONE;541d79c48c7/2050+200/860;9639cc6c;cleanup;treeseed-ai/sdk#408.

#545:f9fe9468;52open;SDK415
#547:159open

test(capacity): retain exact lifecycle metadata in original boundary …

test(capacity): preserve whole custody through permitted lifecycle ad…

test(capacity): narrow unknown public claim before exact canonical as…

test: require reuse of the same invocation packaged API archive (#515)

fix: reuse fresh inspected API archive within the same invocation (#515)

SDK exploratory source custody and canonical workday closeout repair #515

Description

Authorized strict acceptance implementation — 2026-10-09

2026-10-09 19:55 UTC — API fresh scene PASS; stop requested by human

2026-10-09 — API standalone chat producer delivered; native retry pending

Fresh exploratory SDK prerequisites — 2026-10-09 17:22 UTC

2026-10-09 — Fresh prerequisite invocation for standalone-chat repair (in progress)

2026-10-09 16:51 UTC — standalone chat source repair committed, API PR527 in full verification

2026-10-09 — new native SDK preflight failure: standalone chat lacks exact source context

2026-10-09 — team-lock repair delivered through main; temporary branch removed

2026-10-09 team-key lock delivery: staging merged; main verification running

Delivery update — 2026-10-09 03:49 UTC

2026-10-09 — native team-key lock regression/repair; delivery in progress

ALL seven fresh prerequisites verified; ready for ONE fresh exploratory SDK attempt — 2026-10-09 03:14 UTC

Fresh-start prerequisites and handoff delivery — 2026-10-09

Recovery handoff follow-up — API accounting remains exact; local provider custody loss unresolved

Provider consumer follow-up, no new accounting mutation

Actual approved operator dispute — 2026-10-09 00:48:12 UTC

Exact native verification complete — operator recovery candidate

2026-10-08 precise strict-check correction and approved operational preparation

Consumed dispute provider read repaired and pushed; fresh native delivery pending (2026-10-08)

Disputed consumed audit consumer regression reproduced; live mutation HELD (2026-10-08)

APPROVED retrospective dispute implemented; native focused25/25; delivery pending (2026-10-08)

Fresh local complete-suite failure; native Actions pending (2026-10-08)

Future unknown-time terminalization repair: test-first delivery PR524 (2026-10-08)

Unknown operator-action time: deadline zero-settlement regressions (2026-10-08)

2026-10-08 ACTUAL recovery DENIED; earlier "unsettled Reporter reservation" diagnosis corrected by native read-only evidence

2026-10-08 exact recovery candidate Actions and all component evidence PASS; live application pending

Complete current API suite PASS / live pre-recovery baseline

Approved recovery current candidate 2f442d1

Approved unresolved recovery — owning native counter/executor closure, 2026-10-08

2026-10-08 approved unresolved recovery — focused native15/15 PASS; not yet applied

Agent checked staging delivery, operator recovery in progress

Unresolved recovery test-first RED — approved contract

APPROVED: explicit unresolved-usage operator recovery (2026-10-08)

e615 owning workspace closed; operator financial recovery required — 2026-10-08

Live checked writeback applied; original cold-path regression verified — 2026-10-08

2026-10-08 native content execution-start regression and failed SDK closeout custody

SDK e615efe0 failed on exact signed sandbox ordinal; repair is Agent-owned

SDK exploratory invocation e615efe0 — rebuilt exact-scope Agent admitted; original native case running

2026-10-08 — Agent checked staging delivery; ALL7 fresh prerequisites complete; required provider rebuild running

2026-10-08 — API main promotion complete; fresh SDK retry prerequisites progressing

2026-10-08 — fresh prerequisites for repaired exact-scope SDK retry

2026-10-08 — exact-scope Agent whole-suite PASS and PR373; SDK failure retained

2026-10-08 — Agent exact-scope repair committed; failed SDK closed publicly, no passing replay

2026-10-08 — resumed SDK failed at exact repository context resolution; focused RED retained

Original exploratory SDK case started on fresh ALL7 candidates — 2026-10-08 18:54 UTC

Fresh ALL7 prerequisites complete; supported API lifecycle rebuild in progress — 2026-10-08

Checked host repair delivered to staging — 2026-10-08

Canonical lifecycle delivered to checked staging — 2026-10-08

2026-10-08 — retained sandbox physical closure independently verified

2026-10-08 — corrected fresh COMPLETE API suite PASS1989; prior checked repair merged to main

2026-10-08 — four original boundary oracles now PASS; fresh complete corrected candidate running

2026-10-08 — complete lifecycle suite retained FAIL; four original oracles corrected, focused retry running

2026-10-08 — canonical AssignmentAttempt lifecycle batch committed; fresh complete suite running

Canonical lifecycle batch — genuine REDs retained, 48 focused checks pass

Canonical terminal attempt lifecycle regression — test-first, not a golden pass

API repaired runtime and actual failed-run TreeDX closure readback

API checked staging delivery; SDK relaunch remains blocked

2026-10-08 — final required API verification and793 component cases PASS; checked delivery pending

Complete original suite PASS on byte-comparison candidate5c; remote proof still pending

Required CI fails original native watchdog; exact-byte assertion cost repaired, no bound change

Final corrected API candidate: complete native prerequisite PASS; remote verification pending

2026-10-08 — full held API1982/1982, then one genuine helper invariant regression fixed test-first

2026-10-08 — single native dependency hydration repair committed and checked delivery running

2026-10-08 — checked earlier repair promoted; new native dependency repair remains unverified

2026-10-08 — actual dependency-custody RED; native client/server adoption regression authored before manifest/workflow repair

2026-10-08 — checked TreeDX dependency adopted; SDK remains blocked pending fresh API and Deployment/cleanup proof

Checked API delivery, actual live readback, and new TreeDX scope regression

SDK retry prerequisites and cleanup regression — 2026-10-08 11:54 UTC

Checked SDK/Agent merges and CLI candidate-custody correction — acceptance remains open

2026-10-08 — Workday-scoped reader repairs committed; checked source repair merged

2026-10-08 — source and Reporter closeout repairs submitted for native verification

Checked repair and retained unreported closeout history — 2026-10-08

Operator stop genuine canonical closeout RED — 2026-10-08

Source-custody regression evidence — 2026-10-08

Authored focused source-custody regressions — execution pending

SDK exploratory source custody and workday closeout repair

SDK exploratory 57480afc — actual failed attempt; repair active

Test-first owning work

Approved recovery current candidate `2f442d1`