Integration: TUI version and docs contracts on release stack - #10264
Integration: TUI version and docs contracts on release stack#10264lawrencecchen wants to merge 4 commits into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Version consistency evidence for exact head
No tag, publish, or merge action was performed. |
|
Correction to the evidence comment above: the full run covered five binary artifact builds, Windows GNU plus x86_64/aarch64 Apple and x86_64/aarch64 Linux musl. All five passed. |
Final integrated candidate
This dependent draft layers the version identity red/green pair from PR 10251 and the frontend protocol documentation red/green pair from PR 10260 onto PR 10261, which already carries the PR 10258 TUI SDK validation stack and SDK release policy fixes from PRs 10245 and 10250.
Base head:
74a9aef90a0196f2cd8bece7f1ae79647d79ecb9.Candidate head:
9dd3c77aab.Preserved red/green history
56a8991d10(red),3cd80a1479(green).f2d9663b25(red),9dd3c77aab(green).Original PR branches and PR10261 remain unchanged. No merge or release action is requested.
Local evidence
Frontend docs behavior test, TUI spec/schema/resource checks, generated SDK drift check, Python compilation, and
git diff --checkpass. Hosted SDK and spec checks are dispatched for this exact head.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Summary by cubic
Unifies
cmux-tuibinary version identity under one canonical distribution stamp and enforces frontend protocol docs against the supported wire API. Previouslycmux-tui --versionandremote-probemixed the Cargo crate version with a distribution stamp; now both report the same canonical distribution version, and README claims align to protocol v12.DISTRIBUTION_VERSIONincmux-tui-coreand uses it in--versionoutput andremote-probeJSON (versionanddistribution_versionare identical)..githubworkflows to stampCMUX_TUI_DISTRIBUTION_VERSIONfrom a singleversioninput and to validate:--versionoutput starts withcmux <version>(npm prerelease is the canonical nightly stamp).remote-probe --jsonbuild_identity,version, anddistribution_versionmatch the expected head and stamp.cmux-tui/scripts/test_frontend_docs.pyand runs it in the spec workflow to keep README protocol references in sync with the supported WebSocket protocol and the raw protocol guide; updates READMEs to v12.versionto the reusable build workflow; PyPI nightlies may use.dev...as metadata only—the binaries stay stamped with the npm value.Written for commit 9dd3c77. Summary will update on new commits.