docs: changelog and version scoping for 1.0.1 - #158

Docs only, for the 1.0.1 pair release: codegen 1.0.1 with engine v1.0.1. No code, test, workflow, package metadata or VERSION change; the release workflow writes VERSION.

What changed

• CHANGELOG.md: ## 1.0.1 — 2026-10-02, drafted from the merged changes since v1.0.0 (docs: make README, CHANGELOG and docs true of the 1.0.0 release #154, docs(readme): name no latest version in the release note, install note and hosted-server line #155, History of user-defined objects and drawing references #156, History of arrays and matrices; int into a float field #157) and checked against main 67892cd:
  • compatibility and migration: codegen 1.0.1 supports only engine v1.0.1; regenerate the C++ and relink; the Python and JSON contract and the report keys (metrics.equity.sharpe_tv / sortino_tv included) do not change; which scripts 1.0.0 transpiled that are refused now;
  • C++ that did not compile and now compiles: the history of user-defined objects and drawings (History of user-defined objects and drawing references #156), of arrays and matrices (History of arrays and matrices; int into a float field #157), and a non-constant int given to a float field (History of arrays and matrices; int into a float field #157);
  • the one value that came out silently wrong: an int na assigned to a float field was stored as -2147483648 and is na now (History of arrays and matrices; int into a float field #157);
  • the new compile-time refusals with TradingView's codes, and the forms refused by name;
  • "Not covered": the limits both PR bodies list (those History of arrays and matrices; int into a float field #157 closed are left out).
• README.md, as its release-lane note asks: the release section (1.0.1, 2026-10-02), the baseline paragraph, the engine src/source/ link, the @pf-trace note, the clone command and its output, the timing note, the explicit-attachment section and a 1.0.1 row in the Engine pairing table. The note itself now names 1.0.1. Lines that say what changed in 1.0.0 stay. The Install note and the hosted-server line still name no version, and nothing calls a version the latest.
• CONTRIBUTING.md, AGENTS.md / CLAUDE.md (kept in step): codegen 1.0.1 pairs with engine v1.0.1 (image 1.0.1) and 1.0.0 with v1.0.0, instead of "the latest release, codegen 1.0.0".
• docs/PUBLIC_CONTRACT.md: 1.0.1 implements the 1.0 contract unchanged. docs/pine-cap-activation.md: describes 1.0.1 with engine v1.0.1.

Checked

Run on 67892cd (this branch's code) and on v1.0.0, CPython 3.14.6, Apple M4 Max:

• The engine corpus's 325 sources (as v1.0.0 pins it) and the 277 gate fixtures transpile to byte-identical C++; the 13 refused fixtures are refused with the same message.
• The largest transpilation takes 0.048 s (0.049 s on v1.0.0); the largest source is 9,869 characters. The Limits table stands.
• Probes of the refusals: a[1] + 1 and c.push(a[1]) on an array transpile on 1.0.0 (with the warning "array history indexing uses the current collection element") and are refused on 1.0.1 (CE10123); c[1].v (CE10011), c.v[1] (CE10290) and m[1].get(0, 0) are refused; (c[1]).v, (a[1]).size(), (m[1]).get(0, 0) and Cell.new(v = bar_index) transpile; (close * 2).m() still emits None.
• The @pf-trace example gives the same C++ and the /* unsupported: ta.rsi */ marker on both.
• The quick-start SMA cross transpiles to the same C++ on both. Run with engine 6b45f510 (v1.0.0 plus two docs commits; v1.0.1's code) through the engine tutorial (Linux arm64, GCC 13), it prints the README's block: 9 trades (6W / 3L), +738.20, +679.22 / -335.02, -788.79. With initial_capital=1000000, default_qty_type=strategy.fixed, default_qty_value=1 it books 13 trades.
• python -m build and twine check --strict pass.
• The 1,384-source byte identity is the two PRs' own measurement (History of user-defined objects and drawing references #156: identical to 01b4ee3; History of arrays and matrices; int into a float field #157: identical to its base in fresh processes).

No sweep: docs only.

Notes for review

• The changelog policy says to leave a planned release Unreleased until its tag exists. This section carries the planned date, 2026-10-02, because the release runs right after this merges and the sdist ships this CHANGELOG.
• The engine src/source/ link and the clone command name v1.0.1, which exists once the engine release has run; the engine releases first.

🤖 Generated with Claude Code