1.7.0 release prep: CHANGELOG 1.7.0 — 2026-10-25, stale 'unreleased' pointers, macOS build fix (::sig*set macros) - #500

Docs-only (CHANGELOG.md only) for the 1.7.0 tag, on main 91353de (#499). Names the section ## 1.7.0 — 2026-10-25 (was ## Unreleased); states the closed-trade read cache by entry point (no sink: up to 20,447,232 B; sink installed, incl. the release image's docker/run_json.py default unjailed profile: fixed 39,936 B, closed-trade loops over 128 trades re-read from scratch); the Known-limits slowdown line with measured figures: hungpixi through the release image's docker/run_json.py default profile did not finish within 1800 s (stopped at the cap) vs 74.18 s on 1.6.3 on the same box; through scripts/run_strategy.py without a sink (hosted case runner, verifier, sweep) 107.2 s (mean of three); peak RSS scripts/run_strategy.py default path, hl2-01, 100,000 bars, n=3: 144.9 MiB on 1.6.3 vs 125.7 MiB on 1.7.0. src/, include/, tests/ unchanged.

Checks on this head: preflight rj-20261024t211651-b7d846, docs rj-20261024t211655-191c85. REV-CX GO (numbers vs SM-CX's rows), SM-CX checked every figure. VERSION untouched (release.yml writes it).

--- commit message ---
CHANGELOG: say which entry points run with a report sink, and what that costs on the release image

The closed-trade cache bullet said how big the ledger read cache is with and without a report
sink but not which entry points install one. It now names them, from the tree: a handle has no
sink until its host calls strategy_set_report_sink_v1 or strategy_set_report_sink_fd_v1; the C
API used directly, C++ hosts including the Pine host, the runner/ command line,
scripts/run_strategy.py without PINEFORGE_REPORT_SINK=1 and docker/run_json.py --profile jailed
without --report-sink-fd keep the 65,536-row cache (20,447,232 bytes); docker/run_json.py in its
default unjailed profile (it installs a temporary sink on every handle), the jailed profile with
--report-sink-fd, run_strategy.py with PINEFORGE_REPORT_SINK=1 and any host that installs a sink
get the 128-row cache (39,936 bytes), and a closed-trade loop over more than 128 rows re-reads
the colliding rows from scratch files on every pass (every row from 256 closed trades on). The
App's jailed host is stated as not known.

The "Costs that remain" slowdown bullet gains the measurements that go with it, each taken on
one 16 vCPU machine: the six-script figures were measured through scripts/run_strategy.py,
which installs no sink unless PINEFORGE_REPORT_SINK=1 (it was not), so the large cache was in
effect; hungpixi (24,238 closed trades) through the release image's default docker/run_json.py
took 74.18 s on 1.6.3 and did not finish within 1800 s on 1.7.0 (the run was stopped at that
limit); through scripts/run_strategy.py without a sink it takes 107.2 s (mean of three runs);
peak RSS of the default run_strategy.py path (hl2-01, 100,000 bars, n=3) is 144.9 MiB on 1.6.3
and 125.7 MiB on 1.7.0. No statement is made that the run_json.py results are identical: the
1.7.0 run produced none.

Replaced sentences (all four are in the closed-trade cache bullet of CHANGELOG.md on main
91353de, the 1.7.0 line squash of #499, and are replaced here):

• "Without a report sink the cache holds at most TradeLedger::kDefaultCacheRows = 65,536 rows
  of TradeLedger::kLedgerEntryBytes = 312 bytes, 20,447,232 bytes, and is allocated at the
  smaller of that budget ... 20,447,232 bytes above 32,768." is now the sentence beginning
  "A run with no report sink holds at most".
• "With a report sink installed the budget is TradeLedger::kSinkCacheRows = 128 rows,
  39,936 bytes, a fixed bound ... so that the sink run's working memory stays flat." is now
  the sentence beginning "A run with a report sink installed holds at most".
• "Above the budget the cache is direct-mapped, so rows that share a slot evict each other ...
  with a report sink, 2 x (N - 128) rows per pass below 256 closed trades, and every row from
  256 on." keeps both formulas and now says "with no sink" and "with a sink".
• "The budget has no user control in this release: NativeExecutionConsumer::begin_ready sets
  it at every run begin ... and nothing in the C API or the environment changes either
  figure." is now "The two figures cannot be changed by a user in this release: ... installing
  a sink or not is the only choice." (the environment variable PINEFORGE_REPORT_SINK does choose
  whether run_strategy.py installs a sink, so the old sentence overstated).

One more sentence of main's text is reworded in the same bullet: "The six are not a sample of
all scripts, and the results are identical in every measured case." now ends "identical in
every one of those six measured cases", because the run_json.py hungpixi run added below has no
1.7.0 result to compare. The not-affected sentence names the hosted case runner, the verifier
and the sweep, and states that the corpus-parity canary pass sets PINEFORGE_REPORT_SINK=1
(scripts/check_corpus_parity.sh, line 316).

The heading of the 1.7.0 section is renamed: the line "## Unreleased" is replaced by
"## 1.7.0 — 2026-10-25" (same form as "## 1.6.1 — 2026-10-18"). VERSION is not touched here.

Only CHANGELOG.md changes; no citation moves.

Co-Authored-By: Claude Sonnet 5.5 [email protected]

🤖 Generated with Claude Code