# VYNDR — Blockers

## BLOCKER-001: Hosting Decision
**Status:** OPEN
**Impact:** Blocks deployment (Phase 3)
**Options:**
- Vercel — free tier, great for Next.js, limited backend
- Railway — better for full-stack, Node.js native, $5/mo start
**Decision needed by:** End of Phase 1
**Owner:** Kev

## BLOCKER-002: Auth Provider
**Status:** RESOLVED (2026-03-21)
**Decision:** Supabase Auth. See DECISION-004.

## BLOCKER-003: WSL2 Cannot Resolve *.supabase.co Domains
**Status:** OPEN
**Impact:** Blocks applying Feature 1.4 migration and running verify-schema.js from CLI
**Details:**
- WSL2 DNS resolver (10.255.255.254) cannot resolve `*.supabase.co` TLD
- Google DNS (8.8.8.8) returns NXDOMAIN — may be a new project with DNS propagation delay
- `*.supabase.com` (e.g., pooler, api) resolves fine
- Migration SQL is written and validated (37 tests pass)
**Workaround:** Apply migration via Supabase Dashboard SQL Editor
**Resolution path:** Either DNS propagates, or add Supabase IP to /etc/hosts, or use `supabase link` with access token via api.supabase.com
**Owner:** Kev


## PINNACLE MLB PROP COVERAGE STOPPED — 2026-07-31 (open, external)

**One question to PropLine:** *why did Pinnacle MLB player-prop coverage stop on
2026-07-31?*

**Evidence:** `closing_captures` MLB, pinnacle: 103,940 rows over 07-20 → 07-30,
then **4,022 → 0** on 07-31 and zero since, while every other book continued
normally (07-31: 47,606 non-pinnacle rows). `line_type='sharp'` is a label applied
in `closingCapture.js` via `SHARP_BOOKS` — same feed, not a separate provider.

**Why it matters:** Pinnacle is the only sharp anchor we have ever had for props
(17,090 two-sided captures in that window). Without it the consensus ruler is a
**market** consensus, not a **sharp** one.

**Status:** `market-not-sharp` is **PENDING-RECOVERY, not confirmed permanent.**
Do NOT enshrine it in MASTER-PLAN as a permanent limitation until this is
answered. Not caused by any VYNDR change — the display widening only adds books.