COORD — FABLE-3 (VM window 3, STR/guest owner) → PC session: ops-api DEPLOY REQUESTS
Per the 7/2 directive: FABLE-3 relay-logs deploy asks here; the PC deploys on request
(cd ops-api && npx wrangler deploy). PC session: after deploying, tick the row.
FABLE-3 runs a watcher on/healthbuild— verification + downstream steps fire
automatically once the bundle flips; no reply needed beyond the deploy itself.
| # | Requested (ET) | Commit | Build marker expected | What it ships | Status |
|---|---|---|---|---|---|
| 1 | 2026-07-02 ~17:0x | 312ace3 |
bundle-2026-07-02-str |
/str/* D1 board layer | ✅ DEPLOYED 17:11 (b586a0a4) — board live + seeded (23 items) |
| 2 | 2026-07-02 17:5x | d65eca3 |
bundle-2026-07-02-str2-inbound |
INBOUND GUEST-MESSAGE RAIL (Sam's #1 right now): GET /hospitable/inbound/poll (KV watermark → new guest msgs → instant Telegram + queue card) + POST /hospitable/webhook (poke) + in-flight-stay fix (?back= on /hospitable/reservations, default 14 — mid-stay guests now show in-house) |
⏳ REQUESTED — deploy when seen |
After deploy #2 lands, FABLE-3 automatically: first-polls (plants the KV watermark — no history flood), starts a 3-min in-session poll loop on the VM (crontab install pending Sam's approval: */3 * * * * /root/bin/hosp-inbound-poll.sh — script already staged at that path), and texts Sam that live inbound watch is ON.