`meetings/2026-05-01_183809-morning.md`

54 lines
# Daily Stand-up — Fri 2026-05-01 18:38 PDT

---

### 1. Carryover from last meeting

- ✅ `pd-api` — back online (status=online, restarts=4). Was a ghost; now visible. Monitor for stability.
- ⏳ `am-recrawl` — still stopped, 90 restarts. No fix landed. Critical path blocker.
- ⏳ `sf-orchestrator` — 7 restarts, still undiagnosed. No change.
- ⏳ `george-gmail` — 3 restarts / 6h uptime. No new crash in the last hour, but OAuth still unverified.
- ⏳ Directory decision — lawyers + doctors platform scope. Still outstanding.

---

### 2. Last hour (since 17:36 meeting)

**Crashes / instability:**
- `animals-viewer` — climbed from 30 → 34 restarts in one hour. The 4h-old community fix is not holding; crash rate is active right now.
- `visual-factory-orchestrator` — 17 restarts (was 16). Prefetch fix committed 19h ago is not stabilizing it.
- `am-recrawl` — still stopped at 90 restarts. Unchanged; nothing crawling.
- `gemini-catalog-tagger` — 7 restarts / 3h uptime. No new crashes this hour, but fast prior loop.
- `sf-orchestrator` — 7 restarts, no diagnosis.

**Long-running jobs:** Enrichment agents (full-monty, gap, update-sku, silas-sku) stable at 0 restarts / 33h uptime. No crawl input feeding them since am-recrawl is down.

**External signals:** No remote commits from collaborators. `lawyer-directory-builder` and `professional-directory` last touched 2 days ago — no new activity.

---

### 3. Plan + agent assignments

- `debugger-agent` — pull am-recrawl crash logs, identify root cause — feeds all downstream enrichment — commit fix or restart with diagnosis within 24h
- `debugger-agent` — read animals-viewer logs post community fix (34 restarts, still climbing) — confirm whether fix is incomplete or there's a second crash path — clear diagnosis documented
- `debugger-agent` — audit visual-factory-orchestrator logs; 17 restarts says prefetch fix didn't hold — root cause identified or follow-up patch committed
- `pm2-crash-watcher` — deep triage gemini-catalog-tagger (7 restarts / 3h uptime) — fast new crasher with no diagnosis — root cause named
- `Steve` — verify george-gmail OAuth credentials — 3 restarts in 6h is the OAuth signature; no new crash this hour but still unconfirmed — credentials verified or rotated
- `Steve` — write the lawyers + doctors platform decision — two active repos, no architectural decision; pre-scale window closing — decision in writing

---

### 4. Blockers and decisions Steve owes

- **am-recrawl** — log pull needed before anyone can fix it; enrichment queue is coasting on prior data
- **animals-viewer second crash path** — debate patches won't catch a memory leak or external dep; log read is prerequisite
- **visual-factory follow-up patch** — needs a go/no-go after log audit
- **george-gmail OAuth** — 2-minute check, blocked on Steve running it
- **Directory platform decision** — `lawyer-directory-builder` + `professional-directory` are diverging in parallel; every day without a decision is rework risk

---

### 5. One thing to think about

`animals-viewer` added 4 restarts in the last hour — it's actively crashing right now, not just carrying a stale restart count. The debate-driven community fix committed 4h ago clearly didn't close the loop. Before triggering another round of patches, one log read may reveal whether this is a completely different crash path (memory ceiling, external dep timeout, race condition) that code debates won't surface.