Skip to content

fix(state): implement AP076 explicit state ownership - #217

Merged
bordumb merged 5 commits into
mainfrom
codex/explicit-state-ownership-spec
Nov 10, 2026
Merged

bordumb merged 5 commits into
mainfrom
codex/explicit-state-ownership-spec

Conversation

@bordumb

@bordumb bordumb commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

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.

  • Approval sessions snapshot bound mutable inputs before provider calls, propagate cancellation, enforce deadline/usage guards and reject stale or substituted completions.
  • Telemetry flush callers share one batch result. Failures retain the exact batch; joined callers cannot trigger an implicit retry. Reentry and unwind fail closed.
  • TypeScript and Python SDKs share opening/closing generations, distinguish waiter cancellation from owned work, retain late attachments and unresolved cleanup, and expose explicit safe cleanup retry.
  • Submission and journal payloads use closed phases while preserving native entry authority and canonical mutation bytes.
  • Administrative recovery uses existing journals and generation/revocation floors. Exact resume, read-only recovery status, conservative credential retirement, and qualification recovery preserve uncertainty across interruption, competing operators and lost acknowledgements. AP-SPEC-077 defines the protocol and durability contract. Credential notes and collection output directly cut over to schema /2.
  • AGENTS.md now requires explicit state ownership, mutable-input ownership, competing-caller outcomes and durable recovery evidence. Maintained API, CLI, dependency, semantic and formal source records are updated atomically.

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 4a8ba4d9 Python 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.

Workflow Completed-head result
TypeScript SDK package Success
PostgreSQL lifecycle qualification Success
Python SDK package Success
SDK outcome recipes Success
Recipe qualification Success
Gateway operator package Success
Google read demo installed images Success
Gateway isolation Success
Stripe gateway demo Success
Airtable gateway demo Success
CI Success

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.

@bordumb
bordumb marked this pull request as ready for review November 10, 2026 18:04
@bordumb
bordumb merged commit e40bfdd into main Nov 10, 2026
114 of 115 checks passed
@bordumb
bordumb deleted the codex/explicit-state-ownership-spec branch November 11, 2026 00:40
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