Skip to content

Commit 5a1ad3a

Browse files
luisleo526codex
andauthored
docs: date 1.4.0 after the e81072d release notes (#359)
Intentionally supersede the planned, unreleased and before-tag sentences introduced by e81072d. Apply the same 22 dated-release wording substitutions and paired tag links. Preserve historical pre-tag versions and observations, facts, policy, adapter warnings, parser reasons and diagnostic limits. The reanchor and this message clarification do not change the reviewed documentation tree. Hold this change for the coordinated release notice window; a changed dispatch date requires a reviewed date and anchor update. Co-authored-by: Codex <[email protected]>
1 parent e81072d commit 5a1ad3a

6 files changed

Lines changed: 39 additions & 38 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,13 @@ README's *Releases* section and on the GitHub releases page. From 1.0.0 the
55
version number follows semantic versioning over the surfaces the
66
[public contract](docs/pages/public-contract.md) lists.
77

8-
## Unreleased
8+
## 1.4.0 — 2026-10-08
99

10-
**Planned 1.4.0**, paired with pineforge-codegen 1.4.0. This release is not
11-
tagged yet. The candidate pairs engine `b3192bfc` with codegen `bfc4ddce`;
12-
their version files still name 1.3.0 until the release workflow stamps them.
13-
The planned minor release adds run-failure codes, typed report provenance
10+
**[1.4.0](https://github.com/pineforge-4pass/pineforge-engine/releases/tag/v1.4.0)**,
11+
paired with [pineforge-codegen 1.4.0](https://github.com/pineforge-4pass/pineforge-codegen-oss/releases/tag/v1.4.0).
12+
The pre-tag behavior candidate paired engine `b3192bfc` with codegen
13+
`bfc4ddce`; its version files still named 1.3.0 when the samples were built.
14+
This minor release adds run-failure codes, typed report provenance
1415
and the Pine adapter and live-runner corrections below. Regenerate strategy
1516
C++ with the matching codegen and relink against the matching engine headers
1617
and archive; replacing the archive alone does not update a statically linked
@@ -25,7 +26,7 @@ epoch stays `engine_script_run_v19`; *State hashes* below describes the
2526
recipe additions. *Report keys and provenance* describes the JSON changes
2627
that consumers must handle.
2728

28-
The prepared 1.4.0 facts map to baseline
29+
The 1.4.0 facts map to baseline
2930
`pineforge-parity-baseline-20261007-engine-b3192bfc`: its recorded grading
3031
outcomes are **<!-- pf:releases[1.4.0].scoreboard.excellent|int -->7,983<!-- /pf -->
3132
excellent / <!-- pf:releases[1.4.0].scoreboard.strong|int -->6<!-- /pf --> strong**
@@ -227,7 +228,7 @@ results on that population, not cross-version trade or hash identity.
227228

228229
Six synthetic requests were run through the installed entrypoint on
229230
the exact v1.3.0 pair and the pinned candidate pair, using the same 40-bar
230-
feed. Planned 1.4.0 refuses three requests that 1.3.0 allowed to complete:
231+
feed. 1.4.0 refuses three requests that 1.3.0 allowed to complete:
231232
setting a duplicated `Period` title to `"7"`, passing `"color.blue"` to
232233
`Color`, and setting `Choice` to `"15"` outside its `[10, 20, 30]` options.
233234
The old pair returns success reports for these requests; that wire echo
@@ -388,7 +389,7 @@ path's null fingerprint and the legacy path's per-title records.
388389

389390
### Migration
390391

391-
Use engine 1.4.0 with codegen 1.4.0 when the pair is released; earlier paired
392+
Use engine 1.4.0 with codegen 1.4.0; earlier paired
392393
releases remain historical examples. Regenerate and rebuild every generated
393394
strategy and every C++ host against the new headers and archive. C loaders
394395
can probe the two new getters before using them with older libraries.

‎README.md‎

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -35,11 +35,12 @@ The separate PineForge compiler, [`pineforge-codegen`](https://github.com/pinefo
3535
- **Deterministic to the bit.** Two runs with the same inputs produce identical trade lists. Same on Linux and macOS.
3636
- **Yours to embed.** 124 `PF_API` declarations across two headers — `pineforge.h`'s 81 (64 runtime exports and up to 17 per-strategy functions a generated module defines) and `native_c_api.h`'s 43 native-host 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.
3737

38-
**Planned 1.4.0 is unreleased.** Engine `b3192bfc` pairs with codegen
39-
`bfc4ddce` for the candidate; both still report version 1.3.0 until tagging.
40-
The [release notes](CHANGELOG.md#unreleased) cover typed and unresolved
38+
**[1.4.0](https://github.com/pineforge-4pass/pineforge-engine/releases/tag/v1.4.0)
39+
was released on 2026-10-08**, paired with
40+
[pineforge-codegen 1.4.0](https://github.com/pineforge-4pass/pineforge-codegen-oss/releases/tag/v1.4.0).
41+
The [release notes](CHANGELOG.md#140--2026-10-08) cover typed and unresolved
4142
provenance, coded failures, checked settings, adapter fixes and chart-clock
42-
live input. When the 1.4.0 pair is released, regenerate strategy C++ and
43+
live input. For the 1.4.0 pair, regenerate strategy C++ and
4344
relink against that pair's headers and archive. Published 1.3.0 download and
4445
installation examples below remain pinned to that earlier pair.
4546

@@ -139,8 +140,8 @@ TradingView's execution semantics on top of the kernel; this is the path the
139140
validation scoreboard below measures.
140141
141142
This command block is for the published engine/codegen **1.3.0 pair**.
142-
For the unreleased candidate use the pinned pair above; agreement on the
143-
current `VERSION` text alone does not establish a matching build.
143+
For 1.4.0, use the matching release tags linked above and regenerate and
144+
relink against that pair's headers and archive.
144145
145146
```bash
146147
pip install "pineforge-codegen==1.3.0"
@@ -248,7 +249,7 @@ workaround for those versions.
248249

249250
**Measured <!-- pf:scoreboard.date -->2026-10-07<!-- /pf -->** on main engine <!-- pf:scoreboard.engineCommit|short-code -->`b3192bfc`<!-- /pf --> with codegen-oss <!-- pf:scoreboard.codegenCommit|short-code -->`bfc4ddce`<!-- /pf --> (baseline <!-- pf:scoreboard.id|code -->`pineforge-parity-baseline-20261007-engine-b3192bfc`<!-- /pf -->, snapshot <!-- pf:scoreboard.snapshotSha256|short-code -->`28ba8dbd`<!-- /pf -->): **<!-- pf:scoreboard.graded|int -->7,989<!-- /pf --> graded probes, <!-- pf:scoreboard.excellent|int -->7,983<!-- /pf --> excellent + <!-- pf:scoreboard.strong|int -->6<!-- /pf --> strong**, <!-- pf:scoreboard.belowStrong|int -->0<!-- /pf --> below strong and <!-- pf:scoreboard.engineErrors|int -->0<!-- /pf --> engine errors across <!-- pf:scoreboard.lanes|int -->18<!-- /pf --> market/timeframe lanes. The historical release 1.0.1 inventory holds <!-- pf:inventory.tvTrades|int -->4,776,328<!-- /pf --> trades.
250251

251-
Planned **1.4.0 (unreleased)** maps to **<!-- pf:releases[1.4.0].scoreboard.excellent|int -->7,983<!-- /pf --> excellent / <!-- pf:releases[1.4.0].scoreboard.strong|int -->6<!-- /pf --> strong** on <!-- pf:releases[1.4.0].scoreboard.graded|int -->7,989<!-- /pf --> graded probes (baseline <!-- pf:releases[1.4.0].scoreboard.id|code -->`pineforge-parity-baseline-20261007-engine-b3192bfc`<!-- /pf -->, <!-- pf:releases[1.4.0].scoreboard.date -->2026-10-07<!-- /pf -->), with <!-- pf:releases[1.4.0].scoreboard.belowStrong|int -->0<!-- /pf --> below strong and <!-- pf:releases[1.4.0].scoreboard.engineErrors|int -->0<!-- /pf --> engine errors. These are recorded grading outcomes for that pair and population.
252+
Release **1.4.0 (2026-10-08)** maps to **<!-- pf:releases[1.4.0].scoreboard.excellent|int -->7,983<!-- /pf --> excellent / <!-- pf:releases[1.4.0].scoreboard.strong|int -->6<!-- /pf --> strong** on <!-- pf:releases[1.4.0].scoreboard.graded|int -->7,989<!-- /pf --> graded probes (baseline <!-- pf:releases[1.4.0].scoreboard.id|code -->`pineforge-parity-baseline-20261007-engine-b3192bfc`<!-- /pf -->, promoted <!-- pf:releases[1.4.0].scoreboard.date -->2026-10-07<!-- /pf --> UTC), with <!-- pf:releases[1.4.0].scoreboard.belowStrong|int -->0<!-- /pf --> below strong and <!-- pf:releases[1.4.0].scoreboard.engineErrors|int -->0<!-- /pf --> engine errors. These are recorded grading outcomes for that pair and population.
252253

253254
Release **1.3.0 grades <!-- pf:releases[1.3.0].scoreboard.excellent|int -->7,982<!-- /pf --> excellent / <!-- pf:releases[1.3.0].scoreboard.strong|int -->7<!-- /pf --> strong until the next release**, on <!-- pf:releases[1.3.0].scoreboard.graded|int -->7,989<!-- /pf --> probes (baseline <!-- pf:releases[1.3.0].scoreboard.id|code -->`pineforge-parity-baseline-20261006-engine-7a1f01c0`<!-- /pf -->, <!-- pf:releases[1.3.0].scoreboard.date -->2026-10-06<!-- /pf -->). A main scoreboard advance does not change release results.
254255

@@ -668,7 +669,7 @@ Documentation: [C ABI reference](https://cdocs.pineforge.dev) · [Getting starte
668669

669670
## Releases
670671

671-
- **Planned v1.4.0 — unreleased.** 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 when released, regenerate and relink. See [CHANGELOG.md](CHANGELOG.md#unreleased).
672+
- **[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).
672673
- **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).
673674
- **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).
674675
- **v1.1.0** (2026-10-04) — a minor release: a strategy generated by pineforge-codegen 1.1.0 exports six checked-settings C functions and stops C++ exceptions at its C entry points, and codegen 1.1.0's `transpile_full()` lists the other symbols' feeds a script requests; confirmed-bar streams compute what the batch computes, which fixes the v1.0.0 and v1.0.1 stream `request.security` known issue; Pine adapter parity changes, exact tick-built bar volume, a report-only terminal quote, the Docker harness's lot grid from `syminfo.mincontract` and its multi-symbol `request.security` feeds, and native runner webhook routing, with `pineforge/live_parser.h` and the runner's parser plugins removed (the hub image `pineforge-release:1.1.0` carries the pair); regenerate and relink. See [CHANGELOG.md](CHANGELOG.md).

‎docker/README.md‎

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -14,11 +14,10 @@ never leaves the container**. A pre-transpiled `strategy.cpp` is still
1414
accepted for back-compat. JSON report on stdout, build/transpile noise on
1515
stderr.
1616

17-
This checkout documents the **planned 1.4.0 release (unreleased)**. Its
18-
candidate pairs engine `b3192bfc` and codegen `bfc4ddce`; their version files
19-
still say 1.3.0 until tagging. The release adds typed/unresolved provenance
17+
This checkout documents the **1.4.0 release (2026-10-08)**, pairing engine
18+
1.4.0 with codegen 1.4.0. The release adds typed/unresolved provenance
2019
and coded failures, and the harness uses checked settings when the strategy
21-
exports that API. Use the same-version engine/codegen pair when released,
20+
exports that API. Use the same-version engine/codegen pair,
2221
regenerate the C++ and relink; an older image keeps its own harness behavior.
2322

2423
## Pull (prebuilt)
@@ -268,7 +267,7 @@ docker run --rm \
268267
before this variable existed, apart from `elapsed_seconds`.
269268

270269
The engine catches run errors (TF mismatch, unsupported emulation flags,
271-
unknown-input-TF, etc.) into `strategy_get_last_error()` and, with the planned
270+
unknown-input-TF, etc.) into `strategy_get_last_error()` and, with the
272271
1.4.0 runtime, its code/args getters. The failure line below describes both
273272
the coded form and the earlier text-only form. The container exits `4`
274273
(the harness returns 1; the entrypoint maps any harness failure to 4).
@@ -473,7 +472,7 @@ read-only mounts; the image performs no network I/O at run time.
473472
Every JSON report carries a `fingerprint` recording exactly what produced it —
474473
reversible, no key required:
475474

476-
This is a schematic of the planned 1.4.0 provenance shape, not a measured
475+
This is a schematic of the 1.4.0 provenance shape, not a measured
477476
before/after result. Certified values are typed; unresolved rows use the
478477
resolution records described below. The top-level `applied_inputs` and
479478
`applied_overrides` remain wire-string echoes.
@@ -528,7 +527,7 @@ match a JCS direct encoder for the types we accept:
528527
| Bools / null | `true` / `false` / `null` |
529528

530529
The `{token,digest,provenance}` object shape and canonical encoder are
531-
unchanged in planned 1.4.0. Typed provenance normalization changes the values
530+
unchanged in 1.4.0. Typed provenance normalization changes the values
532531
fed to that encoder, including explicit uncertainty; those changes can
533532
change the token and digest.
534533

‎docs/pages/public-contract.md‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -23,14 +23,14 @@ tree; where no checker holds part of a rule, the page says so. The codegen
2323
states its half in its own `docs/PUBLIC_CONTRACT.md` (pineforge-codegen); the
2424
two releases pair as the last section below says.
2525

26-
Planned 1.4.0 is unreleased. Its candidate (engine `b3192bfc`, codegen
27-
`bfc4ddce`) adds two runtime failure getters and the feature probe
26+
1.4.0 followed on 2026-10-08: engine v1.4.0 with pineforge-codegen 1.4.0.
27+
It adds two runtime failure getters and the feature probe
2828
`PINEFORGE_HAS_RUN_FAILURE_CODES_V1`, without changing C layouts or
2929
`PF_ABI_VERSION` 4. It also changes report provenance types and adds
30-
resolution/failure fields. The repository's `CHANGELOG.md`, under
31-
*Unreleased*, inventories the state-hash additions and report migration;
32-
the version files still say 1.3.0 until tagging. This candidate is intended
33-
for the same-version 1.4.0 pair, with regeneration and relinking as below.
30+
resolution/failure fields. The repository's
31+
[CHANGELOG.md](../../CHANGELOG.md#140--2026-10-08), under
32+
*1.4.0 — 2026-10-08*, inventories the state-hash additions and report migration.
33+
Use the same-version 1.4.0 pair, with regeneration and relinking as below.
3434

3535
## Versions
3636

‎docs/pages/release-1.4.0-sample.md‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
1-
# Planned 1.4.0 — public provenance sample {#release_140_sample}
1+
# 1.4.0 — pre-tag public provenance sample {#release_140_sample}
22

33
@tableofcontents
44

5-
This synthetic sample compares the released **1.3.0 source pair** with the
6-
**unreleased 1.4.0 candidate pair**. Both were built and installed on the same
5+
This synthetic sample compared the released **1.3.0 source pair** with the
6+
**pre-tag 1.4.0 candidate pair**. Both were built and installed on the same
77
x86-64 Ubuntu 24.04 host with GCC 13.3.0, then run through their own
88
installed `docker/entrypoint.sh` and `run_json.py`. It is a report-shape
99
example: 40 constant bars, no trades, no performance measurement and no
@@ -12,12 +12,12 @@ private source or feed.
1212
| Pair | Engine commit | Codegen commit |
1313
|---|---|---|
1414
| Released 1.3.0 sources | `ec5d8bf46210bac103870ecf6fc74865cad66c8d` | `0736180e4b1ae8068df222f72ccc6a8a64471d3f` |
15-
| Planned 1.4.0 candidate | `b3192bfc2f5a24bf4efd6d1d01e01e8fe619dfed` | `bfc4ddce453db1ba810692af9b9ba3310d87f0ac` |
15+
| Pre-tag 1.4.0 candidate | `b3192bfc2f5a24bf4efd6d1d01e01e8fe619dfed` | `bfc4ddce453db1ba810692af9b9ba3310d87f0ac` |
1616

17-
These are fresh builds from pinned source, not downloaded release binaries.
18-
Both candidate VERSION files still say 1.3.0. With
19-
`PINEFORGE_VERSION_SOURCE=FILE`, the installed candidate reports version
20-
`1.3.0` and engine commit `b3192bf`; the old build reports `1.3.0` and
17+
These were fresh builds from pinned source, not downloaded release binaries.
18+
Both candidate VERSION files said 1.3.0 at sample-build time. With
19+
`PINEFORGE_VERSION_SOURCE=FILE`, the installed candidate reported version
20+
`1.3.0` and engine commit `b3192bf`; the old build reported `1.3.0` and
2121
`ec5d8bf`. The candidate output has not been relabeled as a tagged artifact.
2222

2323
## Shared inputs

‎docs/pages/tutorial-macd.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ bash tutorial/run.sh
8383
Configures CMake (first time only), builds
8484
`tutorial/macd/strategy.so`, then runs the harness. The output below is the
8585
recorded engine v1.0.0 / codegen 1.0.0 result on the frozen feed; it has not
86-
been re-measured for planned 1.4.0:
86+
been re-measured for 1.4.0:
8787

8888
```
8989
MACD(12,26,9) on BTCUSDT 15m — 672 bars, 2026-04-29 18:15 → 2026-05-06 18:00 UTC

0 commit comments

Comments
 (0)