Skip to content

Commit 5f1cf67

Browse files
luisleo526claude
andcommitted
selected-window: declare contract revision 1.3 with the EN-115 completeness 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]>
1 parent 433f945 commit 5f1cf67

6 files changed

Lines changed: 56 additions & 33 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,16 @@ version number follows semantic versioning over the surfaces the
77

88
## Unreleased
99

10+
- **EN-115 selected-window completeness proof completed.** The image declares
11+
selected-window contract revision `1.3` again: the section-4 producers and
12+
manifest are present, `value_ownership` is `complete`, and a revision `1.3`
13+
pairs only with a `complete` receipt. The `docker/run_json.py
14+
--capabilities-json` probe reports
15+
`capabilities.selected_window_contract_revisions` as `["1.3"]` on a
16+
supported runtime and `[]` otherwise; `1.3-parity` remains the parity
17+
build's literal, and a tuple holding both is invalid. No wire or ABI change:
18+
the selected-window wire version stays 1, the phase version 1 and the
19+
fingerprint/schema version 2.
1020
- `scripts/ci_preflight.py` runs `verifier-tests` (`scripts/test_ci_verify.py`) across parallel `unittest` subprocess shards with per-shard `TMPDIR` isolation via `scripts/run_unittest_shards.py` (`scripts/test_run_unittest_shards.py`).
1121

1222
## 1.6.1-rc.1 — 2026-10-17

