Capture: relay /relay/analyze doc-drift (prompt vs transcript)
This commit is contained in:
@@ -39,3 +39,4 @@ Example:
|
||||
- [ ] (new:portfolio-scraper) [project][P2] Portfolio-company scraper — tracks portfolio companies for podcasts, social tweets, founder appearances, news, etc. and delivers a digest via email or another interface, 2026-06-14
|
||||
- [ ] (recap) [bug][P2] Mobile gets stuck and can't scroll back to top — recaps.cc transcript view. ATTEMPTED in app 0.2.157 (-webkit-overflow-scrolling:touch + overscroll-behavior:contain on .chunks-scroll); UNVERIFIED — needs on-iPad check, plus a screen recording if it persists, 2026-06-14
|
||||
- [ ] (ten31-database) [chore][P2] Reconcile AGENTS.md networking facts: the doc says the CRM is reached "on the LAN or over Tailscale," but it's actually served over ClearNet (StartTunnel) with app-level user auth, and Tailscale is NOT in use. Fix the access/networking wording — surfaced during standards placement-guide verification, 2026-06-15
|
||||
- [ ] (recap-relay) [chore][P3] AGENTS.md endpoint list mis-describes POST /relay/analyze as "{ transcript, … } → topic sections JSON". The actual route (server/routes/analyze.js) takes a free-form { prompt: string } and returns the standard envelope { result: { text } }; "topic sections JSON" is only what the recap-app caller asks for in its prompt. Fix the request-shape wording to { prompt } — surfaced resolving Recaps' Daily Digest synthesis contract (Q4), 2026-06-15
|
||||
|
||||
Reference in New Issue
Block a user