Repository navigation
selected-window: declare contract revision 1.3 (EN-115 completeness) - #410
Closed
luisleo526 wants to merge 6 commits into
Closed
luisleo526 wants to merge 6 commits into
luisleo526 wants to merge 6 commits into
Conversation
…n (EN-115)
Red-first step for the EN-115 declaration flip: the selected-window tests now
expect CONTRACT_REVISIONS == ("1.3",), the probe to print ["1.3"] and no
"1.3-parity" literal, and the AST guard to pin one "1.3" string while refusing
("1.3-parity",), ("1.3", "1.3-parity") and ("1.3-parity", "1.3").
On this commit's code the module still declares ("1.3-parity",), so these
expectations fail for the intended reason.
Co-Authored-By: Claude Code <[email protected]>
…teness proof
Flip CONTRACT_REVISIONS to ("1.3",) and carry the same declaration through the
module and capabilities_record prose, the report-schema and public-contract
pages, the README and docker README capability tables, and a CHANGELOG
Unreleased entry.
A build with the section-4 producers and manifest declares 1.3 and never
1.3-parity; a parity build declares 1.3-parity and never 1.3; a tuple holding
both is invalid. No request, report_window, phase record or fingerprint member
carries the literal, and no wire, phase, fingerprint/schema or ABI version
changes.
Green step for the red-first test commit before it.
Co-Authored-By: Claude Code <[email protected]>
Merge origin/main (f37c8b5, v1.6.1) into core/en115-declare-1.3 by merge, not by rebasing pushed commits. Keep main's 1.6.1 entry and its "1.3-parity" prose as history, and put the EN-115 declaration under 1.6.2 (Unreleased) in CHANGELOG.md, README.md, docker/README.md, docs/pages/public-contract.md and docs/pages/report-schema.md. No code or test change. Co-Authored-By: Claude Code <[email protected]>
Comment only: the selected-window route controls still name "the 1.3-parity capabilities literal" although the image declares 1.3. No test reads it and no code changes. Co-Authored-By: Claude Code <[email protected]>
L6 ruled that the hub image for 1.6.1 is not published: a Debian security update changed the source set after the tag, so v1.6.1 has no image and no GitHub Release, and engine, codegen and HPO 1.6.1 are released as source/packages. Reword every "1.6.1 image declared" claim in the EN-115 prose: the published images up to 1.6.0 declared 1.3-parity, engine 1.6.1 (released, no hub image) declares it too, and from 1.6.2 the image declares 1.3. Prose only; no code or test change. Co-Authored-By: Claude Code <[email protected]>
F5c: correct the F5b clause in the five EN-115 prose places to the history the tags carry: v1.5.0 declares 1.3-parity (v1.4.0 has no revision member), v1.6.0 declares 1.3 without a completeness proof, engine 1.6.1 (released, no hub image) declares 1.3-parity, and from 1.6.2 the image declares 1.3 with the completeness proof. F5d: reword the two inherited 1.6.1 sentences (README.md, docker/README.md) so no file claims a 1.6.1 image: "Engine 1.6.1 (released without a hub image) declares ...". Prose only; no code or test change. Co-Authored-By: Claude Code <[email protected]>
Collaborator
Author
luisleo526
added a commit
that referenced
this pull request
Oct 19, 2026
…teness proof (1.6.2) (#412) 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]>
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.
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