From af6381c1c676c54f57e1672087f8f62186c67b20 Mon Sep 17 00:00:00 2001 From: luisleo526 Date: Tue, 7 Jul 2026 22:34:55 +0800 Subject: [PATCH] docs: correct stale lookahead_on hard-reject claim in CLAUDE.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit barmerge.lookahead_on is accepted with a repaint warning and is engine-supported (first-intrabar publication; script-tf publish gating for finer-than-chart targets) — verified against _check_request_security and test_request_security_lookahead_on_kwarg_warns on 2026-07-07. Also documents ignore_invalid_symbol as accepted-but-inert and the chart-symbol alias forms. This correction was twice lost to concurrent CLAUDE.md rewrites authored from stale bases; the wording now flags the staleness explicitly so it is not restored a third time. Co-Authored-By: Claude Fable 5 --- CLAUDE.md | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index fd7599a..3ec70d4 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -276,13 +276,21 @@ you delete or weaken the special case, the test will tell you. PREVIOUS bar's HLC (`_s_high[1]`, `_s_low[1]`, `_s_close[1]`) per Pine v6 semantics with `developing=false`. 6. **`request.security` is strict.** Only `symbol`, `timeframe`, - `expression`, `gaps`, and `lookahead` are allowed. Symbol must resolve - to the current chart symbol (`syminfo.tickerid` or `syminfo.ticker`). - `gaps` and `lookahead` must be the literal `barmerge.gaps_*` / + `expression`, `gaps`, `lookahead`, and `ignore_invalid_symbol` are + allowed (`ignore_invalid_symbol` is accepted but inert — the symbol is + always the chart symbol, so no symbol can be invalid). Symbol must + resolve to the current chart symbol (`syminfo.tickerid` or + `syminfo.ticker`, incl. first-binding aliases and + `ticker.inherit/standard/heikinashi()`). `gaps` and + `lookahead` must be the literal `barmerge.gaps_*` / `barmerge.lookahead_*` member access (codegen does not parse other - shapes). `barmerge.lookahead_on` is hard-rejected for backtest-honesty - reasons. The `timeframe` argument, when a string literal, is validated - against the Pine v6 TF format at parse time (PR #3). + shapes). `barmerge.lookahead_on` is ACCEPTED with a repaint WARNING — + engine-supported (first-intrabar publication; script-tf publish gating + for finer-than-chart targets): see `_check_request_security`'s lookahead + branch and `test_request_security_lookahead_on_kwarg_warns`. The old + "hard-rejected" wording here was verified stale against the code on + 2026-07-07 — do not restore it. The `timeframe` argument, when a string + literal, is validated against the Pine v6 TF format at parse time (PR #3). 7. `**SUPPORTED_LOG`** gates `log.{info,warning,error}`. Without it, typos like `log.foo("x")` previously emitted a dead empty-string statement. Don't remove the gate.