Skip to content

Commit cca621c

Browse files
luisleo526claude
andcommitted
docs: release notes and version scoping for v1.0.1
v1.0.1 is a documentation-only release that pairs with pineforge-codegen 1.0.1 (codegen #156, #157: history reads of objects, drawings, arrays and matrices whose C++ did not compile now compile, and an int na given to a float field reads na). Since v1.0.0 only Markdown changed (#309, #310): no file under src/, include/, cmake/ or examples/, no CMake file, and docker/run_json.py is unchanged, so the C ABI, the script ABI epoch and the JSON report keys are v1.0.0's. - CHANGELOG.md: "1.0.1 — 2026-10-02". - README.md: front door 1 and the runtime-not-compiler line install pineforge-codegen==1.0.1; the prebuilt library names the v1.0.1 tarballs; the pairing sentence, the scoreboard, the benchmark line and the Releases list name 1.0.1. The MCP image line names no version (its engine_info tool reports it), as codegen #155 did for its hosted-server line. - docs/pages/install.md: the v1.0.1 tarballs and the hub tag engine1.0.1-codegen1.0.1. - docs/pages/public-contract.md: 1.0.1's release line, and engine v1.0.1 with codegen 1.0.1 among the supported pairs. Lines that state what v1.0.0 or codegen 1.0.0 shipped or did (coverage, ABI history, the version.h and find_package examples, the hub 1.0.0 image's tutorial numbers) stay. Replaces text introduced by c5383e6 (#309): README.md's "The image bundles engine v1.0.0 with codegen 1.0.0." and public-contract.md's release line, which now runs on into 1.0.1's. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
1 parent 6b45f51 commit cca621c

4 files changed

Lines changed: 53 additions & 25 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,31 @@ 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+
## 1.0.1 — 2026-10-02
9+
10+
A documentation-only release that pairs with pineforge-codegen 1.0.1, the pair
11+
the release hub's image `ghcr.io/pineforge-4pass/pineforge-release:1.0.1`
12+
carries. Since v1.0.0 no file under `src/`, `include/`, `cmake/` or
13+
`examples/`, no CMake file and nothing under `docker/` but its README changed:
14+
the library, the C ABI (`PF_ABI_VERSION` 4), the native C++ API, the script ABI
15+
epoch `engine_script_run_v19` and its state-hash values, and the JSON report
16+
keys of `docker/run_json.py` (`metrics.equity.sharpe_tv` / `sortino_tv`
17+
included) are v1.0.0's. The GitHub release attaches the three prebuilt
18+
tarballs, `pineforge-v1.0.1-linux-x86_64.tar.gz`,
19+
`pineforge-v1.0.1-linux-aarch64.tar.gz` and
20+
`pineforge-v1.0.1-macos-universal.tar.gz`, each with a `.sha256`.
21+
22+
- **Why a release.** From 1.0.0 the engine and pineforge-codegen release one
23+
version number, and codegen 1.0.1 fixes C++ that did not compile and a value
24+
that came out silently wrong (its
25+
[changelog](https://github.com/pineforge-4pass/pineforge-codegen-oss/blob/main/CHANGELOG.md)).
26+
Regenerate strategy C++ with codegen 1.0.1 and relink it against v1.0.1's
27+
headers and `libpineforge.a`: the pair changed, though no ABI number did.
28+
- **Documentation.** The README, the docs pages and this changelog describe
29+
the v1.0.0 release (#309). The docs no longer point at the retired Python
30+
`pineforge-live` runtime; the native `pineforge-live` runner in `runner/`
31+
replaces it (#310).
32+
833
## 1.0.0 — 2026-09-30
934

1035
The first stable release under semantic versioning. From it on the engine and

‎README.md‎

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ PineForge is a C++17 engine for backtesting and forward execution, with a C ABI
2929
1. **A generic kernel** — a Pine-agnostic backtest and forward-execution state machine: order matching and fills, sizing, margin and settlement, the bar magnifier, indicator classes, `request.security()`, time and session math. Some TradingView-shaped names survive in its archive, each ruled in [ADR 0001](docs/adr/0001-kernel-adapter-boundary.md) and held there by `scripts/check_kernel_residuals.py`.
3030
2. **A source-adapter parity runtime** (`src/source/` and `src/compat/pine/`, `PineExecutionAdapter` + `PineStrategyHost`) — maps Pine/TradingView execution semantics onto that kernel. This is where TradingView parity lives.
3131

32-
The separate PineForge compiler, [`pineforge-codegen`](https://github.com/pineforge-4pass/pineforge-codegen-oss), translates a PineScript v6 script into a C++ strategy that attaches the engine's Pine execution adapter (its release 1.0.0 does; 0.10.4 predates the adapter); it owns translation, not execution semantics. TradingView comparisons measure this Pine path under the tested configurations. The [order model](docs/pages/fill-model.md) describes the current submodels and the remaining migration work; [Architecture](#architecture-kernel-vs-parity) states the boundary.
32+
The separate PineForge compiler, [`pineforge-codegen`](https://github.com/pineforge-4pass/pineforge-codegen-oss), translates a PineScript v6 script into a C++ strategy that attaches the engine's Pine execution adapter (its releases 1.0.0 and 1.0.1 do; 0.10.4 predates the adapter); it owns translation, not execution semantics. TradingView comparisons measure this Pine path under the tested configurations. The [order model](docs/pages/fill-model.md) describes the current submodels and the remaining migration work; [Architecture](#architecture-kernel-vs-parity) states the boundary.
3333

3434
- **Proven, not promised.** All 7,989 graded probes — 309 open reference strategies, 680 community-shared scripts and 61 probe scripts the maintainers wrote, on 18 market/timeframe lanes — grade *excellent* or *strong* against TradingView's own trade lists: **7,905 excellent, 84 strong, zero below strong**. The graded probes' TradingView trade lists hold 4,776,328 trades; 17 probes with TradingView-side defects are excluded.
3535
- **Open runtime.** The engine and native live runner are Apache-2.0. The separately distributed [PineForge compiler](https://github.com/pineforge-4pass/pineforge-codegen-oss/blob/main/LICENSE) uses PolyForm Noncommercial terms with additional personal-trading permission; commercial use requires a separate license. Public reference strategies, benchmarks and validation tooling are available in their respective repositories; the community-script test set is not redistributed.
@@ -62,7 +62,7 @@ For Cursor, which expands `${workspaceFolder}`, or any MCP client (in Claude Des
6262
}
6363
```
6464

65-
Then ask: *"Fetch BTC/USDT 15m for the last 90 days and backtest this strategy"* — the container transpiles Pine → C++ with the bundled [`pineforge-codegen`](https://github.com/pineforge-4pass/pineforge-codegen-oss), compiles, runs, and hands the agent the trade list. The image bundles engine v1.0.0 with codegen 1.0.0. Your Pine and data stay on your machine; only the Binance tools (`fetch_binance_ohlcv`, `binance_symbols`) call out, to Binance's public API. Mount a directory at `/work`; `-i` is required and `-t` must not be added (a TTY corrupts the JSON-RPC stream).
65+
Then ask: *"Fetch BTC/USDT 15m for the last 90 days and backtest this strategy"* — the container transpiles Pine → C++ with the bundled [`pineforge-codegen`](https://github.com/pineforge-4pass/pineforge-codegen-oss), compiles, runs, and hands the agent the trade list. The image is built on the [`pineforge-release`](https://github.com/pineforge-4pass/pineforge-release) image, which ships a released engine and codegen pair; its `engine_info` tool reports the image's version. Your Pine and data stay on your machine; only the Binance tools (`fetch_binance_ohlcv`, `binance_symbols`) call out, to Binance's public API. Mount a directory at `/work`; `-i` is required and `-t` must not be added (a TTY corrupts the JSON-RPC stream).
6666

6767
| Ask | Tool |
6868
|---|---|
@@ -90,7 +90,7 @@ Prerequisites: CMake ≥ 3.16 to build (the verifier and `ctest --test-dir` need
9090

9191
### Prebuilt library
9292

93-
The [v1.0.0 release](https://github.com/pineforge-4pass/pineforge-engine/releases/tag/v1.0.0) attaches the library prebuilt: `pineforge-v1.0.0-linux-x86_64.tar.gz`, `pineforge-v1.0.0-linux-aarch64.tar.gz` and `pineforge-v1.0.0-macos-universal.tar.gz`, each with a `.sha256`. Each unpacks to one directory holding what the install above writes (the two archives, `include/pineforge/` and the `find_package(PineForge)` config) plus `LICENSE`, `NOTICE` and `VERSION`; point `CMAKE_PREFIX_PATH` at it. The package asks for Eigen 3.3+: install it on Linux, while the macOS tarball carries Eigen 3.4.0 ([install guide](docs/pages/install.md)).
93+
The [v1.0.1 release](https://github.com/pineforge-4pass/pineforge-engine/releases/tag/v1.0.1) attaches the library prebuilt: `pineforge-v1.0.1-linux-x86_64.tar.gz`, `pineforge-v1.0.1-linux-aarch64.tar.gz` and `pineforge-v1.0.1-macos-universal.tar.gz`, each with a `.sha256`. Each unpacks to one directory holding what the install above writes (the two archives, `include/pineforge/` and the `find_package(PineForge)` config) plus `LICENSE`, `NOTICE` and `VERSION`; point `CMAKE_PREFIX_PATH` at it. The package asks for Eigen 3.3+: install it on Linux, while the macOS tarball carries Eigen 3.4.0 ([install guide](docs/pages/install.md)).
9494

9595
### Embedded in your own harness
9696

@@ -133,14 +133,14 @@ TradingView's execution semantics on top of the kernel; this is the path the
133133
validation scoreboard below measures.
134134
135135
```bash
136-
pip install "pineforge-codegen==1.0.0"
136+
pip install "pineforge-codegen==1.0.1"
137137
python3 -c "from pathlib import Path; from pineforge_codegen import transpile; Path('generated.cpp').write_text(transpile(Path('strategy.pine').read_text(), filename='strategy.pine'))"
138138
c++ -std=c++17 -O2 -ffp-contract=off -fbracket-depth=1024 -shared -fPIC generated.cpp \
139139
-Wl,-force_load,/usr/local/lib/libpineforge.a -o strategy.so
140140
python3 scripts/run_strategy.py . --ohlcv tutorial/data/btcusdt_15m_7d.csv --no-trim-output # or drive it over the C ABI
141141
```
142142

143-
Run it from the engine checkout, with `strategy.pine` there, after the `cmake --install` above (with a prebuilt tarball instead, add `-I<its directory>/include` and link its `lib/libpineforge.a`). Engine v1.0.0 pairs with pineforge-codegen 1.0.0; codegen 0.10.4 emits C++ for engine v0.13.1, which v1.0.0's headers no longer compile. Neither codegen release has a command-line entry point, so transpile through `transpile()`. The compile line is macOS/Clang's: on Linux link `-Wl,--whole-archive /usr/local/lib/libpineforge.a -Wl,--no-whole-archive`, and drop `-fbracket-depth` for GCC. Linking the whole archive is what puts the runtime's C exports (`pf_abi_version`, the `strategy_stream_*` family) in the module; a script that uses `matrix.*` also needs Eigen's include directory.
143+
Run it from the engine checkout, with `strategy.pine` there, after the `cmake --install` above (with a prebuilt tarball instead, add `-I<its directory>/include` and link its `lib/libpineforge.a`). Engine v1.0.1 pairs with pineforge-codegen 1.0.1, as v1.0.0 does with 1.0.0; codegen 0.10.4 emits C++ for engine v0.13.1, which the headers of v1.0.0 and v1.0.1 no longer compile. No codegen release has a command-line entry point, so transpile through `transpile()`. The compile line is macOS/Clang's: on Linux link `-Wl,--whole-archive /usr/local/lib/libpineforge.a -Wl,--no-whole-archive`, and drop `-fbracket-depth` for GCC. Linking the whole archive is what puts the runtime's C exports (`pf_abi_version`, the `strategy_stream_*` family) in the module; a script that uses `matrix.*` also needs Eigen's include directory.
144144

145145
### 2. C++, against the kernel
146146

@@ -226,7 +226,7 @@ live behavior or real broker fills.
226226

227227
## Validation scoreboard
228228

229-
**Measured 2026-09-29** on engine `35db01c8` with codegen-oss `70c2b4af` (the maintainers' baseline `pineforge-parity-baseline-20260929-engine-35db01c8`): **7,989 graded probes, 7,905 excellent + 84 strong**, none below *strong*, across 18 market/timeframe lanes. Their TradingView trade lists hold 4,776,328 trades. Engine v1.0.0, released 2026-09-30 from main `133f5714`, includes `35db01c8`, codegen 1.0.0 carries `70c2b4af`'s code, and the releases changed no grade.
229+
**Measured 2026-09-29** on engine `35db01c8` with codegen-oss `70c2b4af` (the maintainers' baseline `pineforge-parity-baseline-20260929-engine-35db01c8`): **7,989 graded probes, 7,905 excellent + 84 strong**, none below *strong*, across 18 market/timeframe lanes. Their TradingView trade lists hold 4,776,328 trades. Engine v1.0.0, released 2026-09-30 from main `133f5714`, includes `35db01c8`, codegen 1.0.0 carries `70c2b4af`'s code, and the releases changed no grade. The 1.0.1 releases (2026-10-02) were not re-graded: engine v1.0.1 changes only documentation since v1.0.0, and codegen 1.0.1 transpiles the public corpus and the 1,384 real-world strategy sources its pull requests measured to the same C++ as 1.0.0.
230230

231231
| Board | Test set | Result |
232232
|---|---|---|
@@ -333,7 +333,7 @@ Slot 192 has no PyneCore trade list: PyneSys rejects its source (`"Empty documen
333333
- **Tiers:** they now come from the canonical `scripts/verify_corpus.py::analyze_strategy` rubric. The old table graded a different 100-strategy population with `compare.py`'s own copy of the rubric, which had drifted from the canonical one and no longer parsed the current tape format.
334334
- **Speed:** that table was timed on the Apple M4 Max. The 2026-06-11 engine, rebuilt on the AWS host and timed in the same window, runs the three probes both populations share 4–8× faster than `35db01c8` ([provenance](benchmarks/results/speed.md#provenance)).
335335

336-
Last refresh **2026-09-29** (engine `35db01c8`, codegen `121b3e6a`, PyneCore 6.10.3, PineTS 0.9.34, vectorbt 0.28.2; timed on an AWS c7a.8xlarge running Ubuntu 24.04); v1.0.0 was released after it, and neither the tiers nor the timings were re-measured on the release. Per-strategy table: [`benchmarks/results/summary.md`](benchmarks/results/summary.md). Population manifest: [`benchmarks/results/selection.md`](benchmarks/results/selection.md). Method, fairness and the reproduction recipe: [`benchmarks/README.md`](benchmarks/README.md).
336+
Last refresh **2026-09-29** (engine `35db01c8`, codegen `121b3e6a`, PyneCore 6.10.3, PineTS 0.9.34, vectorbt 0.28.2; timed on an AWS c7a.8xlarge running Ubuntu 24.04); v1.0.0 and v1.0.1 were released after it, and neither the tiers nor the timings were re-measured on them. Per-strategy table: [`benchmarks/results/summary.md`](benchmarks/results/summary.md). Population manifest: [`benchmarks/results/selection.md`](benchmarks/results/selection.md). Method, fairness and the reproduction recipe: [`benchmarks/README.md`](benchmarks/README.md).
337337

338338
---
339339

@@ -425,7 +425,7 @@ ground written for an agent that has been handed a brief in this repository.
425425
- `benchmarks/` — the cross-engine comparison harness (PineForge, PyneCore, PineTS, vectorbt) and the throughput package.
426426
- `scripts/` — `run_corpus.sh`, `verify_corpus.py`, `run_strategy.py` (load any `.so` via ctypes), `regen_corpus_cpp.sh`, `coverage.sh`.
427427

428-
**This is the runtime, not the compiler.** The PineScript → C++ transpiler is [`pineforge-codegen`](https://github.com/pineforge-4pass/pineforge-codegen-oss) (its release 1.0.0, `pip install "pineforge-codegen==1.0.0"`, pairs with engine v1.0.0), bundled with the runtime in the [`pineforge-release`](https://github.com/pineforge-4pass/pineforge-release) image that the MCP server builds on. **It is a backtest engine, not a chart:** `plot` and `bgcolor` compile and draw nothing; `line`, `box`, `label` and `linefill` objects are kept as data the script can read back, never rendered. **It is not a TradingView clone:** where TradingView's behaviour is undocumented or platform-specific (the bar magnifier's intrabar path, float ordering) PineForge chooses deterministic rules and documents them; where it converges, it converges exactly.
428+
**This is the runtime, not the compiler.** The PineScript → C++ transpiler is [`pineforge-codegen`](https://github.com/pineforge-4pass/pineforge-codegen-oss) (its release 1.0.1, `pip install "pineforge-codegen==1.0.1"`, pairs with engine v1.0.1), bundled with the runtime in the [`pineforge-release`](https://github.com/pineforge-4pass/pineforge-release) image that the MCP server builds on. **It is a backtest engine, not a chart:** `plot` and `bgcolor` compile and draw nothing; `line`, `box`, `label` and `linefill` objects are kept as data the script can read back, never rendered. **It is not a TradingView clone:** where TradingView's behaviour is undocumented or platform-specific (the bar magnifier's intrabar path, float ordering) PineForge chooses deterministic rules and documents them; where it converges, it converges exactly.
429429

430430
Full coverage map — every TA class, every order primitive, every `request.security()` semantic, and what is deliberately not implemented: [`docs/coverage.md`](docs/coverage.md).
431431

@@ -604,6 +604,7 @@ Documentation: [C ABI reference](https://cdocs.pineforge.dev) · [Getting starte
604604

605605
## Releases
606606

607+
- **v1.0.1** (2026-10-02) — documentation only: no library, C ABI, script ABI or report change since v1.0.0. It pairs with pineforge-codegen 1.0.1, which compiles history reads of objects, drawings, arrays and matrices where 1.0.0's C++ did not, and stores an int `na` given to a `float` field as `na` (the hub image `pineforge-release:1.0.1` carries the pair); regenerate and relink. See [CHANGELOG.md](CHANGELOG.md).
607608
- **v1.0.0** (2026-09-30) — the first stable release under semantic versioning; from it the engine and pineforge-codegen release one version (codegen 1.0.0; the hub image `pineforge-release:1.0.0` carries the pair). Every change since v0.13.1: C ABI version 4, the native kernel and its C host API, the script ABI epoch v19. What a 0.13.1 user must act on is in [CHANGELOG.md](CHANGELOG.md); what 1.x promises is the [public contract](docs/pages/public-contract.md).
608609
- **v0.13.1** (2026-09-06) — the parity campaign's rounds 7–11: TradingView's broker rules pinned with sensor exports and landed with replay tests — ten-significant-digit money, trailing-stop restarts, zero-offset trails, declined-reversal bracket legs, the surviving `strategy.close`, sparse `ta.atr`/`ta.tr`, same-bar market transactions, early-close higher-timeframe buckets; the corpus keeps every USDT-quoted book in USDT. Closed test 3,880/3,881; corpus 309/309. ABI v3, 32 symbols, 198 tests.
609610
- **v0.13.0** (2026-09-05) — native higher-timeframe and auxiliary `request.security()` feeds, TradingView's range-end close (ABI v3, `pf_trade_t::open_at_end`), the market-entry affordability gate for fixed, cash and explicit-quantity entries, `na` handling in the extremes and `ta.stdev`.

‎docs/pages/install.md‎

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -53,24 +53,24 @@ ${prefix}/
5353
## Prebuilt tarballs
5454

5555
A release attaches the library prebuilt to its GitHub release. For
56-
[v1.0.0](https://github.com/pineforge-4pass/pineforge-engine/releases/tag/v1.0.0)
57-
they are `pineforge-v1.0.0-linux-x86_64.tar.gz`,
58-
`pineforge-v1.0.0-linux-aarch64.tar.gz` and
59-
`pineforge-v1.0.0-macos-universal.tar.gz` (one archive for arm64 and x86_64),
56+
[v1.0.1](https://github.com/pineforge-4pass/pineforge-engine/releases/tag/v1.0.1)
57+
they are `pineforge-v1.0.1-linux-x86_64.tar.gz`,
58+
`pineforge-v1.0.1-linux-aarch64.tar.gz` and
59+
`pineforge-v1.0.1-macos-universal.tar.gz` (one archive for arm64 and x86_64),
6060
each with a `.sha256`. A tarball unpacks to one directory,
61-
`pineforge-v1.0.0-<platform>/`, laid out as the install above (both archives,
61+
`pineforge-v1.0.1-<platform>/`, laid out as the install above (both archives,
6262
`include/pineforge/`, `lib/cmake/PineForge/`), with `LICENSE`, `NOTICE` and
6363
`VERSION` beside them:
6464

6565
```bash
66-
curl -LO https://github.com/pineforge-4pass/pineforge-engine/releases/download/v1.0.0/pineforge-v1.0.0-linux-x86_64.tar.gz
67-
curl -LO https://github.com/pineforge-4pass/pineforge-engine/releases/download/v1.0.0/pineforge-v1.0.0-linux-x86_64.tar.gz.sha256
68-
sha256sum -c pineforge-v1.0.0-linux-x86_64.tar.gz.sha256 # macOS: shasum -a 256 -c
69-
tar -xzf pineforge-v1.0.0-linux-x86_64.tar.gz
66+
curl -LO https://github.com/pineforge-4pass/pineforge-engine/releases/download/v1.0.1/pineforge-v1.0.1-linux-x86_64.tar.gz
67+
curl -LO https://github.com/pineforge-4pass/pineforge-engine/releases/download/v1.0.1/pineforge-v1.0.1-linux-x86_64.tar.gz.sha256
68+
sha256sum -c pineforge-v1.0.1-linux-x86_64.tar.gz.sha256 # macOS: shasum -a 256 -c
69+
tar -xzf pineforge-v1.0.1-linux-x86_64.tar.gz
7070
```
7171

7272
A CMake consumer finds it with
73-
`-DCMAKE_PREFIX_PATH=$PWD/pineforge-v1.0.0-linux-x86_64` (@ref integration_cmake).
73+
`-DCMAKE_PREFIX_PATH=$PWD/pineforge-v1.0.1-linux-x86_64` (@ref integration_cmake).
7474
The package config asks for Eigen 3.3 or later (`find_dependency(Eigen3 3.3)`):
7575
install it on Linux (`libeigen3-dev` on Debian and Ubuntu); the macOS tarball
7676
carries Eigen 3.4.0's headers and CMake package, which the same prefix finds.
@@ -90,7 +90,7 @@ with the hub's own version (`X.Y.Z`, `X.Y`, and `latest` for the newest stable
9090
one), with `engine<E>-codegen<C>` naming the pair it carries, and with
9191
`sha-<short>`; a release candidate gets no `latest`. Pin the
9292
`engine<E>-codegen<C>` tag of the engine release you build against: for
93-
v1.0.0, `engine1.0.0-codegen1.0.0`, the image the hub also tags `1.0.0`.
93+
v1.0.1, `engine1.0.1-codegen1.0.1`, the image the hub also tags `1.0.1`.
9494

9595
```bash
9696
docker pull ghcr.io/pineforge-4pass/pineforge-release:latest

0 commit comments

Comments
 (0)