[adrianwebb]

Outcome

Repair two observed shared-backend blockers in the same portfolio workflow: discover dependencies from the exact published library commit, and acknowledge already-settled native TreeDX report closeouts without requiring a sandbox that was never acquired.

Work authority

• Work item / Issue: Complete accounting transition observations for strict Agent acceptance #553; live portfolio evidence Keep Atlas detail headers usable with real long identifiers ui#70
• Proposal / decision: Integrator recovery for accepted UI9787d8e9-267a-46db-8151-a8b340352e2d v3 / Decision3069ee63-5fa0-48f2-ba24-4e1bd8a0aa62 and Admina309d6bf-1a49-47cb-92de-238230906ac3 v9 / Decision694f53b0-b0d4-4ca9-91d7-8bc632554192.
• Assignment / checkpoint: Integrator blocker repair, no agent assignment or estimate claimed. Published note operationff7566ae-f80f-4473-b210-0f771f5aecb3.
• Actor: Codex integrating assistant
• Human authority: @adrianwebb, standing authority to repair blockers in small slices
• Agent / capacity provider: Integrator implementation; no TreeSeed agent delivery credit.
• Exact base ref: staging 855f483
• Exact head ref: codex/pin-published-graph553 0b8e3d2

Contributor mode (select one):

• Human-authored
• Agent-assisted under human authority
• Agent-authored under human authority

Plan

This follows merged #588. Protected staging requires an up-to-date branch; merge a1c24f4 incorporates staging855 with a byte-identical tree to locally proven9e38. Required Actions must pass on the updated head before merge. Reproduce the moving-ref discrepancy, pin through existing authority, run focused checks/build, adopt locally and read the real graph, then complete Actions and release.

Changes and commits

Commit9e38e24a3ff48c2605385c3fbcc4bf94fb48fd57 resolves the bound ref with listRepositoryPaths, validates the exact commit, and uses the existing exact-ref grant before querying the graph. Returned graph commit, endpoints, note bytes, digest and all existing checks remain enforced. No schema, additional executor or compatibility path.

The regression returns no graph nodes for the moving ref and the actual relation for its exact commit. Existing signed HTTP fault cases also cover the path-list boundary.

Verification

• New stale-moving-ref regression fails on696bb97fd81eb7a408bc6bbcd8344e7fb1f200a6.
• After fixture mock correction,16 focused relation tests pass across3 files. The initial4 mock setup failures are retained locally.
• Strict build and git diff --check pass.
• Local candidate adopted using supported dev rebuild; no release success is claimed.
• Real backend execution.reconcile produced graph revision82707 and edge_gJ_sby084Tq7GArzzynw7_yyzQWGG7nd, provenance treedx-link, from UI v3 reviewing node_oOyC5ztF2ampzVQ_7elFzKqAX-fQbuXi to Admin v9 acting node_B7yArVnpeWl-CxtGeeBb4_-FieCcmCKb. Source note notes/real-workday-picker-ui-to-admin.mdx at56f6c8764d419cc23a790a94d4a7b7fcfd4b7e12, digest sha256:0e8cd88b554f1e7a05633692dc9faeefc8c8ed47ac8d0543ff25f39ddfdb1387.
• Both nodes were stale at that read-back: this proves dependency discovery, not blocked-admission, implementation, review or release success.
• Approved UI acting workday workday-94b8eebe-d064-4cf2-9d58-341e3984bb1b subsequently admitted and Engineer assignment_XVN3cqRxnce8NmaQTMCqYpV5s-YMqFn7 claimed. Admin remains unadmitted pending the real reviewed UI product.

Focused command: node node_modules/vitest/vitest.mjs run --config vitest.control-plane.config.ts tests/unit/control-plane/capacity/execution/graph/architecture/relations tests/unit/control-plane/capacity/execution/graph/relations/exact-dependency-links.test.ts. Build: npm run build:dist. Controlled HTTP fixture checks are not full native acceptance. Required Actions remain pending; no broad local acceptance campaign claimed.

• I ran the narrowest relevant package verification and documented any checks that could not be run.

Risk and rollback

Path-list or exact-ref authorization failures remain fail-closed. No migration. Revert9e38e24a3ff48c2605385c3fbcc4bf94fb48fd57 and rebuild/reselect696bb97fd81eb7a408bc6bbcd8344e7fb1f200a6 to restore the first slice; preserve original failed observations and published note.

Completion summary

The local dependency-discovery repair is proven with the actual published portfolio note. Actions, upstream merge, release and the complete cross-project implementation/review/simulated-release outcome remain pending.

AGPL committer authorization

The existing base-owned authorization check applies; no licensing change.

Submission checklist

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

Additional real recovery blocker in this candidate

Agent#506 was adopted through the supported provider handoff and freed two native Reporter slots as unresolved while retaining original outputs/period holds. The other two (JGg/HX) reached API acknowledgement and failed its identical sandbox/native.elapsedSeconds assumptions. Public capacity ledger/usage inspection confirms original provider_usage_report settlements already committed once: JG11active/11elapsed, HX10/10, nativeUsage{}; they are not automatic zero settlements or unmeasured charges. Operator unresolved recovery correctly refuses those measured consumed reservations. Do not weaken or change that accounting rule.

Commit0b8e3d2066e3f5010ff6a79a8c1ea4a08b855f74 extends the existing failure acknowledgement for native TreeDX content with no sandbox/environment/guest artifacts. It reuses validateAssignmentResultCompletion for exact original workspace/reference/time authority, preserves all VM receipt rules, and requires an already-consumed reservation before native acknowledgement. The existing full original-scope, ledger/usage, exact-result replay, state-version and event checks still run. Native elapsed is not invented; the canonical integer elapsed must match the already-settled authoritative usage. The expired attempt remains unsuccessful and assignmentResult remainsnull. No extra settlement, refund, new schema or handler-specific policy is added.

Real-shape regression RED at the original sandbox guard (after correcting one test-fixture SQL quoting error).34 cases across terminal-races and3 relation files now pass, including actual owning embedded PostgreSQL service transactions and negative native output/reference/counter cases; strict package build and diff check pass. Controlled clock/content references are test inputs, not real TreeDX/server/physical proof. Live native acknowledgement and independent report read-back remain pending. No full local acceptance campaign claimed.

This small owning API correction is batched into the current runtime candidate rather than creating another competing long verification candidate. Work authority extends to treeseed-ai/agent#496 and the user's explicit retained-claim instruction. The prior9e38/a1c24 observations and required runs remain historical evidence; new required Actions must pass on exact0b8e3d20 before merge. Candidate adoption will wait for active assignment leases to close.

Live adoption at exact0b8e3d20 succeeded through trsd. JG/HX native Reporter closeout acknowledgments released their retained leases while preserving original expired disposition, null canonical assignmentResult, and exactly one original11/10second ledger charge each. Original report files read back at retained commits/hashes. Together with Agent/Deployment fixes, all four October21 claims release concurrency; h5t/5y remain unresolved accounting holds. UI admission now exposes a distinct graph/result revision mismatch tracked in API#590, not a regression in native accounting. Required Verify39663702132 remains pending; no release/formal acceptance claim.