You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 17087c5
Browse filesBrowse the repository at this point in the historyBrowse files
HaoLiangWen
authored and
HaoLiangWen
committed
docs: declare selected-window contract revision 1.3-parity for 1.6.1 (EN-115)
Update docs/pages/report-schema.md, docs/pages/public-contract.md,
docker/README.md and README.md so the image declares selected-window
contract revision 1.3-parity (["1.3-parity"] on a supported runtime and []
otherwise), covering value ownership through strategy_value_invalid,
engine_command_value_invalid, report_result_invalid and
report_post_execution_failed, value parity with the 1.4.0 reference on
tested cases, and no completeness claim. Add the 1.6.1 — Unreleased
entry to CHANGELOG.md (EN-115: no completeness proof). VERSION stays
untouched.
Replaces the 1.3 capability sentences introduced by 868aa65 and
517a1b4 (following 47184e5):
- docs/pages/report-schema.md (868aa65): "The engine/codegen 1.6.0 image
declares selected-window contract revision 1.3, meaning complete value
ownership with strategy_value_invalid, engine_command_value_invalid,
report_result_invalid and report_post_execution_failed." and "The
--capabilities-json probe's capabilities.selected_window_contract_revisions
is ["1.3"] for a supported runtime and [] otherwise."
- docs/pages/public-contract.md (517a1b4, 868aa65): "It declares
selected-window contract revision 1.3 (["1.3"] under
capabilities.selected_window_contract_revisions when the runtime supports
selected windows and [] otherwise) and extends typed failures across
source value admission (strategy_value_invalid), derived execution and
settlement arithmetic (engine_command_value_invalid), non-finite canonical
trade or summary doubles (report_result_invalid) and post-boundary
serialization faults (report_post_execution_failed), without changing C
layouts or PF_ABI_VERSION 4."
- README.md (517a1b4, 868aa65): "The release notes cover selected-window
contract revision 1.3, typed failures across source values, engine
arithmetic and report production, finite trade and summary doubles, and the
documentation, test, CI and benchmark updates since 1.5.0.", "The
engine/codegen 1.6.0 image advertises selected-window contract revision
1.3 through docker/run_json.py --capabilities-json: value ownership through
strategy_value_invalid, engine_command_value_invalid,
report_result_invalid and report_post_execution_failed.",
"capabilities.selected_window_contract_revisions is ["1.3"] when the runtime
supports selected windows and [] otherwise; see the capability table and
report schema." and the v1.6.0 Releases bullet ("selected-window contract
revision 1.3").
- docker/README.md (517a1b4, 868aa65): "The engine/codegen 1.6.0 image's
run_json.py --so <strategy.so> --capabilities-json probe declares revision
1.3, covering value ownership through strategy_value_invalid,
engine_command_value_invalid, report_result_invalid and
report_post_execution_failed." and the selected_window_contract_revisions
table row.
- **[v1.6.0](https://github.com/pineforge-4pass/pineforge-engine/releases/tag/v1.6.0)** (2026-10-17) — selected-window contract revision `1.3` (`capabilities.selected_window_contract_revisions: ["1.3"]` on a supported runtime and `[]` otherwise); typed failures across source value admission (`strategy_value_invalid`), derived execution and settlement arithmetic (`engine_command_value_invalid`), non-finite canonical trade or summary doubles (`report_result_invalid`) and post-boundary serialization faults (`report_post_execution_failed`), with every report writer enforcing JSON so no bare `NaN` or `Infinity` token is emitted; Doxygen favicon, 404 page, `robots.txt`, `sitemap.xml`, canonical URLs and tag-or-`unreleased` version label; CI deadline and timeout-flag removals, private-fixture test moves and benchmark comparison/quiet-gate updates. The C layouts stay at ABI 4, `PF_ABI_VERSION` stays 4, the selected-window wire version stays 1, the phase version 1 and the fingerprint/schema version 2. Pair with codegen 1.6.0, regenerate and relink. See [CHANGELOG.md](CHANGELOG.md#160--2026-10-17).
690
+
- **[v1.6.0](https://github.com/pineforge-4pass/pineforge-engine/releases/tag/v1.6.0)** (2026-10-17) — selected-window contract revision `1.3-parity` in 1.6.1 (`capabilities.selected_window_contract_revisions: ["1.3-parity"]` on a supported runtime and `[]` otherwise, covering value ownership through the four codes, parity with the 1.4.0 reference on tested cases, and no completeness claim; the 1.6.0 tag declared `["1.3"]` without a completeness proof); typed failures across source value admission (`strategy_value_invalid`), derived execution and settlement arithmetic (`engine_command_value_invalid`), non-finite canonical trade or summary doubles (`report_result_invalid`) and post-boundary serialization faults (`report_post_execution_failed`), with every report writer enforcing JSON so no bare `NaN` or `Infinity` token is emitted; Doxygen favicon, 404 page, `robots.txt`, `sitemap.xml`, canonical URLs and tag-or-`unreleased` version label; CI deadline and timeout-flag removals, private-fixture test moves and benchmark comparison/quiet-gate updates. The C layouts stay at ABI 4, `PF_ABI_VERSION` stays 4, the selected-window wire version stays 1, the phase version 1 and the fingerprint/schema version 2. Pair with codegen 1.6.0, regenerate and relink. See [CHANGELOG.md](CHANGELOG.md#160--2026-10-17).
689
691
-**[v1.5.0](https://github.com/pineforge-4pass/pineforge-engine/releases/tag/v1.5.0)** (2026-10-12) — recorded outputs: a module can record per-bar doubles in named slots, run-level doubles and events, read through the nine `pf_outputs` runtime exports with coded refusals, off until a caller turns them on and byte-identical when unused; a run's report belongs to the call that began it; the engine's test inputs and strategy scripts moved to a private repository, with tests that need them skipping by name, a LEGAL.md *Data not distributed* note and a maintainers' private-fixture overlay. The C layouts stay at ABI 4, `PF_ABI_VERSION` stays 4 and the new members enter `engine_script_run_v19` without an epoch. Pair with codegen 1.5.0, regenerate and relink. See [CHANGELOG.md](CHANGELOG.md#150--2026-10-12).
690
692
-**[v1.4.0](https://github.com/pineforge-4pass/pineforge-engine/releases/tag/v1.4.0)** (2026-10-08) — two additive C failure getters; typed input/override provenance with explicit unresolved reasons and duplicate-title counts; coded failure JSON and checked-setting refusals; Pine exit/fill-location corrections that can change trades, reports and hash values on the affected paths; chart-timeframe live input and final-delivery draining; feed ownership and verification improvements. The C layouts stay at ABI 4, while hash recipes and report content have the disclosed changes. Pair with codegen 1.4.0, regenerate and relink. See [CHANGELOG.md](CHANGELOG.md#140--2026-10-08).
691
693
-**v1.3.0** (2026-10-06) — a minor release: `pineforge-live` admits the proven confirmed-bar request shapes and standalone close-only `varip` from the confirmed-bar receipt a strategy generated by pineforge-codegen 1.3.0 exports; Pine adapter parity changes (exit binding at the call, global exits on a held position beside an opposite entry or a same-side add, margin calls at the open after a `process_orders_on_close` close fill, the margin-call schedule, the exact reversal tie, the carried trail, the position view after a close fill, open-marketable exits first). `pineforge.h` is unchanged. No report key changes. The hub image `pineforge-release:1.3.0` carries the pair; regenerate and relink. See [CHANGELOG.md](CHANGELOG.md).
0 commit comments