Skip to content

chore(release): prepare v1.4.0 MCP expansion - #365

Merged
abruption merged 2 commits into
mainfrom
chore/release-1.4.0
Nov 2, 2026
Merged

abruption merged 2 commits into
mainfrom
chore/release-1.4.0

Conversation

@abruption

@abruption abruption commented Nov 2, 2026 •

Copy link
Copy Markdown
Owner

Summary

Prepare runtime v1.4.0 on the integrated MCP feature base f290973 (#361–#364).

  • Bump the source and generated standalone version to 1.4.0; add release preparation notes in English, Korean, Japanese and Simplified Chinese.
  • Clarify ordinary CLI JSON envelopes versus structured preflight/MCP projections, complete selector signatures, and preserve existing anchors. Date publication-status statements to the preparation checkpoint; retain historical release instructions.
  • Defensively reject native-result root fields in MCP preflight responses instead of ignoring contradictory evidence. The fixed producer does not emit these fields; this is defensive schema hardening, not a reproduced routing incident.
  • Honor an explicitly supplied internal POSIX invocation timeout while preserving the dynamically resolved default. Add regression coverage with an independent watchdog and a mutation check that fails when the override is ignored.

Refs #356, #357, #358, #359. This preparation does not close their remaining acceptance work automatically.

Validation

  • Documentation: 89 tests pass; generator consistency and git diff checks pass.
  • MCP integration on the final committed HEAD: 103 tests pass, 1 skipped. The ignored-timeout mutation fails as intended.
  • Distribution: 41 tests pass, 3 PowerShell skips.
  • Final committed source: two wheel/sdist builds compare reproducibly; archive contents/payload manifests and fresh, separate wheel and sdist core installations pass, including version/help and pip check.
  • Existing companion skill v0.4.1 snapshot remains byte-identical (SHA-256 fdf5697c04f4a37194986622afb3a7966bb02631c128cf18a323e3fbe5ae90ed). No frozen handoff contract or fixture change.

Independent review

Claude Code 2.1.314 (response-confirmed claude-opus-5-5) and Codex CLI 0.166.0 (default model; actual backend model identifier not exposed) independently reviewed the same frozen packets, non-interactively and read-only. Two rounds completed successfully. Findings were checked against source; document ambiguities, defensive preflight validation and timeout regression coverage were corrected. Final small fixture/doc refinements received local checks; they are not represented as a third paired CLI review.

At the user's request, Antigravity CLI 1.4.12 independently reviewed the document changes using requested gemini-3.8-flash-medium, medium, fresh plan+sandbox calls with no tools, network, tests or writes. Three rounds completed successfully (396.648s, 209.986s, 161.635s). Codex validated suggestions against source, fixed Korean candidate-label remnants and clarified the original baseline tool signatures. The second packet had a reported truncation in an unchanged Chinese tail; the final packet contains the complete changed regions of all 24 modified documents. The final round reported zero concrete defects. This is textual review, not native acceptance or publication evidence.

Final document packet: 119537 bytes, SHA-256 43f79cc30eaae2923f043c5a2c9059eb64aea589031597d2da78bd39c948b417. Second paired review packet: SHA-256 c8319778f8fd37d2cdb86062bf2147db8b2a01e9a7578b47cbf5b27abf4922b5.

Release boundaries

This PR prepares the release only. Merge, tag, release/workflow dispatch, PyPI publication and operations are separate gates. Current-head CI/review and final protected-main checks remain required; the base main CI is not substituted for them. No new live native, SSH, Windows, MDM, ACK or service verification is claimed.

The companion session has been sent the proposed skill 0.5.0 / minimum 0.9.1 / full coverage 1.4.0 scope, retaining codexBin floor 1.0.1. Queue submission is not consumption or approval. Final coverage requires actual runtime publication; skill approval/publication and exact published snapshot synchronization remain separate.

@abruption abruption added this to the v1.4.0 milestone Nov 2, 2026
@abruption abruption self-assigned this Nov 2, 2026
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-02T04:24:57.548504Z 1bea6cb PR opened
🔒 Security Review ✅ Completed 2026-11-02T04:25:16.800276Z 1bea6cb PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@abruption
abruption merged commit 476c67e into main Nov 2, 2026
44 checks passed
@abruption
abruption deleted the chore/release-1.4.0 branch November 2, 2026 04:29
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