‎README.md‎

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -45,18 +45,21 @@ The [release notes](CHANGELOG.md#160--2026-10-17) cover typed failures across
4545
source values, engine arithmetic and report production, finite trade and
4646
summary doubles, and the documentation, test, CI and benchmark updates since
4747
1.5.0; in [1.6.1 (unreleased)](CHANGELOG.md#161-rc1--2026-10-17) the selected-window
48-
contract revision is `1.3-parity` rather than `1.3`.
48+
contract revision is `1.3` again, now with the EN-115 completeness proof.
4949
For the 1.6.0 pair, regenerate strategy C++ and relink against that pair's
5050
headers and archive. Published 1.3.0 download and installation examples below
5151
remain pinned to that earlier pair.
5252

5353
From 1.6.1 (unreleased), the engine/codegen image advertises selected-window
54-
contract revision `1.3-parity` through `docker/run_json.py --capabilities-json`:
55-
it emits the four typed codes (`strategy_value_invalid`,
54+
contract revision `1.3` through `docker/run_json.py --capabilities-json`:
55+
with the section-4 producers and manifest present and value ownership
56+
`complete` (EN-115), it emits the four typed codes (`strategy_value_invalid`,
5657
`engine_command_value_invalid`, `report_result_invalid` and
57-
`report_post_execution_failed`), with parity with the 1.4.0 reference on tested
58-
cases, and no completeness claim (the published 1.6.0 image declares `1.3`).
59-
`capabilities.selected_window_contract_revisions` is `["1.3-parity"]` when the
58+
`report_post_execution_failed`). A build declaring `1.3` pairs only with a
59+
`complete` receipt; `1.3-parity` remains the parity build's literal, and a
60+
tuple holding both is invalid (the published 1.6.0 image declared `1.3`
61+
without that proof).
62+
`capabilities.selected_window_contract_revisions` is `["1.3"]` when the
6063
runtime supports selected windows and `[]` otherwise; see the
6164
[capability table](docker/README.md#selected-window-contract-revision) and
6265
[report schema](docs/pages/report-schema.md).

‎docker/README.md‎

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -269,16 +269,18 @@ docker run --rm \
269269
### Selected-window contract revision
270270

271271
From 1.6.1 (unreleased), the engine/codegen image's `run_json.py --so
272-
<strategy.so> --capabilities-json` probe declares revision `1.3-parity`: it
273-
emits the four typed codes (`strategy_value_invalid`,
272+
<strategy.so> --capabilities-json` probe declares revision `1.3`: with the
273+
section-4 producers and manifest present and value ownership `complete`
274+
(EN-115), it emits the four typed codes (`strategy_value_invalid`,
274275
`engine_command_value_invalid`, `report_result_invalid` and
275-
`report_post_execution_failed`), with value parity with the 1.4.0 reference on
276-
tested cases, and no completeness claim (the published 1.6.0 image declares
277-
`1.3`).
276+
`report_post_execution_failed`). A build declaring `1.3` pairs only with a
277+
`complete` receipt; `1.3-parity` remains the parity build's literal, and a
278+
tuple holding both is invalid (the published 1.6.0 image declared `1.3`
279+
without that proof).
278280

279281
| Capability member | Supported runtime | Unsupported runtime |
280282
| --- | --- | --- |
281-
| `selected_window_contract_revisions` | `["1.3-parity"]` | `[]` |
283+
| `selected_window_contract_revisions` | `["1.3"]` | `[]` |
282284

283285
This member belongs to the probe's `capabilities` object. The selected-window
284286
wire version remains 1, the phase version 1 and the fingerprint/schema version 2.

‎docker/selected_window_report.py‎

Lines changed: 14 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
* the in-place trim view and the hash of the retained rows in the existing primary hash domain;
1111
* the exact report_window record R (its lookback member is the one triple of a build with no
1212
lookback producer), the full/v1 report_shape and the capability record (its
13-
contract revision is this build's parity declaration, CONTRACT_REVISIONS);
13+
contract revision is this build's completeness declaration, CONTRACT_REVISIONS);
1414
* the frozen selected_window ABI as a ctypes wrapper, and
1515
the exact comparison of the engine's native counts with the planned counts.
1616
@@ -53,16 +53,17 @@
5353
FINGERPRINT_VERSION = 2
5454
# The contract revision this build declares in its capability record (the member
5555
# selected_window_contract_revisions of --capabilities-json). This is the ONE place it is
56-
# written; capabilities_record is the code that reads it. Revision 1.3-parity declares value
57-
# parity with the 1.4.0 reference on the tested cases, with the typed value-ownership codes
58-
# strategy_value_invalid, engine_command_value_invalid, report_result_invalid and
59-
# report_post_execution_failed emitted and no completeness claim (value_ownership
60-
# parity_with_reference; a full build with a completeness proof lists ("1.3",), never both).
56+
# written; capabilities_record is the code that reads it. Revision 1.3 declares value
57+
# ownership "complete": the section-4 producers and manifest are present, the completeness
58+
# proof has run (EN-115), and the typed value-ownership codes strategy_value_invalid,
59+
# engine_command_value_invalid, report_result_invalid and report_post_execution_failed are
60+
# emitted. A full build declares 1.3, never 1.3-parity; a parity build declares 1.3-parity
61+
# (value_ownership parity_with_reference) and never 1.3; a tuple holding both is invalid.
6162
# The supported runtime lists this singleton tuple, with no feature switch, environment knob
6263
# or second constant. It is a declaration only: no request, report_window, phase record or
6364
# fingerprint member carries it, and the wire version (1), the phase version (1) and the
6465
# fingerprint/schema version (2) are unchanged.
65-
CONTRACT_REVISIONS = ("1.3-parity",)
66+
CONTRACT_REVISIONS = ("1.3",)
6667
REPORT_SHAPE = "full/v1"
6768
METERING_BASIS = "window-primary-input-bars/v1"
6869
MAX_PREROLL_BARS = 5000
@@ -694,10 +695,12 @@ def capabilities_record(supported: bool) -> Dict[str, Any]:
694695
members of features this build does not offer (compact shape, digest) are always absent.
695696
696697
selected_window_contract_revisions is CONTRACT_REVISIONS as a fresh list when supported:
697-
exactly ["1.3-parity"], declaring value parity with the 1.4.0 reference on the tested
698-
cases, with the typed value-ownership codes (strategy_value_invalid,
699-
engine_command_value_invalid, report_result_invalid and report_post_execution_failed)
700-
emitted and no completeness claim, and never "1.3", which requires a completeness proof.
698+
exactly ["1.3"], declaring value ownership "complete": the section-4 producers and
699+
manifest are present, the completeness proof has run (EN-115), and the typed
700+
value-ownership codes (strategy_value_invalid, engine_command_value_invalid,
701+
report_result_invalid and report_post_execution_failed) are emitted. A full build
702+
declares "1.3", never "1.3-parity"; a parity build declares exactly ["1.3-parity"] and
703+
never "1.3"; a tuple holding both is invalid.
701704
It is [] when the runtime is not supported,
702705
so an unsupported runtime lists no revision at all. No other member of this document
703706
changes with the declaration."""

‎docs/pages/public-contract.md‎

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -48,12 +48,15 @@ It extends typed failures across source value admission
4848
(`report_post_execution_failed`), without changing C layouts or
4949
`PF_ABI_VERSION` 4; from 1.6.1 (unreleased; see
5050
[CHANGELOG.md](../../CHANGELOG.md#161-rc1--2026-10-17)) the image declares
51-
selected-window contract revision `1.3-parity` (`["1.3-parity"]` under
51+
selected-window contract revision `1.3` again (`["1.3"]` under
5252
`capabilities.selected_window_contract_revisions` when the runtime supports
53-
selected windows and `[]` otherwise), which emits the four typed codes
53+
selected windows and `[]` otherwise), now with the EN-115 completeness proof:
54+
the section-4 producers and manifest are present and value ownership is
55+
`complete`, and it emits the four typed codes
5456
(`strategy_value_invalid`, `engine_command_value_invalid`,
55-
`report_result_invalid` and `report_post_execution_failed`), with parity with
56-
the 1.4.0 reference on tested cases, and no completeness claim (1.6.0 declared
57+
`report_result_invalid` and `report_post_execution_failed`). A build declaring
58+
`1.3` pairs only with a `complete` receipt; `1.3-parity` remains the parity
59+
build's literal, and a tuple holding both is invalid (1.6.0 declared
5760
`1.3` without a completeness proof). The repository's
5861
[CHANGELOG.md](../../CHANGELOG.md#160--2026-10-17), under
5962
*1.6.0 — 2026-10-17*, inventories these changes and the documentation, test,

‎docs/pages/report-schema.md‎

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,15 @@ each field to its meaning and units.
88
@see #pf_report_t for the verbatim struct declaration.
99

1010
The published engine/codegen **1.6.0** image declares selected-window contract
11-
revision `1.3`. From 1.6.1 (unreleased), the image declares `1.3-parity`
12-
instead: it emits the four typed codes (`strategy_value_invalid`,
13-
`engine_command_value_invalid`, `report_result_invalid` and
14-
`report_post_execution_failed`), with value parity with the 1.4.0 reference on
15-
tested cases, and no completeness claim.
11+
revision `1.3`. From 1.6.1 (unreleased), the image declares `1.3` again, now
12+
with the EN-115 completeness proof: the section-4 producers and manifest are
13+
present, value ownership is `complete`, and it emits the four typed codes
14+
(`strategy_value_invalid`, `engine_command_value_invalid`,
15+
`report_result_invalid` and `report_post_execution_failed`). A build declaring
16+
`1.3` pairs only with a `complete` receipt; `1.3-parity` remains the parity
17+
build's literal, and a tuple holding both is invalid.
1618
The `--capabilities-json` probe's
17-
`capabilities.selected_window_contract_revisions` is `["1.3-parity"]` for a
19+
`capabilities.selected_window_contract_revisions` is `["1.3"]` for a
1820
supported runtime and `[]` otherwise. The declaration lives in that capability
1921
record; the selected-window wire version remains 1, the phase version 1 and the
2022
fingerprint/schema version 2.

0 commit comments

Comments
 (0)