Skip to content

Adopt public v2 supervised launch contracts - #1970

Draft
ViperJuice wants to merge 35 commits into
mainfrom
t3/v12-closeout
Draft

ViperJuice wants to merge 35 commits into
mainfrom
t3/v12-closeout

Conversation

@ViperJuice

@ViperJuice ViperJuice commented Nov 9, 2026 •

Copy link
Copy Markdown
Collaborator

Implement the pinned public v2 envelope through held operator/controller snapshots, passive binding verification, captured launch admission and the bounded supervised worker. Preserve exact RFC 8785 caller-context echoes outside JOURNAL and map results to the pinned status schema. Production selects only the passwd-home operator binding and refuses before launch until its independent inputs are provisioned.

Historical receipts and uv.lock remain unchanged. CLOSEOUT carries separate observed metadata and retains false byte-pin authority. EC-CLOSEOUT acceptance stays blocked on independently owned producer evidence under C-S4; installed-provider qualification and live use remain separate.

Validation on ai: the complete named V0–V3 producer union passed 2,291 tests, with one explicitly unavailable optional xdist check and only the exact post-stamp consumer deselected. Then the unchanged stamp tool ran on CLOSEOUT only, followed by 58 passing V3/receipt-consumer tests. Required inventories and targeted Ruff passed. The refreshed installed-wheel sparse-tree check passed 702 tests with nine expected source-workflow-only skips, including the current receipt consumer. JUnit and logs are retained on dev0. No Gate A or live-provider run was dispatched.

The earlier hosted failures were reconciled: the offline fake-provider fixture now uses the fixed system interpreter; direct intake consumption remains confined to its approved modules; the completed receipt supplies the previously missing consumer input. The preserved deep-JSON test identity is supported by bounded metadata without renaming historical nodes. Hosted checks and independent implementation reviews remain pending; this PR stays draft.


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

Current evidence distinguishes 51 case-specific obligation rows from 67 family witnesses; family witnesses supply no obligation-level acceptance claim. Historical assessments become inapplicable on changed content without making later suites fail. Unexpected worker-boundary errors retain closed diagnostics and admission cleanup. Hosted required-check authentication remains fail-closed, including unfinished checks sharing the same run ID.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant