Skip to content

Commit 83d64dc

Browse files
luisleo526claude
andcommitted
docs: #315's range-end change folds less, not more
The 1.1.0 lead said three changes "fold more state"; #315's range-end change instead stops folding a stream report's terminal re-mark into the hashed extremes. The sentence now says the three changes change what the hashes fold, and names Stream/0/1 as a re-pinned witness row without claiming it is #315's only one. Replaces text introduced by 66be240 (this branch's second commit): "Three changes also fold more state" and "re-pinning one witness row (`Stream/0/1`, whose recorded-row digest alone moves)". Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
1 parent 66be240 commit 83d64dc

1 file changed

Lines changed: 10 additions & 9 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -21,15 +21,16 @@ layout moves; the frozen historical headers and archives are untouched. The
2121
script ABI epoch stays `engine_script_run_v19`, and the state hashes keep their
2222
domain tags, `pineforge-broker-state/v19` and `pineforge-source-adapter/v4`.
2323
Their values change in two ways. A run whose fills a Pine adapter change below
24-
alters hashes to new values. Three changes also fold more state, so a run can
25-
hash differently from 1.0.1 with byte-identical trades: [#315] folds a pending
26-
same-bar entry's original (unbatched) request and placement and no longer folds
27-
a stream report's terminal re-mark into the hashed extremes, re-pinning one
28-
witness row (`Stream/0/1`, whose recorded-row digest alone moves); [#316] folds
29-
an opening stop's next waypoint, re-pinning `Random44/0/0` and `Random44/0/1`;
30-
and [#319] folds tick-volume accumulator state only where it adds information,
31-
so every existing pin holds. The installed header `pineforge/live_parser.h` is
32-
removed with the runner's parser plugins ([#320]); no surface of the [public
24+
alters hashes to new values. Three changes also change what the hashes fold, so
25+
a run can hash differently from 1.0.1 with byte-identical trades: [#315] folds
26+
a pending same-bar entry's original (unbatched) request and placement and no
27+
longer folds a stream report's terminal re-mark into the hashed extremes (the
28+
witness row `Stream/0/1` is re-pinned with only its recorded-row digest
29+
moving); [#316] folds an opening stop's next waypoint, re-pinning
30+
`Random44/0/0` and `Random44/0/1`; and [#319] folds tick-volume accumulator
31+
state only where it adds information, so every existing pin holds. The
32+
installed header `pineforge/live_parser.h` is removed with the runner's parser
33+
plugins ([#320]); no surface of the [public
3334
contract](docs/pages/public-contract.md) covers it. The four rows of the 1.0 C
3435
boundary that were scheduled for 1.1.0 (C-SURFACE-2: a non-mutating execution
3536
preview, the origin and label of an applied event, a closed-trade entry-comment

0 commit comments

Comments
 (0)