[daggerok]

What

Shared range-52w block from the workspace etf-std tools, applied with apply-block.ts, wired once in main() right before index.json is written (withRange52w). Every funds[].metrics gets seven keys, placed before returnsBasis and performanceAsOf:

• week52Low, week52High: lowest and highest close of the 52 weeks up to the last published close
• range52w: position of that close between them in percent (0 = at the low, 100 = at the high)
• range52wClose, range52wAsOf: the close used and its date
• range52wSince: first close when the fund has less than 52 weeks of history, else null
• range52wBasis: the history column used (Close, Market Price, NAV)

Closes, not intraday highs and lows; no new requests. Unavailable values are null, never 0.

Why

A 52-week range column sorted by position (like Fidelity) in the brand apps and the ETFs hub; the UI follows in a separate change.

Checks

• bun test (42 pass, exit 0), and again with the 24 workflow controls of scripts/update-data.config.json exported (exit 0); the first pipeline test now checks the seven keys on every row
• TC_MODE=esnext .claude/tools/etfs/tc/check.sh . prints nothing; the default (IDE) run shows no new error lines compared with main (53 pre-existing)
• live TICKERS="AAXJ ACWI" bun ./scripts/update-data.ts: 482 rows, 482 with dataFile, all 482 get a range, 27 young funds carry range52wSince; basis NAV per Share everywhere, because the iShares history sheet publishes only NAV (As Of, NAV per Share, Ex-Dividends, Shares Outstanding, Non-FV NAV), no market close; returnsBasis and performanceAsOf stay the last two keys