`meetings/2026-05-05_120029-morning.md`

55 lines
# DW Morning Stand-Up — Tue 2026-05-05 09:00 PDT

---

## 1. Carryover from Last Meeting

1. ⏳ **Steve: PM2 restore** — Now resolved (PM2 data visible in context). Still flag: george-gmail at 4 restarts.
2. ⏳ **Steve: george-gmail OAuth rotation** — 7 days overdue. george-gmail shows restarts=4 in current fleet. This is today's first action.
3. ⏳ **Steve: platform decision doc** — lawyer-build-agent healthy at Iter 45; doctor apply-templates.js still ungreenlighted.
4. ⏳ **am-recrawl: kill or diagnose** — no resolution; no am-recrawl visible in PM2 fleet (may have died or was killed without note).

---

## 2. Overnight

**Crashes / instability:**
- `ventura-corridor` — restarts=13 ⚠️ — most unstable process in fleet; shipped v1 5 hours ago, suggesting crash loop post-deploy.
- `commerce-claw` — restarts=7 — abnormal; no recent commits to explain it.
- `sf-viewer` — restarts=5 — Site Factory viewer flapping; sf-orchestrator is stable.
- `george-gmail`, `site-wholivedthere`, `ai-factory-orchestrator`, `archive-agent`, `retrowalls` — all at restarts=4.

**Long-running jobs:**
- `small-business-builder` — deployed to Kamatera 14h ago with full schema migrations 002-008. Confirm live.
- `ventura-corridor` — v1 shipped 5h ago; currently crashing. Needs immediate triage.
- `pd-crawler` / `pd-dedupe` — both at restarts=3, uptime=18h (new restart cycle overnight). Doctor pipeline active.
- `ai-factory-viewer` — uptime=1h indicates a very recent restart.

**External signals:** No collaborator commits. All activity is Steve's own agents.

---

## 3. Today's Plan

1. `Steve — rotate george-gmail OAuth credentials — 7 days overdue, restarts=4 signals auth churn — outbound mail verified sending`
2. `debugger — triage ventura-corridor crash loop (restarts=13, v1 shipped 5h ago) — likely post-deploy startup error — process stable with restarts=0 for 30min`
3. `debugger — investigate commerce-claw restarts=7 — no commits, unclear cause — root cause identified + fix or kill decision`
4. `Steve — greenlight doctor apply-templates.js sample run — apply-templates.js merged 3 days ago, no sign-off yet — explicit go/no-go stated`
5. `lawyer-build-agent — continue Iter 46+ autonomously — no intervention needed — monitor commit cadence`
6. `pm2-crash-watcher — audit sf-viewer, site-wholivedthere, ai-factory-orchestrator (all restarts=4) for shared root cause — three independent restarts is suspicious — single upstream dependency or config identified`

---

## 4. Blockers Steve Owes

- **george-gmail OAuth rotation** — nothing blocks execution except Steve doing it.
- **Doctor platform go/no-go** — apply-templates.js is merged; no greenlight = no production mockup rotation.
- **commerce-claw + archive-agent** — unknown what these serve; no README or commit context. Steve needs to ID them or authorize kill.
- **ventura-corridor v1** — just shipped; crash loop may need Steve's eyes on the deploy config.

---

## 5. One Thing to Think About

ventura-corridor hit restarts=13 within 5 hours of v1 launch — that's a crash loop, not a flap. Before any other new site launches (smb-builder just deployed too), is there a common startup pattern (missing env var, port collision, missing DB migration) that's repeating across new deploys?