Session 52: Coming Soon teaser + infrastructure verification (2239 tests)
Phase 1 — Push-to-Book teaser (feature not live; teaser only): - StatStrip: "BOOK IT ⟶" per graded prop (hover: "Push-to-Book coming soon"). - GradeResultCard: "PUSH-TO-BOOK · COMING SOON" footer. Phase 2 — infrastructure verification: - snapshotScheduler logs armed AND disarmed state (incl SNAPSHOT_CRON) so container logs disambiguate off-vs-crashed. - NEW GET /api/internal/snapshot/status (internal-key gated): cron_armed, cron_hours_utc, last_snapshot per sport (gradeCount/deltaCount), redis_keys existence map, ticker_count. The post-deploy pipeline health probe. - Finding: Redis AOF/RDB persistence is a server-side (Coolify) config the app can't set/verify — documented. Phase 3 — delta pipeline (verified sound, no fix needed): - runSnapshot already rotates :latest->:previous and diffs locked lines; added opt-in SNAPSHOT_DEBUG=1 [deltas] log + a trace test asserting :previous is preserved verbatim and the delta math is correct. Backend 2234 -> 2239 tests (+5), 192 suites. Web build clean (exit 0). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
+31
-2
@@ -4,8 +4,37 @@
|
||||
2026-06-18
|
||||
|
||||
## Current Phase
|
||||
SHIP BUILD v51.0 — Team Hub: /team/[abbr] roster with archetypes, season stats,
|
||||
graded props; clickable team abbrs on every game card. Research depth.
|
||||
SHIP BUILD v52.0 — Push-to-Book "Coming Soon" teaser + infrastructure
|
||||
verification (snapshot status probe, scheduler logs, delta pipeline confirmed).
|
||||
|
||||
## Session 52 (2026-06-19) — SHIPPED ✅ TEASER + INFRA VERIFICATION
|
||||
|
||||
Backend 2234 → **2239 tests** (+5), 192 suites. Web build clean (exit 0).
|
||||
|
||||
### Phase 1 — Push-to-Book teaser (feature NOT live; teaser only)
|
||||
- `StatStrip`: a `BookItTeaser` ("BOOK IT ⟶", hover tooltip "Push-to-Book coming
|
||||
soon — connect your sportsbook") after the parlay "+" on every graded prop.
|
||||
- `GradeResultCard`: a "PUSH-TO-BOOK · COMING SOON" footer section.
|
||||
|
||||
### Phase 2 — infrastructure verification
|
||||
- `snapshotScheduler` now logs BOTH states: armed (`[snapshotScheduler] armed —
|
||||
SNAPSHOT_CRON=1, hours=…`) and disarmed (so container logs disambiguate
|
||||
off-vs-crashed). Test asserts the armed log.
|
||||
- NEW `GET /api/internal/snapshot/status` (internal-key gated): `{ cron_armed,
|
||||
cron_hours_utc, last_snapshot:{sport:{updated_at,gradeCount,deltaCount}},
|
||||
redis_keys:{…:bool}, ticker_count }`. The single probe to verify the pipeline
|
||||
post-deploy.
|
||||
- REDIS PERSISTENCE FINDING: the app uses `REDIS_URL` (ioredis) — AOF/RDB
|
||||
persistence is a server-side (Coolify Redis) config the app can't set/verify.
|
||||
If snapshot keys vanish on restart, enable persistence on the Redis instance.
|
||||
|
||||
### Phase 3 — delta pipeline (verified sound; no fix needed)
|
||||
`runSnapshot` already reads `:latest` as prev → `computeLineDeltas(enriched,
|
||||
prev.grades)` → writes old→`:previous`, new→`:latest`. So deltas populate on the
|
||||
2nd+ run. Added an opt-in debug log (`SNAPSHOT_DEBUG=1`) + a trace test asserting
|
||||
`:previous` is preserved verbatim and the delta math is correct.
|
||||
|
||||
## Session 51 (2026-06-19) — SHIPPED ✅ TEAM HUB
|
||||
|
||||
## Session 51 (2026-06-19) — SHIPPED ✅ TEAM HUB
|
||||
|
||||
|
||||
Reference in New Issue
Block a user