Item 1 — VERB LAW: one verb, READ (never SCAN), + a lint that enforces it

The product argued with itself: FAB/nav said "Scan", Free tier "5 scans",
ticker "MLB slate scanned" — while the Ledger says "MY READS". Swept every
user-visible surface to READ:
- BottomTabBar FAB + Nav link: 'Scan' → 'Read'
- Pricing free tier: '5 scans to try the model' → '5 reads …'
- StatStrip: 'Awaiting next scan' → 'Awaiting next read'
- Ticker badge + snapshotService event: tag 'SCAN' → 'READ',
  'slate scanned' → 'slate read' (readSportOf parses BOTH old and new so
  cached ticker items dedupe cleanly through the rollover)
- upgradePitch: 'You've scanned N parlays' / 'unlimited scans' → read/reads

Internal untouched (not user-visible): /api/scan routes, scan_count column,
scanning state, DemoScan/ScanIcon, scanlines CSS, the transitional SCAN
color-map key.

tests/unit/verbLaw.test.js is the enforcement: it fails on user-visible
scan/scanned/scans copy across web/src + src/services (skips comments). Suite
270/3254 green, web build exit 0.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

web/src/lib/pipelineSchedule.js

@@ -1,6 +1,6 @@
 /* ============================================================
    Session 59 (work-order 2.3) — the REAL pipeline schedule, for honest
-   waiting states. "Awaiting next scan" told the user nothing; the truth is
+   waiting states. "Awaiting next read" told the user nothing; the truth is
    the cron fires at fixed UTC hours, so we can say "Grades post ~6:00 PM ET".
 
    HOURS_UTC mirrors the backend default (snapshotScheduler SNAPSHOT_HOURS_UTC

web/src/lib/slateAdapter.js

@@ -297,7 +297,7 @@ function slateTeamsMatch(a, b) {
  * Build pre-graded `playerStrips` for one game by OVERLAYING the snapshot's
  * locked grades onto the game's odds-derived props (which already carry the
  * correct game grouping). Each prop is either graded (grade + gradedAt + delta)
- * or `awaiting:true` (no snapshot match yet → "Awaiting next scan", no Read
+ * or `awaiting:true` (no snapshot match yet → "Awaiting next read", no Read
  * button). Archetype comes from the snapshot's per-player classification.
  *
  * Session 59 (work-order 1.6) — THE JOIN INVARIANT: when the snapshot knows