feat(runtime): expand outcome reconciliation compatibility - #153
Merged
0YHR0 merged 14 commits intoAug 21, 2026
Conversation
0YHR0
marked this pull request as ready for review
August 21, 2026 10:03
0YHR0
deleted the
agent/control-plane-runtime-a4-outcome-reconcile-compat
branch
August 21, 2026 10:03
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.
Scope
A4.1b.2a expand-only compatibility release for future managed Runtime outcome reconciliation.
RECONCILE_RUNTIME_*TaskResolution actionsRECONCILEDRollout / rollback
This PR must be merged and deployed before the writer slice. A clean 0048 -> 0047 downgrade is supported before writer activation. Once a later release persists the new values, 0048 is the schema floor and application rollback targets this compatibility release; audit evidence is never rewritten.
Validation
ruff check .passedtest_official_stdio_client_invokes_the_bundled_read_only_server); that isolated failure isWinError 5before child launchOut of scope
No A4.1b.2b command writer, authority mutation, deployment, or gate activation.