orphan-watchlist follow-up RESOLVED (considered, dropped: not actually orphaned)

Thesis

orphan-watchlist follow-up RESOLVED (considered, dropped: not actually orphaned)

The promote entry carried an open "wire nearline-storage into a recurring scan slot" item. Checked the mechanism — it's a non-issue:

  • fetch:all and precompute both auto-discover every .json in the watchlists dir (listWatchlists() / precompute-summaries.ts line 406 Deno.readDir), so nearline-storage is already fetched + summarized every cycle (its summary exists and refreshes; the foreign-primary precompute bug fixed same day proves it's in the loop).
  • Analysis coverage comes from the Phase-0 perspective refresh, which reads data/summaries/nearline-storage.json directly — independent of any named scan slot.
  • STX/WDC are double-covered via the memory watchlist (["MU","STX","WDC","DRAM","HY9H.F","005930.KS","EWY"]).

A dedicated named scan slot would only add a scan-name↔watchlist mapping to maintain (a known confusion source) for zero new signal — it wouldn't change any call. Considered, dropped. The only genuinely-open nearline item is the HOCPY segment-financials pull (which would change the upstream-pick call), carried to its own research launch.

No direct external sources are attached to this read.