feat: add managed agent integration lifecycle - #104
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Boundaries
The per-tool baseline recognizes a cooperative pair of exact prior bytes. It
does not authenticate historical origin or permit overwriting local edits.
New generation-2 terminal receipts bind the desired-state identity; the old
binary must reject them without mutation even after the transaction completes.
Legacy receipts remain readable historical evidence but cannot authorize an
apply replay. Recovery preserves the original terminal outcome.
Operational observation failures remain operation errors, not semantic recovery
packets. Cancellation, rollback, cleanup and durability outcomes retain their
native meaning through both JSON/text CLI projections and exit codes.
Verification
The final committed candidate
4e8d227ff97ca28ced33da6cc638c0f45232306epassed
npm run checkwith the pinned npm 12.0.2 toolchain, including the fullGo suite, static checks, 93 browser tests across Chromium/Firefox/WebKit,
package/wheel verification, command-oracle/coverage and release closeout.
Committed-range
git diff --checkpassed and the worktree remained clean.Exact-head GitHub checks are a separate merge prerequisite, not yet claimed.
Additional evidence includes transaction/integration/adoption race tests on
the unchanged runtime, nine causally isolated semantic mutants, the actual
published predecessor across six pending/terminal recovery cases, and isolated
native Codex/Claude present/absent/altered-skill controls. Each native-host
record retains the source and binary identity actually executed. The final
test-only repair independently kills the update-byte-guard mutant for both
tools and admits the real CLI positive control.
Independent reviews cover owner boundaries, state transitions, CLI/error
projection, proof inventories and oracle independence. No-finding results are
bounded review observations, not a claim of universal defect freedom.
Non-Claims
This pull request does not establish publication, consumer rollout, production
readiness, authenticated baseline ownership, revocation of an already loaded
skill, or support for arbitrary native agent hosts. Browser redesign and source
codec selection remain separate roadmap phases. Design and implementation
working documents remain outside the repository.