Skip to content

Commit 673e95b

Browse files
luisleo526claude
andcommitted
Place the symbol-feeds CHANGELOG entry after the confirmed-bar streams one
After the rebase onto #325 the entry sat at the top of Unreleased; it now follows #325's entry, as the merge order asks. Wording unchanged. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
1 parent 8c554c5 commit 673e95b

1 file changed

Lines changed: 13 additions & 13 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -7,19 +7,6 @@ version number follows semantic versioning over the surfaces the
77

88
## Unreleased
99

10-
- **Harness symbol feeds:** `docker/run_json.py --symbol-feeds` (`PINEFORGE_SYMBOL_FEEDS`)
11-
installs other symbols' bars for `request.security` on another symbol: a JSON
12-
index keyed by the exact symbol string the script passes and by timeframe, each
13-
feed an OHLCV CSV plus the symbol's catalog `syminfo`, through
14-
`strategy_set_symbol_facts` / `strategy_set_symbol_feed` (engine and codegen
15-
1.0.0 and later). One feed per requested timeframe: nothing aggregates another
16-
symbol's bars, so a `1` feed serves neither a `240` nor a `D` request. Unset
17-
changes nothing; an index or feed it cannot install fails
18-
the run (one `{"engine":"pineforge","error":...}` line, harness exit 1,
19-
entrypoint exit 4). What was installed is recorded as
20-
`applied_runtime.symbol_feeds`, so such a run has its own fingerprint digest.
21-
The engine library is unchanged.
22-
2310
- **Harness lot grid:** `docker/run_json.py` applies `mincontract` from the
2411
`--syminfo` (`PINEFORGE_SYMINFO`) file as the engine's lot grid, the metadata key
2512
`qty_step` plus the `mincontract` key a script's `syminfo.mincontract` reads, so a
@@ -44,6 +31,19 @@ version number follows semantic versioning over the surfaces the
4431
unchanged. The streaming guide gains a "Backtest vs live" section listing what a
4532
backtest can see that a live run cannot.
4633

34+
- **Harness symbol feeds:** `docker/run_json.py --symbol-feeds` (`PINEFORGE_SYMBOL_FEEDS`)
35+
installs other symbols' bars for `request.security` on another symbol: a JSON
36+
index keyed by the exact symbol string the script passes and by timeframe, each
37+
feed an OHLCV CSV plus the symbol's catalog `syminfo`, through
38+
`strategy_set_symbol_facts` / `strategy_set_symbol_feed` (engine and codegen
39+
1.0.0 and later). One feed per requested timeframe: nothing aggregates another
40+
symbol's bars, so a `1` feed serves neither a `240` nor a `D` request. Unset
41+
changes nothing; an index or feed it cannot install fails
42+
the run (one `{"engine":"pineforge","error":...}` line, harness exit 1,
43+
entrypoint exit 4). What was installed is recorded as
44+
`applied_runtime.symbol_feeds`, so such a run has its own fingerprint digest.
45+
The engine library is unchanged.
46+
4747
- **Native runner routing and delivery:** webhooks are optional; `--webhook-routes`
4848
adds first-match per-action targets and payload `pineforge-native-order-action/v2`.
4949
New `actions`, `status` and offline `redeliver` commands expose the journal and

0 commit comments

Comments
 (0)