Repository navigation
docs: changelog and version scoping for 1.3.0 - #180
Merged
Merged
Conversation
1.3.0 pairs only with engine v1.3.0. The changelog section takes in the Unreleased note and covers #173, #178, #179, #177, #174 and #175: the confirmed-bar receipt and what engine v1.3.0's live runner does with it, the capability receipt's request entries now read from the lowering, the order-shapes receipt, which no engine reads yet, the checked settings fix for string dropdowns with built-in constants (now supported=false where 1.2.0 wrote an integer code or published the input as supported), the PineForge Source License 1.2, and the pairing and migration steps. The Python and JSON contract is unchanged; the engine's report harness is the same file as in v1.2.0, so no report key changes. The README, AGENTS.md / CLAUDE.md, CONTRIBUTING.md, LEGAL.md, docs/PUBLIC_CONTRACT.md, docs/pine-cap-activation.md and npm/README.md name 1.3.0 where they named 1.2.0 as the current release or pair, the pairing table gets a 1.3.0 row, the "unreleased (after 1.2.0)" markers name 1.3.0, and the license badge reads 1.2. The release scoreboard sentence and the pf markers are left to the release lane. Measured for 1.3.0: the engine's 325 corpus sources and the 277 gate fixtures, each in a fresh process, transpile to 1.2.0's C++ byte for byte once the confirmed-bar and order-shapes functions are removed (13 refusals, same messages), with transpile_full results and transpile_json envelopes without cpp equal to 1.2.0's, each in under 0.1 s on CPython 3.14.6 on an Apple M4 Max. The tutorial run of the quick-start C++ against engine main 7a1f01c0 (Linux x86_64, GCC 13) prints 9 trades and +738.20, and 13 trades with the old sizing declared, as 1.2.0 with engine v1.2.0 does. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
…e facts tokens The README's release sentence moves to the releases[1.3.0] tokens and its main-scoreboard lines re-render, and the 1.3.0 changelog says which registry baseline grades the release and why that baseline is the release's code, all rendered from pineforge-release facts/facts.json at ff21de0 (#32). Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The release workflow writes only
VERSION; this docs-only change supplies the1.3.0 changelog section and names 1.3.0 where the documentation names the
current release or pair, so the README that PyPI shows for 1.3.0 is right at
the tag.
What changed
CHANGELOG.md:## 1.3.0 — 2026-10-06, taking in the Unreleased note. Itcovers Confirmed-bar receipt: versioned metadata from lowering decisions #173 (the confirmed-bar receipt; the capability receipt's request
entries now read their timeframe, Heikin-Ashi flag and feed from the
lowering), Order-shapes receipt: lowered order-call facts for closing-time order processing #178 (the order-shapes receipt, which no engine reads yet), Checked settings: string dropdowns with built-in display constants no longer break the settings receipt #179
(a string dropdown with a built-in constant no longer breaks the checked
settings; such an input is now
"supported": falsewith no options, where1.2.0 wrote the constant's integer code or published the input as
supported), License: the PineForge Source License 1.2; a funded-trader challenge, evaluation or simulated account is not Personal Trading and is investment capital #177 (the PineForge Source License 1.2), docs: render the active scoreboard from the facts tokens at pineforge-release 3e39d64 #174 (the scoreboard
render) and CI: install the codegen docs-only gate, with a same-repository guard for forks #175 (repository CI only), with the pairing and migration
steps. Codegen 1.3.0 supports only engine
v1.3.0; enginev1.3.0's<pineforge/pineforge.h>isv1.2.0's (C ABI 4,engine_script_run_v19).src/source/link,@pf-tracenote, timing note, clone command and itsoutput, "This section describes …", license badge 1.2), AGENTS.md and
CLAUDE.md (identical edits), CONTRIBUTING.md, LEGAL.md (1.3.0 is the first
release under 1.2), docs/PUBLIC_CONTRACT.md (the "unreleased (after 1.2.0)"
markers name 1.3.0; the catalog asset is
diagnostics_catalog-v1.3.0.json),docs/pine-cap-activation.md and npm/README.md. Lines that say what an
earlier release shipped stay. The release scoreboard sentence and the pf
markers are left to the release lane.
Compatibility
removed or renamed. Since 1.2.0 the package's code changed only under
pineforge_codegen/codegen/;__init__.py,errors.py,gate/glue.pyandthe diagnostics catalog (628 codes) are 1.2.0's files.
docker/run_json.pyis the same file in enginev1.3.0as inv1.2.0, so no report key is added, removed or renamed;metrics.equity.sharpe_tv/sortino_tv(EQUITY_REPORT_KEYS) areunchanged, and the engine's ADR-0001 keeps serialized report keys as they
are.
(a proprietary-trading firm's or funded-trader program's account, including
a challenge, evaluation or simulated account, is not Personal Trading, and
its capital, real or simulated, is investment capital). 1.2.0 shipped under
1.1; releases up to and including 1.1.0 under "PineForge Codegen —
License".
LICENSEis the controlling text.Verified
transpiled in a fresh process with 1.2.0 and with this branch: with the
confirmed-bar and order-shapes functions removed, 589 of 589 C++ files are
byte-identical and the 13 expected refusals keep their messages; for all
602,
transpile_full()'s result and thetranspile_jsonenvelope withoutcppare identical.0.065 s) on CPython 3.14.6 on an Apple M4 Max.
main7a1f01c0 (Linux x86_64, GCC 13): 9 trades, +738.20; 13 trades withthe old sizing declared. Codegen 1.2.0 with engine
v1.2.0prints the same.git diff --checkis clean, and the codegen docs-only classifier acceptsthe diff (
codegen-docs-only/v1).Not changed here: the
pyproject.tomlcomment still names license 1.1 (notdocs-only).
Release grades (second commit)
The README's release sentence moves to the
releases[1.3.0]tokens, its main-scoreboard lines re-render, and the changelog says which registry baseline grades 1.3.0, all rendered from pineforge-releasefacts/facts.jsonat ff21de0 (#32): 7,982 excellent / 7 strong of 7,989 graded probes, 0 below strong, on engine 7a1f01c0 and this repository at 3e50082 (#178 adds only receipt functions; the rest is documentation).lab facts checkand--github-renderpass.Gate
Codegen docs-only basis (
codegen-docs-only/v1, 9 Markdown files): receipt recorded for this head before the push (PASS (docs-only), engine 7a1f01c0 / codegen d20a02d); no sweep. The CIgatejob posts the required status.🤖 Generated with Claude Code