Skip to content

Commit 900995e

Browse files
luisleo526claude
andcommitted
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]>
1 parent 6944163 commit 900995e

6 files changed

Lines changed: 9 additions & 8 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -73,6 +73,7 @@ does not update a statically linked strategy library.
7373
`PINEFORGE_PRIVATE_FIXTURES` — the verification requires every pinned row to
7474
run: a row that skips there fails the run. Without the overlay, those rows
7575
skip in public runs and the row floors account for them.
76+
- **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.
7677

7778
[#361]: https://github.com/pineforge-4pass/pineforge-engine/pull/361
7879

‎docker/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -268,7 +268,7 @@ docker run --rm \
268268

269269
### Recorded outputs (the harness's `--outputs`)
270270

271-
This section describes unreleased support targeted for **1.5.0**. Released
271+
This section describes support released in **1.5.0**. Released
272272
1.4.0 images do not provide recorded outputs.
273273

274274
A library compiled to record outputs keeps, besides its trades, values per bar,

‎docs/outputs.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Recorded outputs
22

3-
Recorded outputs are unreleased, targeted for 1.5.0, and not part of 1.4.0.
3+
Recorded outputs are released in 1.5.0, and not part of 1.4.0.
44

55
A module can record what it computes on each bar besides its trades: values
66
kept per bar, values kept once per run, and events with an optional message.

‎docs/pages/abi-stability.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ From 1.0.0, within one `PINEFORGE_VERSION_MAJOR` (the
1717
- **`extern "C"` functions are append-only.** New functions may be added;
1818
existing ones are never removed or renamed.
1919
- **Enum values** are **stable**. New enumerators may be added; existing
20-
values never change. One exception, unreleased and targeted for 1.5.0:
20+
values never change. One exception, released in 1.5.0:
2121
`RunFailureCode` in the installed C++ header
2222
`include/pineforge/run_failure_codes.hpp` is renumbered, and 36 of the 38
2323
codes released in 1.4.0 get new numeric values (`none` and the first two
@@ -67,7 +67,7 @@ Three layers:
6767

6868
## Symbol inventory
6969

70-
The counts below include recorded outputs and describe the unreleased API targeted for 1.5.0; recorded outputs are not part of 1.4.0.
70+
The counts below include recorded outputs and describe the released 1.5.0 API; recorded outputs are not part of 1.4.0.
7171

7272
A built strategy `.so` exposes 96 compiled-strategy `PF_API` declarations
7373
(80 runtime implementations plus sixteen generated exports) plus 43 native-host
@@ -229,7 +229,7 @@ a run with no symbol data folds nothing new. The C side is append-only -- four
229229
functions, each behind its own `PINEFORGE_HAS_…_V1` probe -- so
230230
`PF_ABI_VERSION` stays 4.
231231

232-
Recorded outputs are unreleased, targeted for 1.5.0, and not part of 1.4.0.
232+
Recorded outputs are released in 1.5.0, and not part of 1.4.0.
233233

234234
Recorded outputs (lane SM-E1, `docs/outputs.md`) adds the recorder to
235235
`BacktestEngine` inside v19, without an epoch: data members outside both

‎docs/pages/index.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,7 @@ directly, so a Pine-layer symbol reaching one is a link error.
135135

136136
## API at a glance
137137

138-
The counts below include recorded outputs and describe the unreleased API targeted for 1.5.0; recorded outputs are not part of 1.4.0.
138+
The counts below include recorded outputs and describe the released 1.5.0 API.
139139

140140
The public C surface is **145 `PF_API` declarations** across the five installed headers that declare any:
141141

‎docs/pages/run-failure-codes.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ codes it tested the text alone, so a script stopped by an empty
9393

9494
The tables below list the catalog at this tree.
9595

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.
9797

9898
<!-- BEGIN generated from docker/run_failure_codes.json: python3 scripts/test_gen_run_failure_catalog_diff.py --write-docs-tables -->
9999

@@ -224,7 +224,7 @@ three: `report_post_execution_failed` (the phases after the strategy has
224224
finished), `engine_command_value_invalid` (an invalid command value the engine
225225
derived itself) and `window_pruner_unsupported` (the optimizer's trial pruner).
226226
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
228228
declares them and validates their arguments, which is all this page states
229229
about them: whether a build raises one is the build's own, and a row in the
230230
catalog is not proof that the source paths it names enforce anything.

0 commit comments

Comments
 (0)