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

55 lines
# Daily Stand-up — Fri 2026-05-01 13:25 PDT

---

### 1. Carryover from last meeting (Sunday Digest)

⏳ `am-recrawl` — 90 restarts, now stopped. Still no root-cause. Blocked on diagnosis before any endpoint changes.
⏳ `pd-api` — 23 restarts on a 2-day-old project. Likely missing env var / DB string. Shouldn't be a persistent PM2 service yet.
⏳ `visual-factory-orchestrator` — 16 restarts; prefetch fix landed 14h ago. Verdict on whether it held is due today.
⏳ Directory consolidation question — doctors + lawyers directories both committing fast, separate codebases, shared infra risk. Decision still owed.

---

### 2. Overnight (last 12 hours)

**Crashes / instability**
- `george-gmail` — online but 3 restarts in 1h. New entrant; likely auth token expiry or missing credential. Watch it.
- `visual-factory-orchestrator` — still showing 16 restarts; the prefetch fix is 14h old but PM2 data doesn't show post-fix restart count separately. Inconclusive.
- `pd-api` (23), `animals-viewer` (21), `sf-orchestrator` (7), `gemini-catalog-tagger` (6) — all carrying over from prior window.
- `am-recrawl` — stopped, 90 restarts. No change.

**Long-running jobs**
- `silas-sku-agent`, `gap-agent`, `update-sku-agent` — 28h uptime, 0 restarts. Running but no commits visible; unclear if producing output or idling.
- `gemini-tag-engine` (1 restart / 11h) vs `gemini-catalog-tagger` (6 restarts / 4h) — queue competition still unresolved.

**External signals**
- No collaborator commits. `animals` and `claude-codex-meeting` are both Steve's.

---

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

- `Steve` — pull `am-recrawl` logs and identify crash reason — 90 restarts with stopped status is a hard block — clear go/no-go before next endpoint touch
- `Steve` — check `pd-api` env config (missing DB string / API key likely) — stabilize or pull it from PM2 until ready — zero restarts for 1h
- `pm2-crash-watcher` — confirm whether `visual-factory-orchestrator` restarted post-prefetch-fix (compare timestamps) — determines if fix held or needs architectural review — restart count since 14h ago = 0
- `Steve` — check `george-gmail` auth credentials — 3 restarts in 1h on a Gmail agent almost always means OAuth token issue — stable green for 2h
- `gemini-catalog-tagger` vs `gemini-tag-engine` — confirm they're not competing on the same queue — one should be paused or scoped to a separate queue — no duplicate processing
- `Steve` — decide: one shared professionals platform or two parallel bets — window is now, before either directory scales — written decision, even a one-liner

---

### 4. Blockers & decisions Steve owes

- `am-recrawl` root-cause — nothing else can proceed on that service
- `pd-api` env vars — needs Steve to supply or confirm what's missing
- Directory consolidation — doctors + lawyers, one platform or two
- `gemini-catalog-tagger` queue scope — is it safe to let both taggers run simultaneously?
- FashionCrawler — open items unknown; needs a fresh log pull or an explicit "table it" decision

---

### 5. One thing to think about

`george-gmail` just appeared in PM2 with 3 restarts in its first hour. If it's wired into any outbound email flow (client comms, vendor onboarding, Norma), a flapping Gmail agent is a silent delivery failure. Is it connected to anything live-facing right now, or is it still being wired up?