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 ec3f3ba
Browse filesBrowse the repository at this point in the historyBrowse files
docs: release-notes backfill for 1.6.2, 1.6.3 and 1.7.0 (README Releases list, CHANGELOG sections) (CR-315)
The README Releases list stopped at v1.6.1 and the CHANGELOG had no 1.6.2 or 1.6.3
section (1.7.0 sat directly above 1.6.1). This adds, from the tags and the GitHub release
bodies only:
- README.md Releases: v1.7.0 (2026-10-25), v1.6.3 (2026-10-23), v1.6.2 (2026-10-21), each
with its release link, the codegen it pairs with and the CHANGELOG anchor.
- CHANGELOG.md: "1.6.3 - 2026-10-23" (CI, release-gate and test-only; `git diff v1.6.2
v1.6.3` under src/ include/ cmake/ docker/ runner/ shows only
docker/run_failure_codes_diff.json) and "1.6.2 - 2026-10-21" (selected-window contract
revision 1.3 with the EN-115 completeness proof, proportional annualisation for runs
shorter than a day, CI changes; the maintainer-built linux-x86_64 archive and its SHA-256
as the release body states them).
Additions only (0 lines removed), so no sentence is replaced and no citation moves; the
engine README and CHANGELOG carry no file:line citations.
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
paired with [pineforge-codegen 1.6.3](https://github.com/pineforge-4pass/pineforge-codegen-oss/releases/tag/v1.6.3).
831
+
This patch release carries CI, release-gate and test-only changes after 1.6.2.
832
+
Nothing under `src/`, `include/`, `cmake/` or `runner/` changed between `v1.6.2`
833
+
and `v1.6.3`; under `docker/` only `run_failure_codes_diff.json` changed, which
834
+
is the run-failure code catalog diff published with the release.
835
+
836
+
-**CI runs on the GCP fleet.** The engine's CI runs on the GCP fleet
837
+
(`pf-gcp-pr`, `pf-gcp-main`), fork-gated (#474). The pull-request wall is
838
+
split from full-event verification (CR-233 A and B, squash of #477, #480).
839
+
-**A release needs full verify and parity green first.** The release job
840
+
requires both before an engine release (C2, #479).
841
+
-**Test-only.** The live test matches delivery receipts by request sequence
842
+
(CR-223, #478); a session tape comment no longer names a private repository
paired with [pineforge-codegen 1.6.2](https://github.com/pineforge-4pass/pineforge-codegen-oss/releases/tag/v1.6.2).
- **[v1.7.0](https://github.com/pineforge-4pass/pineforge-engine/releases/tag/v1.7.0)** (2026-10-25) — report-sink transport, scratch-backed history and bounded storage admission, with new C++ views and command-line report routes. `get_trade()` and `closed_trade()` now return `Trade` by value, working-book, journal and cohort accessors return views, and some reads can throw on scratch I/O; closing a trade writes `TradeLedger` scratch even without a report sink, so a run needs a disk-backed `TMPDIR` or an explicit scratch directory; the C++ epoch namespace is still `engine_script_run_v19` although the layout of `BacktestEngine` changed, so rebuild every C++ object that includes an engine header, regenerate strategy C++ with the matching codegen and relink. Pair with [codegen 1.7.0](https://github.com/pineforge-4pass/pineforge-codegen-oss/releases/tag/v1.7.0). The known limits of this release (slower than 1.6.3 on some scripts, the closed-trade cache and its size by entry point) are in [CHANGELOG.md](CHANGELOG.md#170--2026-10-25), section "Costs that remain".
715
+
-**[v1.6.3](https://github.com/pineforge-4pass/pineforge-engine/releases/tag/v1.6.3)** (2026-10-23) — CI, release-gate and test-only changes after 1.6.2: the engine's CI runs on the GCP fleet (`pf-gcp-pr`, `pf-gcp-main`), fork-gated; the PR wall is split from full-event verification (CR-233 A+B); a release requires full verify and parity green first (C2); the live test matches delivery receipts by request sequence (CR-223); a session tape comment no longer names a private repository. Nothing under `src/`, `include/`, `cmake/` or `runner/` changed since v1.6.2, and in `docker/` only the run-failure code catalog diff (`run_failure_codes_diff.json`) did. Pair with codegen 1.6.3. See [CHANGELOG.md](CHANGELOG.md#163--2026-10-23).
716
+
-**[v1.6.2](https://github.com/pineforge-4pass/pineforge-engine/releases/tag/v1.6.2)** (2026-10-21) — selected-window contract revision `1.3` again, declared with the EN-115 completeness proof (`capabilities.selected_window_contract_revisions: ["1.3"]` on a supported runtime and `[]` otherwise; 1.6.1 declared `1.3-parity`); proportional annualisation for runs shorter than a day, never null (CR-202, W-73); the ownership probes fixed so proof B reads 118/118 (CR-139) and the ownership manifest-controls test sharded four ways (CR-196); CI changes: Linux x64 jobs on the pf-ci-spot pool and release jobs on pf-ci-release, `timeout-minutes` removed, the actions of `promote-baseline.yml` pinned by SHA, the PR tier skipping the slow rows (D1, CR-195). It ships the [v1.6.2-rc.1](https://github.com/pineforge-4pass/pineforge-engine/releases/tag/v1.6.2-rc.1) candidate (2026-10-19). Pair with codegen 1.6.2, regenerate and relink. See [CHANGELOG.md](CHANGELOG.md#162--2026-10-21).
714
717
- **[v1.6.1](https://github.com/pineforge-4pass/pineforge-engine/releases/tag/v1.6.1)** (2026-10-18) — selected-window contract revision `1.3-parity` (`capabilities.selected_window_contract_revisions: ["1.3-parity"]` on a supported runtime and `[]` otherwise) rather than `1.3` until a completeness proof exists (EN-115), with the four typed value-ownership codes (`strategy_value_invalid`, `engine_command_value_invalid`, `report_result_invalid` and `report_post_execution_failed`) emitted and value parity with the 1.4.0 reference on the tested cases; per-stage `startedAt` and `seconds` in `preflight-summary.json`; `noindex` on raw Doxygen source listings and their omission from `sitemap.xml`; verifier-tests sharded across parallel `unittest` subprocesses; the lower-feed timing ratio skipped only under AddressSanitizer. 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.1, regenerate and relink. See [CHANGELOG.md](CHANGELOG.md#161--2026-10-18).
715
718
- **[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; 1.6.0 declared contract revision `1.3`; corrected to `1.3-parity` in 1.6.1); 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).
716
719
-**[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).
0 commit comments