- Add await ctx.cache.subscribe() to addSymbol mutation so symbols added via the sidebar get registered in symbol_demand and yfinance jobs are queued immediately - Backfill PEP, WYNN, STZ, CELH into symbol_demand + adapter_queue - Upgrade yahoo-finance2 3.15.3 -> 3.15.4 and pass validateResult:false to quoteSummary() to handle Yahoo schema drift - Add error detail logging for analyst ratings schema failures - Update .gitignore with common ignores
1.4 KiB
This is NOT the Next.js you know
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices.
Cross-Session Context
Before starting work on investor-flow, read:
- Domain wiki:
~/Library/Mobile Documents/iCloud~md~obsidian/Documents/Life/System/Projects/investor-flow.md - As-built status:
docs/FUNCTIONAL_DESIGN.md+docs/TECH_DESIGN.md(prefer these over HANDOFF or old slice SPECs for "what's built") - Glossary:
CONTEXT.md
Confirm at session start: Print a one-line confirmation like "✓ Read investor-flow domain model + as-built designs" so the user knows context was loaded.
Rate-Limit Rules (ADR-0009)
Never bypass the rate-limit system. Every external data source (Yahoo Finance, SEC EDGAR, X/Twitter, Reddit, FRED) must go through either:
AdapterQueue(production pipeline with per-source min-interval + 429 cool-down), or- A local in-memory throttle with explicit backoff on rate-limit errors (for ad-hoc/service-path fetches)
No direct vendor calls from TRPC endpoints, next.js server actions, or agent scripts without rate-limit protection. The app is designed on the principle that stale cached data beats empty/erroring UI.