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

57 lines
# Daily Stand-up — Fri 2026-05-01 14:34 PDT

---

### 1. Carryover from last meeting (13:25 PDT, ~1h ago)

⏳ `am-recrawl` — still stopped, 90 restarts. No change. Root-cause diagnosis still owed.
⏳ `pd-api` — now 26 restarts (was 23). Climbing. Missing env var still unresolved.
⏳ `visual-factory-orchestrator` — still 16 restarts but **no new restarts in the past hour**. Prefetch fix appears to be holding. Watching.
⏳ Directory consolidation decision — doctors + lawyers, one platform or two. Still owed.

---

### 2. Last hour

**Crashes / instability**
- `animals-viewer` — 28 restarts now, up from 21 an hour ago (+7 in 1h). Accelerating. This is the fastest-growing failure in the fleet.
- `pd-api` — 26 restarts, up from 23. Still climbing, slower rate.
- `george-gmail` — 3 restarts / 2h uptime. No new restarts since last check. Holding, not resolved.
- `visual-factory-orchestrator` — stable at 16 since prefetch fix. Tentatively call it ✅ pending a full hour of clean runtime.
- `gemini-catalog-tagger` — 6 restarts at 6h uptime, up from 4h. No new restarts in 2h. May have stabilized.

**Long-running jobs**
- `silas-sku-agent`, `gap-agent`, `update-sku-agent` — 0 restarts, 29h uptime. No output signals visible; unclear if working or idling.

**Git activity**
- `animals` — commit 3 minutes ago: "fix(community): debate-driven fixes for visibility, comments, signup." Could be related to `animals-viewer` restarts. Check whether this deploy landed cleanly.

---

### 3. Today's plan + agent assignments

- `Steve` — pull `animals-viewer` logs immediately — 28 restarts in 29h and still accelerating is the hottest active fire — identify crash reason before it hits 40
- `Steve` — check whether the `animals` commit (3 min ago) stabilized `animals-viewer` or if restarts are continuing post-deploy — success = 0 new restarts in next 30 min
- `Steve` — supply missing env var / DB string to `pd-api` or pull it from PM2 — 26 restarts on a new project is noise in the fleet — 0 restarts for 1h
- `Steve` — pull `am-recrawl` logs, identify crash reason — 90 restarts / stopped is a hard block — go/no-go decision before any endpoint changes
- `Steve` — check `george-gmail` OAuth credentials — 3 restarts in first 2h almost always means token issue — stable green for 2h
- `pm2-crash-watcher` — confirm `silas-sku-agent` / `update-sku-agent` are producing output, not just idling — 29h uptime with 0 restarts but no visible commits suggests possible silent idle — queue drain evidence in last 6h
- `Steve` — written one-liner: one professionals platform or two — window is now before either directory scales further

---

### 4. Blockers & decisions Steve owes

- `animals-viewer` — root cause unknown; actively worsening
- `am-recrawl` — nothing proceeds on that service without a diagnosis
- `pd-api` — needs env var from Steve to stabilize
- Directory consolidation — doctors + lawyers, one codebase or two
- `george-gmail` OAuth — if it's wired to any live outbound flow, every flap is a silent drop
- `gemini-catalog-tagger` vs `gemini-tag-engine` queue scope — deferred from last meeting, still unresolved

---

### 5. One thing to think about

`animals-viewer` jumped 7 restarts in the last hour — that's the steepest crash rate in the fleet right now, and a fresh commit to the `animals` repo just landed 3 minutes ago. Did that deploy fix the restarts or introduce them? Check the restart timestamps against the commit time before assuming the fix landed cleanly.