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 4c78f39
Browse filesBrowse the repository at this point in the historyBrowse files
docs: the 1.5.0 release (changelog, current pair, HPO note) (#374)
Squash of #374 (3 docs commits on 2394ba2, tree 776a3cb). The CHANGELOG entry is dated 2026-10-12, the tag date; the first commit's "2026-10-13" below is superseded. The three commit messages follow verbatim, so their doc-revert namings are kept.
docs: prepare the 1.5.0 release (changelog, current pair)
Date the CHANGELOG's 1.5.0 entry 2026-10-13 and give it the release link
line naming the paired pineforge-codegen 1.5.0, keeping the recorded-outputs
and call-scoped-report content unchanged. Add the release's other
user-visible changes: the test inputs and strategy scripts moved to a
private repository, where a test that needs one skips with the pinned
message naming the missing file; the LEGAL.md "Data not distributed"
section; and the private-fixture overlay the maintainers run the
verification with.
README: the current-release block, the codegen command-block pointer, the
C ABI counts line and a new v1.5.0 Releases bullet now name 1.5.0; the
v1.4.0 descriptions, scoreboard and benchmark measurements stay untouched.
The current-release block's 1.4.0 sentence from 5a1ad3a ("The release notes
cover typed and unresolved provenance, coded failures, checked settings,
adapter fixes and chart-clock live input") is replaced on purpose by the
1.5.0 sentence that lists what 1.5.0 covers; that 1.4.0 summary stays in the
Releases list (the v1.4.0 bullet) and in CHANGELOG.md's 1.4.0 entry.
docs/pages/public-contract.md: the 1.5.0 paragraph follows the 1.4.0 one
and the same-version pairing line now says 1.5.0.
Scoreboard and benchmark numbers are untouched; no file outside these
three changes.
docs: 1.5.0 is released: status words, HPO note
The CHANGELOG's 1.5.0 entry gains its HPO bullet: pineforge-hpo 0.13.2
pins pineforge-codegen <1.4, and HPO support for codegen 1.4 and 1.5
(enum options as Enum.member tags) comes in pineforge-hpo 0.14.0.
Five files that still called 1.5.0, or a 1.5.0 feature, unreleased or
targeted for it now read as released once the tag lands:
docs/pages/abi-stability.md (the RunFailureCode exception, the
symbol-inventory counts line, the recorded-outputs line),
docs/pages/index.md (its counts line, matching the README wording),
the run-failure page (the outputs and selected-window rows' status, the
two 1.5.0 outputs reasons, and the 24 catalog rows that said none was
released), docker/README.md (the recorded-outputs section) and
docs/outputs.md. Only the status words change; "not part of 1.4.0"
stays where it is true history, and no number, claim or other sentence
moves.
No file outside these six changes.
Co-Authored-By: Claude Code <[email protected]>
docs: list the new installed header native_calc_point.hpp for 1.5.0
K1 (#369) added include/pineforge/native_calc_point.hpp, installed by the
include/pineforge rule in CMakeLists.txt with the other headers. Name it in the
1.5.0 CHANGELOG entry and in the native C++ API list of
docs/pages/public-contract.md (new in 1.5.0). Docs only.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
paired with [pineforge-codegen 1.5.0](https://github.com/pineforge-4pass/pineforge-codegen-oss/releases/tag/v1.5.0).
12
+
This minor release adds recorded outputs and the call-scoped report rule
13
+
below, and moves the engine's test inputs and strategy scripts out of this
14
+
repository. Regenerate strategy C++ with the matching codegen and relink
15
+
against the matching engine headers and archive; replacing the archive alone
16
+
does not update a statically linked strategy library.
9
17
10
18
-**Recorded outputs.** A module can record what it computes on each bar
11
19
besides its trades: doubles in named slots per bar, doubles kept once per
@@ -48,6 +56,30 @@ version number follows semantic versioning over the surfaces the
48
56
`BacktestEngine::fill_report`, so the C and native-module entry points and
49
57
the generated `run_backtest` / `run_backtest_full` wrappers all obey it, with
50
58
no change to emitted source.
59
+
-**The test inputs and strategy scripts moved to a private repository.** The
60
+
engine's non-public test inputs — price series, strategy scripts and the
61
+
sources generated from them, and some test programs — are no longer in this
62
+
repository; the maintainers keep them in a private repository. A test that
63
+
needs one skips, naming the missing file with the pinned message
64
+
`SKIP private fixtures not present:` followed by that file's path, so a tree
65
+
without them still configures and runs the rest of the suite.
66
+
-**LEGAL.md, "Data not distributed".** LEGAL.md now carries a *Data not
67
+
distributed* section — pointed to from its submodule paragraph — recording
68
+
that some test inputs are not distributed in this repository or in its
69
+
submodules, and that the engine does not depend on them: it builds without
70
+
them, and the public corpus and the kernel suites run without them.
71
+
-**A private-fixture overlay for the maintainers' verification.** With the
72
+
private inputs overlaid back into the tree — signalled by
73
+
`PINEFORGE_PRIVATE_FIXTURES` — the verification requires every pinned row to
74
+
run: a row that skips there fails the run. Without the overlay, those rows
75
+
skip in public runs and the row floors account for them.
76
+
-**A new installed header, `<pineforge/native_calc_point.hpp>`.** It holds the
77
+
plain-data vocabulary of the calculation points of a driving-event schedule:
78
+
the driving-event kinds (`EventKind`, `Event`), the cadence bits an instance
79
+
computes on, and the phase and finality of one planned calculation. The
80
+
headers install with the others (CMakeLists.txt, the `install(DIRECTORY
81
+
include/pineforge ...)` rule); it is part of the native C++ host surface.
82
+
-**HPO.** pineforge-hpo 0.13.2 pins pineforge-codegen <1.4; HPO support for codegen 1.4 and 1.5 (enum options as Enum.member tags) comes in pineforge-hpo 0.14.0.
Copy file name to clipboardExpand all lines: README.md
+12-11Lines changed: 12 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,16 +36,16 @@ The separate PineForge compiler, [`pineforge-codegen`](https://github.com/pinefo
36
36
-**Yours to embed.** 145 `PF_API` declarations across five installed headers — `pineforge.h`'s 94 (74 of the 80 runtime exports, the other six being declared in `execution_observer.h` and `selected_window.h`, three each, and up to 20 per-strategy functions a generated module defines), `native_c_api.h`'s 43 native-host declarations and `selected_window_plan.h`'s two planner declarations — an ABI that is append-only within a major version from 1.0 on. Call it from C, Python, Rust, Go, Node, Julia — or let an AI agent drive it over MCP.
37
37
38
38
Recorded outputs and their additional API declarations described here are
39
-
unreleased work targeted for **1.5.0**; they are not part of 1.4.0.
-**[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).
677
678
-**[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).
678
679
-**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).
679
680
-**v1.2.0** (2026-10-05) — a minor release: a strategy generated by pineforge-codegen 1.2.0 exports a compiled execution-capabilities receipt (`strategy_capabilities_receipt`), from which `pineforge-live` refuses what its close-only stream cannot honour; Pine adapter parity changes (exit children at one point, the trail tolerance, margin, sizing and admission rules, the explicit quantity floor, the script's equity mark, bar fills under `process_orders_on_close`, the session clock across daylight-saving switches), and native runner service operation, cumulative report export and live redelivery. No report key changes. The hub image `pineforge-release:1.2.0` carries the pair; regenerate and relink. See [CHANGELOG.md](CHANGELOG.md).
Copy file name to clipboardExpand all lines: docs/pages/run-failure-codes.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ codes it tested the text alone, so a script stopped by an empty
93
93
94
94
The tables below list the catalog at this tree.
95
95
96
-
The `outputs_limit` and `outputs_rejected` rows below are unreleased, targeted for 1.5.0, and not part of 1.4.0; so are the 24 selected-window and report-contract rows described [after the tables](#run_failure_codes_selected_window). The other 38 codes retain their released 1.4.0 status. The `strategy_library_incompatible` row counts the two unreleased 1.5.0 outputs reasons, `outputs_api_mismatch` and `outputs_manifest_invalid`, in addition to its six released 1.4.0 reasons.
96
+
The `outputs_limit` and `outputs_rejected` rows below are released in 1.5.0, and not part of 1.4.0; so are the 24 selected-window and report-contract rows described [after the tables](#run_failure_codes_selected_window). The other 38 codes retain their released 1.4.0 status. The `strategy_library_incompatible` row counts the two released 1.5.0 outputs reasons, `outputs_api_mismatch` and `outputs_manifest_invalid`, in addition to its six released 1.4.0 reasons.
97
97
98
98
<!-- BEGIN generated from docker/run_failure_codes.json: python3 scripts/test_gen_run_failure_catalog_diff.py --write-docs-tables -->
99
99
@@ -224,7 +224,7 @@ three: `report_post_execution_failed` (the phases after the strategy has
224
224
finished), `engine_command_value_invalid` (an invalid command value the engine
225
225
derived itself) and `window_pruner_unsupported` (the optimizer's trial pruner).
226
226
Their classes, argument kinds and English are the contract's; all are
227
-
`retryable: false` and `since: 1.5.0`, and none is released. The registry
227
+
`retryable: false` and `since: 1.5.0`, and all are released. The registry
228
228
declares them and validates their arguments, which is all this page states
229
229
about them: whether a build raises one is the build's own, and a row in the
230
230
catalog is not proof that the source paths it names enforce anything.
0 commit comments