docs: changelog and version scoping for 1.2.0

[luisleo526]

What and why

1.2.0 pairs with engine v1.2.0. The engine's pineforge.h defines
PF_CAPABILITIES_API_VERSION (1) and declares strategy_capabilities_api_version
and strategy_capabilities_receipt (pineforge-engine#332). The C++ of codegen
1.2.0 defines both functions (#167). The pair keeps PF_ABI_VERSION 4 and the
script ABI epoch engine_script_run_v19. This README becomes PyPI's long
description for 1.2.0, so the version scoping has to be right at the tag.

• CHANGELOG.md: the ## 1.2.0 — 2026-10-05 section absorbs the Unreleased notes
  and covers Emit immutable compiled execution capability receipts (capability extension v1) #167, Stable diagnostic codes, an ICU message catalog, and first error in source order #166, License: the PineForge Source License 1.0 (pineforge, LLC); investment management is commercial for every organization #168 and Linear-time diagnostic codes, the PineForge Source License 1.1, and the scoreboard README at pineforge-release 03b8dcc #171:
  • the capability receipt and what engine v1.2.0's pineforge-live does
    with it;
  • diagnostic code / args, diagnostics_catalog(), render_diagnostic(),
    the glue envelope keys, and the catalog file
    (diagnostics_catalog-v1.2.0.json on the GitHub release);
  • the first error in source order again;
  • the linear-time classification, as a security fix (denial of service via
    crafted script text; on main only, never in a release);
  • the license change;
  • the README scoreboard render;
  • compatibility and migration.
• README.md, AGENTS.md / CLAUDE.md (identical edits), CONTRIBUTING.md,
  docs/PUBLIC_CONTRACT.md and docs/pine-cap-activation.md now name 1.2.0 /
  v1.2.0 wherever they named 1.1.0 as the current release or pair. The pairing
  table gets a 1.2.0 row. Lines that say what an earlier release shipped are
  unchanged.
• README.md: the license badge read "PineForge Source 1.0". It now reads 1.1, to
  match LICENSE and the License section.
• npm/README.md lists two things the package carries since Stable diagnostic codes, an ICU message catalog, and first error in source order #166 and License: the PineForge Source License 1.0 (pineforge, LLC); investment management is commercial for every organization #168: the
  diagnostics_catalog.json export and LICENSE.
• README.md: the release sentence names 1.2.0 and renders releases[1.2.0]
  (registry baseline pineforge-parity-baseline-20261005-engine-52292db9,
  engine #339's merge, which v1.2.0 equals in behaviour: 7,970 excellent / 19
  strong of 7,989, none below strong), and the main scoreboard renders the same
  baseline, from pineforge-release facts/facts.json at 0c2f6838
  (pineforge-release fix(codegen): harden validation edge cases #28). lab facts check against that pinned file passes,
  with --github-render. CHANGELOG.md states the release's grades in its
  documentation entry, as 1.1.0's does.

Compatibility statements

• Report keys: the engine's docker/run_json.py, which the hub image runs, is
  byte for byte the same file in engine v1.1.0 and engine main 52292db9 (#339). No
  report key is added, removed or renamed. metrics.equity.sharpe_tv and
  sortino_tv (EQUITY_REPORT_KEYS) are unchanged, and the engine's ADR-0001
  keeps serialized report keys unchanged.

• The Python and JSON contract is additive. git diff v1.1.0..48e7a13 touches
  three contract files, and each change is an addition:

  • gate/glue.py adds code and args to each JSON diagnostic;
  • pineforge_codegen/errors.py adds the code and args properties;
  • pineforge_codegen/__init__.py adds the diagnostics_catalog /
    render_diagnostic import.

  No argument, result key or envelope is removed or renamed. One result
  changes: which error is raised first for a script with several errors (Stable diagnostic codes, an ICU message catalog, and first error in source order #166).

• License: 1.2.0 is the first release under the PineForge Source License 1.1
  (licensor pineforge, LLC). All 20 earlier release tags ship "PineForge Codegen
  — License", which is the PolyForm Noncommercial License 1.0.0 with PineForge's
  supplemental sections. Those releases keep that license. The changelog
  summarizes LICENSE and LEGAL.md and names LICENSE as the controlling text.

Verified

• Transpile identity, run on the Mac with CPython 3.14.6 on an Apple M4 Max.
  Each source ran in its own process, once with the v1.1.0 tree and once with
  48e7a13. The sources were the engine's 325 public corpus sources (corpus pin
  b40aa8ec) and the 277 gate fixtures. Of these, 589 transpile. For each of
  them, 1.2.0's C++ with the capability block removed equals 1.1.0's byte for
  byte, and each carries exactly one capability block. The other 13 are refused
  with the same message by both versions.
• Timing: run sequentially, each source took at most 0.054 s, so the README
  says "under 0.1 seconds".
• Tutorial, on an AWS spot box (Linux x86_64, GCC 13.3). The instance has been
  terminated.
  • Engine main 44eab7b1 with 1.2.0's quick-start C++ prints 9 trades,
    +738.20, best/worst +679.22 / -335.02, max dd -788.79 and elapsed 1.0 ms.
    With the old sizing declared it books 13 trades.
  • Engine v1.1.0 with 1.1.0's C++ prints the same, which matches the
    README.
  • The .so built against engine main's headers exports both capability
    functions.
  • 1.2.0's C++ built against v1.1.0's headers compiles without them, as the
    #ifdef guard intends.
• git diff --check origin/main is clean. Only Markdown files changed. Every
  pf: marker value comes from the facts render above.

Gate

pr-gate for (engine main 52292db9, this head 95a5314): PASS (no-improve-no-regression), experiment
exp-rel120-cgnotes-gate-20261005 (134/134 cases), candidate d8af0284 vs baseline 7161ebdc (the active
…-20261005-engine-52292db9) over population 40c482c2; eventKey
verdict-52292db9df56-95a5314bf0cf-36475251a30c, gated 2026-10-05 04:24Z.

🤖 Generated with Claude Code