feat: complete Codex projection, runtime ownership and platform packages - #4
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.
Summary
Codex 0.3.0 exposes all 96 SDK-adopted stable App Server requests as typed MCP tools and retains 51 experimental methods through the explicit experimental path. swift-codex owns schemas, generated bindings and adoption metadata; this plugin derives its projection and applies host-specific risk and lifecycle policy.
Native threads, turns, requests and Exec sessions retain their original host invocation and runtime ownership. The adapter adds metadata-first history pages, safe writer handoff, exact JSON integers, generic Host Services integration and native Windows process/IPC support. Platform archives include declared entrypoints, verified runtime dependencies and provenance receipts; the vendor Codex executable and credentials remain user-owned.
Retained events preserve typed token-use and Goal counters while recursively redacting credentials, including API-key fields. Complete protocol payloads remain distinct from bounded diagnostic/event views.
Validation
4b922678370025d222220d767a88bcd38fbad65cpins swift-codex 0.4.1 and MCP 0.13.1-computer-mcp.1. All schema declaration bytes remain SDK-derived; only the provenance receipt changes.95c86760167ad9da3bc269b2968fb553a2b81ac6strengthens the startup deadline check for cooperative and forced cleanup: actual protocol/supervisor/process-group absence, confirmed cleanup and zero retained work. A fixture directory removed by an EXIT trap is not a valid live-process ownership assertion after SIGKILL. The unchanged runtime passes the full suite and five two-case repetitions; all existing deadlines and cleanup guards remain.Delivery boundary
Source promotion is authorized. Final package acceptance and Microsoft runtime redistribution eligibility remain required for public platform delivery. Vendor binaries and credentials remain user-owned. Windows scope is the native adapter and required SDK chain; it does not add a Windows Computer MCP desktop App. No published release or existing user App Server is replaced.