Repository navigation
selected-window: declare contract revision 1.3 with the EN-115 completeness proof (1.6.2) - #412
Merged
Merged
Conversation
…teness proof (1.6.2) Reverts the declaration of b148979 ("selected window: declare 1.3-parity, not 1.3, until a completeness proof exists (1.6.1)", #401) now that the EN-115 completeness proof exists: `run_json.py --capabilities-json` declares `["1.3"]` again for a supported runtime and `[]` otherwise, and 1.3-parity stays the parity build's literal (a tuple holding both is refused). Docs: README.md, docker/README.md, docs/pages/public-contract.md and docs/pages/report-schema.md restore "is `["1.3"]` when the runtime supports selected windows" and replace b148979's sentence "From 1.6.1 (unreleased), the image declares `1.3-parity` instead" with the per-version history: 1.5.0 and engine 1.6.1 (released without a hub image) declare 1.3-parity, the published 1.6.0 image declared 1.3, and from 1.6.2 the image declares 1.3 with the proof. CHANGELOG: an Unreleased entry above main's 1.6.1 entry. Tests (red first on the parity literal): tests/test_run_json_selected_window.py, the literal-once and mutation guards; tests/test_selected_window_routes.cpp comment. Replaces PR #410 (same tree; one commit so check_doc_reverts can see the naming of b148979 on the commit that changes its text). Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Brings in the three CI-only commits that landed after the 1.6.1 final (#415, #420, #439): workflows, docs/ci.md and ci_preflight. No file of this branch's eight is touched by them; the merge is clean and changes none of the EN-115 declaration, its tests or its prose. A merge commit on purpose: the branch is pushed, so its history is not rewritten. Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
luisleo526
added a commit
that referenced
this pull request
Oct 19, 2026
Engine main moved after this branch was cut (#412, the EN-115 declaration, and the CI commits before it). promote-baseline.yml is untouched by those commits; the merge is clean and changes only what main brings. A merge commit, no rebase, so the commit CORE-TOP already pushed (aafab8f) stays an ancestor. Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
This was referenced Oct 19, 2026
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.
Replaces #410: the same tree, in one commit. #410's per-commit history failed
check_doc_revertsbecause its commits revert b148979's (#401) 1.3-parity sentences without naming it (lab rj-20261018t070209-5ac5af: release, debug, sanitizers, kernel and docs passed; preflight failed on doc-reverts only). That history is pushed, so it isn't rewritten.CR-139 EN-115, lane L1 (schedule A, 1.6.2 patch).
HOLD: draft until (1) the 1.6.1 final is tagged tonight (this must not ride 1.6.1), (2) the EN-115 L3 gating read passes, and (3) the engine and kit proof boxes are green. It is then cut as 1.6.2-rc.1, before any CR-150 feature commit lands on main (semver rule).
🤖 Generated with Claude Code