Ship native CLI observation assets through the public binary

[adrianwebb]

Outcome

CLI archives retain the selected native workday event and diagnostic acceptance assets. Both original cases execute the package's declared compiled public binary, preserve denied reads and unchanged retries, and no longer invoke checkout source or substitute an unbound command.

Work authority

• Work item / Issue: Current cli backlog: retained requirements after issue consolidation #274; continuation Complete strict SDK capacity-provider and agent acceptance bindings sdk#387
• Proposal / decision: User-approved strict capacity-provider and agent-execution implementation plan; bounded installed-owner custody repair.
• Assignment / checkpoint: CLI packaging and selected public-boundary lane; managed SDK launch remains blocked.
• Actor: Codex
• Human authority: @adrianwebb, explicit implementation authorization in the shared workspace.
• Agent / capacity provider: Codex / existing configured provider; no simulated agent execution claimed.
• Exact base ref: staging 63c7928b2ab2456e495a0e55572b9a47d379315c
• Exact head ref: codex/installed-observation-assets-274 5a73cd434a42f237543d30c8b8c7bd5e912ab173

Contributor mode (select one):

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

Plan

Ship the minimum existing native observation closure; preserve independent CLI builds, exact public commands, original native assertions and 30-second deadlines. Run complete owner verification and fresh full prerequisites before component scenes, then ordinary staging merge/read-back after all required checks pass. Installed six-owner acceptance and managed SDK semantics remain separate unresolved gates.

Changes and commits

• 2f0d5a2: focused regressions reproduce archive omissions, installed missing assets, and checkout source execution.
• 5a73cd434a42f237543d30c8b8c7bd5e912ab173: ship existing metadata/guarantees and minimum assets; move the two native cases intact into acceptance assets, import existing compiled runtime contracts, resolve the sole public binary, and update full-suite discovery/registry paths together.
• Convert the existing synthetic OS fixture to TypeScript and update its owning runner/workflow tests. Child subprocesses use the explicitly resolved loader and shipped fixture. The fixture remains component-only evidence; no genuine credential-custody claim.
• Actual CLI, SDK and Identity archives install with production dependencies and scripts disabled. Native proof checks exact archive/asset bytes, strict dependency tree and public binary execution without checkout source or development dependencies. No runtime dependency or product behavior added.

Verification

Focused source command: node --import tsx --import ./tests/support/os-custody.ts --test tests/contract/package/installed-assets.test.ts tests/acceptance/workday-events.test.ts tests/unit/command-boundary/observation/workday-events.test.ts tests/unit/native-suite-reporting.test.ts tests/integration/native-suite-reporting.test.ts tests/contract/package/thin-package.test.ts: 22/22 passed, zero failed/skipped/todo. Strict TypeScript checks for the three new/converted assets and original file architecture/length checks passed, under Node 24.12.0.

Local npm run verify:direct failed at the original strict SBOM gate before tests/scenes because the retained local dependency tree lacks development dependencies; exact log and failure classification are retained in the Issues. No gate weakened. Complete TREESEED_DEVELOPMENT_WORKSPACE_ROOT=/tmp/sdk369-platform-authority-de2LzF npm test on this exact candidate passed 369/369 under Node 24.12.0, zero failed/skipped/todo, in 120.1 seconds; /tmp/cli274-installed-assets-full-suite-20261010.log. Clean Actions 38007844944 passed npm run verify:direct with 369/369, then freshly ran all 369 before 168 component scene steps on tested merge 8d0919a04c66e911e27a6521519f6c4381fda7c5 (tree 837b887bc913a554513f43e48df0eb437815b138). All applicable checks passed. Prerequisite source digest 723a1ba4a6c99bc3c116e9ed18aa5fd01b94f8cc82d4eb2c113364fb00335c08; scene report SHA256 60ff6ae6765c91999f808d73eaa1731880859e722f7dc8ca5173e45321f05865. Scene artifact 11652440908 ZIP SHA256 686ce582aa857b70aabb920c140077cb3e9f658018210c009c1e0b30b42fe3b9; package artifact 11651976465 ZIP SHA256 1f977558be3b4d7bf0a8d8f8eb0a71abea88daca1541b1143720edb406dd9dbf. Existing component reporting is not a strict managed SDK receipt.

Risk and rollback

No API, schema, runtime command, license, deployment or infrastructure change. Native HTTP responses and OS fixture credentials are controlled test inputs, not managed model/API authorization evidence. Actual joined production-owner installed execution remains unproven. Roll back by an ordinary revert of the repair commit through a checked staging PR; preserve the regression commit and failed observations.

Completion summary

Focused archive/public-binary proof passes. The complete local suite passed 369/369. Clean Actions run https://github.com/treeseed-ai/cli/actions/runs/38007844944 passed full verification and fresh complete prerequisites before all 168 component steps. Ordinary staging merge/read-back is next. No managed acceptance campaign, runtime selection, tag or release was created.

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.

Delivered by ordinary staging merge 22b6a27136a3583f4128cfd763917371e5572985; exact tree 837b887bc913a554513f43e48df0eb437815b138 matches the tested merge. Source ancestry, clean local fast-forward and exact temporary remote branch deletion independently verified; main unchanged. Component scope only; joined installed and managed SDK proof remain pending.