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 517a1b4
Browse filesBrowse the repository at this point in the historyBrowse files
authored
docs: the 1.6.0 release (changelog, current pair, HPO note) (#399)
* docs: the 1.6.0 release (changelog, current pair, HPO note)
Prepare the final 1.6.0 release documentation dated 2026-10-17, paired with pineforge-codegen 1.6.0 and the matching pineforge-hpo release for selected-window contract revision 1.3.
CHANGELOG.md adds the 1.6.0 — 2026-10-17 entry above 1.6.0-rc.1 — 2026-10-14, carrying forward the release-candidate entry's substance and naming the six documentation and test-only changes merged since v1.6.0-rc.1 (#390, #393, #394, #395, #396, #397).
README.md updates the current-release block and the codegen command-block pointer to 1.6.0 and adds the v1.6.0 bullet to the Releases section. The current-release block's 1.5.0 sentence from 4c78f39 ("The release notes cover recorded outputs, the call-scoped report rule and the test inputs' move to a private repository") is replaced on purpose by the 1.6.0 sentence that lists what 1.6.0 covers; that 1.5.0 summary stays in the Releases list (the v1.5.0 bullet) and in CHANGELOG.md's 1.5.0 entry.
docs/pages/public-contract.md adds the 1.6.0 paragraph after the 1.5.0 paragraph and updates the same-version pairing line to 1.6.0.
* docs: 1.6.0 notes review fixes (HPO pairing line, follow-up figures, value-ownership wording)
The paired-HPO line no longer claims HPO support for selected-window
revision 1.3; HPO 1.6.0 does not implement selected windows
(docs/return-stats.md:9 in pineforge-hpo). The landed follow-ups #396/#397
are said to be checked against their own deliberate bugs, and the figures
remain the candidate's. README.md and docker/README.md replace
"complete value ownership with" by "value ownership through", the wording
of the 1.6.0-rc.1 changelog entry, since no completeness proof was run.
The changelog's no-code-change sentence names the docker/README.md rewording.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
---------
Co-authored-by: HaoLiangWen <[email protected]>
Co-authored-by: CORE-TOP <[email protected]>
Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
paired with [pineforge-codegen 1.6.0](https://github.com/pineforge-4pass/pineforge-codegen-oss/releases/tag/v1.6.0).
12
+
This minor release extends typed failures from source values through engine
and `docs/ci.md` list `docs/seo_postprocess.py` among the five
134
+
documentation-build inputs excluded from docs-only CI skips ([#394]).
135
+
-**Release-candidate notes, README apex link and 1.5.0 notes additions ([#393]).**
136
+
Added the `1.6.0-rc.1` changelog entry, updated the `README.md` header
137
+
link from `https://www.pineforge.dev` to `https://pineforge.dev`, and added
138
+
*Additions to the 1.5.0 notes* in `CHANGELOG.md` for the opt-in
139
+
selected-window mode ([#363]) and `_typed_failure` in `docker/run_json.py`.
140
+
-**Value-failure raise sites on the run-failure-codes page ([#395]).**
141
+
`docs/pages/run-failure-codes.md` lists fifteen of the 24 selected-window
142
+
and report-contract codes as having a raise site in this tree:
143
+
`strategy_value_invalid` in the C++ source layer,
144
+
`engine_command_value_invalid` in the engine kernel, native engine and Pine
145
+
adapter, and `report_result_invalid` in `docker/run_json.py`, alongside the
146
+
twelve `docker/` wrapper codes, leaving nine codes with no producer in this
147
+
tree.
148
+
-**Assertion on the quantity-grid overflow fallback ([#396]).**
149
+
In `tests/test_value_admission_arith.cpp`,
150
+
`quantity_infinite_intermediate_fallback` places a cash-typed entry (`cash`
151
+
`1e308`, `price``2`, `grid``0.001`) through `strategy_entry`, catches a
152
+
thrown failure as a failed `CHECK` rather than terminating through a
153
+
`noexcept` boundary, and asserts the admitted contracts equal `cash / price`
154
+
bit for bit; the explicit fixed-quantity overflow check stays in
155
+
`quantity_explicit_overflow_fallback` when the cash row records no failure.
156
+
-**Assertion that a failed report writes one whole JSON document on stdout ([#397]).**
157
+
In `tests/test_run_json_post_execution.py`, `assert_failure` requires the
158
+
owned stdout to be one JSON-object line (turning a JSON decode error into
159
+
an `AssertionError` naming the prefix and length), and
160
+
`test_encoder_failure_after_report_chunks` asserts from the recorded fault
161
+
prefix that no report chunk reached stdout and that `stdout.write` was
162
+
called once.
163
+
-**HPO.** Pair with the matching `pineforge-codegen 1.6.0` and `pineforge-hpo`
164
+
1.6.0 (`pineforge-hpo` 0.13.2 pinned `pineforge-codegen <1.4`, and 0.14.0 added
Copy file name to clipboardExpand all lines: README.md
+12-9Lines changed: 12 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,18 +38,20 @@ The separate PineForge compiler, [`pineforge-codegen`](https://github.com/pinefo
38
38
Recorded outputs and their additional API declarations described here are
- **[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).
686
689
-**[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).
687
690
-**[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).
688
691
-**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