Repository navigation
fix(state): implement AP076 explicit state ownership - #217
Merged
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.
Implement AP-SPEC-076 on merged PR #216 (
2fa22cc350956a82fe0e770d456f4455e58b6f6c). Workflows that previously inferred their phase from flags, optional values or pending callbacks now have one explicit transition owner.The dependency gate also required the official rmcp 3.9 model update. Unused server features are removed; newly exposed continuation fields are rejected and immediate MCP calls retain exact canonical bytes. See dependency repair.
Evidence and limits
Implementation/evidence map, AP-SPEC-076, and AP-SPEC-077 map A1–A6, B1–B4, C1–C7, D0–D4 and P1 to their transition/test owners. Source and installed-package tests exercise controlled completions, cancellation, cleanup retries and eager scheduling. Native file/TLS PostgreSQL tests retain decision, entry, receipt and counter checks. Process-termination matrices exercise installation and first/replacement qualification writes, synchronization, renames, restart, repeated commands and competing operators.
Process termination is evidence for the documented file synchronization model, not physical power-loss guarantees. This change grants no production qualification, provider entry authority, whole-repository audit claim or AP075 independent-review completion.
This final attestation supersedes provisional CI dispositions in the implementation record. In particular, the prior
4a8ba4d9Python workflow ended non-green because GitHub could not allocate a macOS runner; its executed jobs passed. Earlier revisions are not acceptance evidence for this head.Acceptance attestation
Accepted head:
5a3ecfb2d82c2a45abd3a0ec60d6e180afe9c996, based on merged PR #216 (2fa22cc350956a82fe0e770d456f4455e58b6f6c). Every required workflow completed successfully on this exact revision.The authoritative repository run passed the complete qualification interruption/repeat matrix, installation recovery, replay synchronization, competing imports, and generated CLI fixtures. Kani, translation, and clean authoritative Lean passed; the Lean audit covers 329 compiled statements under the existing assurance scope.
Python's 26 jobs all passed. Only its unallocated CPython 3.10 macOS job was retried; successful jobs were retained. The five protected production-qualification stages are intentionally not invoked by this PR event, consistent with the limits above. No required engineering check is failed, pending, cancelled, or bypassed.