Skip to content

docs: changelog and version scoping for 1.3.0 - #180

Merged
luisleo526 merged 2 commits into
mainfrom
rel/1.3.0-notes
Oct 6, 2026
Merged

luisleo526 merged 2 commits into
mainfrom
rel/1.3.0-notes

Conversation

@luisleo526

Copy link
Copy Markdown
Contributor

The release workflow writes only VERSION; this docs-only change supplies the
1.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

Compatibility

  • Python and JSON contract: no argument, result key or envelope is added,
    removed or renamed. Since 1.2.0 the package's code changed only under
    pineforge_codegen/codegen/; __init__.py, errors.py, gate/glue.py and
    the diagnostics catalog (628 codes) are 1.2.0's files.
  • Report keys: the engine's docker/run_json.py is the same file in engine
    v1.3.0 as in v1.2.0, so no report key is added, removed or renamed;
    metrics.equity.sharpe_tv / sortino_tv (EQUITY_REPORT_KEYS) are
    unchanged, and the engine's ADR-0001 keeps serialized report keys as they
    are.
  • License: 1.3.0 is the first release under the PineForge Source License 1.2
    (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". LICENSE is the controlling text.

Verified

  • The engine's 325 public corpus sources and the 277 gate fixtures, each
    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 the transpile_json envelope without
    cpp are identical.
  • Each of the 602 sources is transpiled or refused in under 0.1 s (max
    0.065 s) on CPython 3.14.6 on an Apple M4 Max.
  • The engine tutorial with the quick-start C++ of this branch against engine
    main 7a1f01c0 (Linux x86_64, GCC 13): 9 trades, +738.20; 13 trades with
    the old sizing declared. Codegen 1.2.0 with engine v1.2.0 prints the same.
  • git diff --check is clean, and the codegen docs-only classifier accepts
    the diff (codegen-docs-only/v1).

Not changed here: the pyproject.toml comment still names license 1.1 (not
docs-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-release facts/facts.json at 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 check and --github-render pass.

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 CI gate job posts the required status.

🤖 Generated with Claude Code

luisleo526 and others added 2 commits October 6, 2026 09:53
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]>
@luisleo526
luisleo526 merged commit cb5eb94 into main Oct 6, 2026
5 checks passed
@luisleo526
luisleo526 deleted the rel/1.3.0-notes branch October 6, 2026 04:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant