docs: release notes and version scoping for v1.1.0

[luisleo526]

Release notes and version scoping for engine v1.1.0. The release workflow writes only VERSION; this docs-only change supplies the CHANGELOG section, moves the version-specific lines to 1.1.0 as #311 did for 1.0.1, and amends the public contract's state-hash rule. It merges after #325 and #327 and folds their CHANGELOG entries into 1.1.0.

1.1.0 is a minor release because #317 adds six functions to the C ABI: <pineforge/pineforge.h> declares strategy_settings_api_version, strategy_create_checked, strategy_set_input_checked, strategy_set_override_checked, strategy_get_effective_settings and run_backtest_full_checked, which a strategy generated by pineforge-codegen 1.1.0 exports. It pairs with pineforge-codegen 1.1.0 (hub image ghcr.io/pineforge-4pass/pineforge-release:1.1.0). It also fixes the v1.0.0 and v1.0.1 stream request.security known issue (#325).

Changes

• CHANGELOG.md: ## 1.1.0 — 2026-10-04, with no ## Unreleased left: a lead paragraph (what the release adds, the pair, the three tarballs, what stays), one bullet per change a user can observe since v1.0.1 (docs: state the merge rule's zero-score outcome as it is now #312, grader: resolve distinct-entry identity against every TradingView entry key #313, Pine adapter: eight parity changes, 35 probes strong to excellent #315, Pine adapter: resolved margin-call fills and pyramiding-one admission, 3 probes strong to excellent #316, Checked strategy settings and contained C ABI exceptions #317, Render parity scoreboard docs from release-hub facts #318, Exact tick-built bar volume and a genuine-tick equivalence harness #319, Live runner: normalized feed input and per-action webhook routing #320, Report-only native intraday terminal quote #321, Apply syminfo.mincontract as the engine's lot grid in the Docker harness #322, Document the stream request.security known issue (v1.0.0, v1.0.1) #323, docs: keep the parity and trades badges out of a raw HTML block #324, Confirmed-bar streams compute what the batch computes #325, Install other symbols' bars for request.security in the Docker harness (--symbol-feeds) #327), each linking its PR, and the subsections State hashes, Report keys and Migration. Confirmed-bar streams compute what the batch computes #325's and Install other symbols' bars for request.security in the Docker harness (--symbol-feeds) #327's Unreleased bullets are folded into 1.1.0.
• README.md: pineforge-codegen==1.1.0 (two places), the v1.1.0 tarballs, the pairing sentence, the benchmark refresh line, the release scoreboard sentence with releases[1.1.0] markers, the stream known issue marked fixed in 1.1.0 (Confirmed-bar streams compute what the batch computes #325), and a v1.1.0 line in Releases. The public corpus sweep's "311 excellent + 1 declared anomaly" is scoped to the v1.0.1 library it was measured on. Fact markers rendered from the facts export that maps releases[1.1.0] to pineforge-parity-baseline-20261004-engine-7b596622 (7,951 excellent / 38 strong of 7,989); the active scoreboard markers move to the same baseline, in README.md and docs/pages/contributing-llm.md.
• docs/pages/install.md: the v1.1.0 tarballs and the hub tag engine1.1.0-codegen1.1.0.
• docs/pages/public-contract.md: 1.1.0's release line; engine v1.1.0 with codegen 1.1.0 among the supported pairs; the four C-boundary rows planned for 1.1.0 (C-SURFACE-2) stated as not in it; and the state-hash rule amended (the semver rule is unchanged): a minor release may add a field to the hashed state when every trade and every other report field stays byte-identical, with unchanged domain tags and a CHANGELOG State hashes disclosure; any other change to what a state hash folds is a new epoch and a major release; Pine adapter: resolved margin-call fills and pyramiding-one admission, 3 probes strong to excellent #316 is named as the first use.
• docs/pages/streaming.md: the stream request.security known issue affected v1.0.0 and v1.0.1 and is fixed in 1.1.0 (Confirmed-bar streams compute what the batch computes #325).

Lines that state what an earlier version shipped or did stay as they are (the 1.0.1 and 1.0.0 CHANGELOG sections, the v1.0.1 Releases line, VERSION, the release-version test data).

Report keys (docker/run_json.py, v1.0.1 → v1.1.0)

• No key removed or renamed; EQUITY_REPORT_KEYS unchanged (metrics.equity.sharpe_tv / sortino_tv).
• Added applied_runtime.syminfo = {"qty_step": <float>, "mincontract": <float>} (Apply syminfo.mincontract as the engine's lot grid in the Docker harness #322), present only when the --syminfo / PINEFORGE_SYMINFO file carries a valid mincontract, absent otherwise.
• Added applied_runtime.symbol_feeds = {"canonicalization": "pf-symbol-feed-barc-close-le-v1", "symbols": {"<symbol string>": {"facts": {...}, "feeds": {"<timeframe>": {"bars": <int>, "first_ts": <int>, "last_ts": <int>, "source_values_sha256": "<hex>"}}}}} (Install other symbols' bars for request.security in the Docker harness (--symbol-feeds) #327), present only when --symbol-feeds / PINEFORGE_SYMBOL_FEEDS installed at least one symbol, absent otherwise.
• fingerprint.provenance.runtime mirrors applied_runtime, so a run with either key has its own fingerprint; a run without them is unchanged for the same library apart from elapsed_seconds.
• Failure output: the existing one-line {"engine":"pineforge","error":...}, harness exit 1, image entrypoint exit 4, with new messages: syminfo.mincontract must be a positive finite number, got <json>, the strategy library has no strategy_set_syminfo_metadata, so syminfo.mincontract cannot be applied, and the --symbol-feeds: … family.

Notes for the maintainers

• State hashes: the contract's state-hash rule is amended here (recipe only), as ruled for 1.1.0. Pine adapter: eight parity changes, 35 probes strong to excellent #315, Pine adapter: resolved margin-call fills and pyramiding-one admission, 3 probes strong to excellent #316, Exact tick-built bar volume and a genuine-tick equivalence harness #319 and Confirmed-bar streams compute what the batch computes #325 each add hashed fields and none removes, renames or re-encodes one; the domain tags are unchanged (scripts/check_aggregate_cpp_versions.py and scripts/check_broker_state_hash_coverage.py pass). Only Pine adapter: resolved margin-call fills and pyramiding-one admission, 3 probes strong to excellent #316 has a witness that isolates its addition (hash moved, trades identical); the fields Pine adapter: eight parity changes, 35 probes strong to excellent #315, Exact tick-built bar volume and a genuine-tick equivalence harness #319 and Confirmed-bar streams compute what the batch computes #325 add come with those PRs' own behaviour changes. Pine adapter: eight parity changes, 35 probes strong to excellent #315's range-end equity-extreme change is a behaviour change and is listed with the parity fixes.
• Facts: the export used is byte-identical to pineforge-release main's facts/facts.json at eef6d7ec, so lab facts check against the published facts passes.
• docs/pages/native-engine.md, docs/pages/pine-to-native.md, docs/adr/0001-kernel-adapter-boundary.md and comments in include/pineforge/native_c_api.h / native_host.hpp still call the four C-SURFACE-2 rows "scheduled for 1.1.0". They are left as they are here: those pages are checked by the build, so editing them takes the merge gate off the docs-only basis. The CHANGELOG and the public contract say the four rows are not in 1.1.0.

Verified

• Facts, from the 1.1.0 export: lab facts render: PASS: 51 fact markers; 2 file(s) rendered: README.md, docs/pages/contributing-llm.md; lab facts check: PASS: 51 fact markers; 0 file(s) drifted.
• scripts/check_doc_reverts.py --base origin/main: OK (4 commits, 0 unnamed sentence deletions or reverts). scripts/check_doc_lint.py: 0 offenders. scripts/check_doc_anchors.py: every anchor resolves. git diff --check: clean.
• Re-checked in the tree: PF_ABI_VERSION 4; pineforge.h only gains declarations; native_c_api.h and the native C++ host headers are unchanged since v1.0.1 (Confirmed-bar streams compute what the batch computes #325 and Install other symbols' bars for request.security in the Docker harness (--symbol-feeds) #327 touch neither); the epoch is engine_script_run_v19; the hash-recipe changes listed under State hashes are additions only (file:line evidence was given to the lane supervisor); Install other symbols' bars for request.security in the Docker harness (--symbol-feeds) #327's report keys and messages come from its docker/run_json.py docstring, load_symbol_feeds / install_symbol_feeds / symbol_feeds_record and docker/README.md on main; codegen request discovery from codegen session symbols round 7: HTF completion/warm-up on the symbol clock, prearmed brackets at the fill open, syminfo.type, 24h session strings, trail_offset ticks, Qty export #164.
• The MACD tutorial's printed numbers (docs/pages/tutorial-macd.md, tutorial/README.md) were re-measured on a spot build box at this branch's earlier code (before Confirmed-bar streams compute what the batch computes #325 and Install other symbols' bars for request.security in the Docker harness (--symbol-feeds) #327): 50 trades (17W / 33L), net pnl +569.97, as the pages state. Confirmed-bar streams compute what the batch computes #325 leaves batch results unchanged and Install other symbols' bars for request.security in the Docker harness (--symbol-feeds) #327 changes only the harness.
• The public corpus sweep's "311 excellent + 1 declared anomaly" was not re-run (a full 312-probe sweep); the README scopes it to the v1.0.1 library it was measured on.

🤖 Generated with Claude Code