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

55 lines
Using the context bundle provided directly in the prompt — here is today's meeting.

---

## Daily Stand-Up — Fri 2026-05-01

---

### 1. Carryover from last meeting
_No prior meeting on file. Clean slate._

---

### 2. Overnight (last 12 hours)

**Crashes / instability** — multiple unstable processes:

- ⚠️ `am-recrawl` — **stopped**, 90 restarts. Highest urgency. Not recovering on its own; likely a hard error (bad endpoint, auth expiry, or out-of-memory loop). Needs manual inspection before re-enabling.
- ⚠️ `pd-api` — online but 23 restarts. Professionals directory API is flapping; probably tied to the LA County doctors project (committed 2 days ago). App-level crash, not infra.
- ⚠️ `animals-viewer` — online, 21 restarts. A near-me SQL fix was just committed 3 minutes ago — this may settle. Watch it.
- ⚠️ `visual-factory-orchestrator` — online, 16 restarts. A socket prefetch fix was pushed 13h ago (`agent:false`). May be stabilizing; restart count doesn't show post-fix window.
- ⚠️ `george-gmail` — online but only 1h uptime, 3 restarts. Email infra is fragile right now.
- `sf-orchestrator` — 7 restarts (not in top-30 list, flagged in crash list only). Needs a log pull.
- `gemini-catalog-tagger` — 6 restarts in 4h. Tagging pipeline is actively struggling.

**Long-running jobs** — `gemini-tag-engine` has been running 11h (1 restart, appears stable). `full-monty-agent`, `gap-agent`, `update-sku-agent` all stable at 28h uptime.

**External signals** — all git activity is local (Steve). No collaborator commits. Visual-factory prefetch fix and animals SQL fix both landed overnight/just now.

---

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

1. `Steve` — inspect `am-recrawl` logs (`pm2 logs am-recrawl --lines 50`) — 90 restarts means a hard loop; determine if it's an auth expiry or bad target URL — **success: root cause identified, process either restarted clean or stopped intentionally**
2. `debugger-agent` — pull `pd-api` crash logs and identify why it's flapping at 23 restarts — probably a missing env var or DB connection string in the new professional-directory project — **success: error type identified, fix scoped**
3. `Steve` — verify `animals-viewer` stabilizes after the near-me SQL fix committed 3min ago — just watch pm2 restart count for 30 min — **success: restarts stop climbing**
4. `Steve` — check `george-gmail` (1h uptime, 3 restarts) — email infra failure could silently kill outbound comms — **success: logs reviewed, process stable or root cause surfaced**
5. `gemini-catalog-tagger` — if still restarting after #2 is scoped: pause it and run `gemini-tag-engine` solo until tagger is fixed — **success: tagging pipeline producing output without crash loop**
6. `Steve` — review lawyer-directory dashboard changes (committed 35h ago) for the wiki-lawyers importer — **success: confirm wiki source data is pulling correctly, no false positives in the import**

---

### 4. Blockers & decisions Steve owes

- `am-recrawl` restart: can't auto-recover at 90 restarts — Steve must decide restart-or-disable.
- `pd-api` / professional-directory: new project with no prior context — Steve needs to confirm whether this is production or still dev (affects urgency of the flapping fix).
- `visual-factory-orchestrator` — 16 restarts: is the socket fix sufficient or does this need a deeper architectural review?
- FashionCrawler TODO content was truncated — unknown open items there.

---

### 5. One thing to think about

`pd-api` (professionals directory) and `lawyer-directory-builder` are both new directory projects committing in parallel. Are these the same product family or separate initiatives — and if separate, are they sharing infra/DB, or is that a gap that'll bite you at launch?