Skip to content

docs: refresh README + AGENTS + journal for end-of-day handoff#5

Merged
ByteStreams-AI merged 1 commit intomainfrom
docs/end-of-day-followups
May 2, 2026
Merged

docs: refresh README + AGENTS + journal for end-of-day handoff#5
ByteStreams-AI merged 1 commit intomainfrom
docs/end-of-day-followups

Conversation

@Bytes0211
Copy link
Copy Markdown
Collaborator

@Bytes0211 Bytes0211 commented May 2, 2026

Summary

Captures the May 2 work after PRs #2/#3/#4 merged so picking up cold in 2–3 days doesn't require re-discovering anything.

README.md — bumped from "M1–M7 complete... Next: M8" to "M1–M8 complete, Path A demo proven live". Stack updated (Telnyx, not Twilio). "Where things live" table refreshed. Pointer to developer/m8-live-demo-checklist.md for the deploy runbook.

AGENTS.md — current-state header rewritten. Five new convention bullets covering the gotchas agents commonly miss (CORS preflight, auth init bootstrap, branding location/access, customer-facing route ownership, Stripe-three-environments). New "Open follow-ups" section at the bottom listing the three known pre-launch items — admin chrome branding, kitchen "Ready" SMS, Path B Vapi — each with scope and estimated effort.

developer/developer-journal.md — new dated entry "May 2 (later)" covering PRs #3 + #4, the dialtone_menu PR #27 reversal, the SQL cleanup of orphaned test orders, and the doc refresh itself. Decisions section explains the design choices (columns vs separate table, RPC scoped by order_id, helpers extracted for testability, hexToRgba fallback). Follow-ups mirror AGENTS.md so the same plan is visible from both surfaces.

Test plan

  • pnpm ci:fast green (220 unit tests, lint, typecheck)
  • Docs only — no behavior change

🤖 Generated with Claude Code

Greptile Summary

Documentation-only end-of-day handoff refresh across three files. README and AGENTS.md are updated to reflect M8 Path A going live (cloud Supabase, Stripe/Telnyx/Cloudflare end-to-end validated), and developer-journal.md adds a dated entry narrating today's PRs, decisions, and the three scoped follow-ups. No code changes — all content is internally consistent and accurately cross-references the prior PRs.

Confidence Score: 5/5

Docs-only PR with no code changes — safe to merge as-is.

All three files are documentation updates with no code or configuration changes. Content is factually consistent across files, cross-references resolve to real artifacts in the repo, and the known issues are honestly scoped with effort estimates. No P0/P1/P2 findings identified.

No files require special attention.

Important Files Changed

Filename Overview
README.md Status bump from M1–M7 to M1–M8, stack corrected from Twilio to Telnyx, "Where things live" table refreshed with new artifacts, new Deploy section added — accurate and internally consistent
AGENTS.md Current-state header rewritten for M8 live demo; five new convention bullets covering CORS, auth init, branding access, customer-facing route ownership, and Stripe env gotcha; new "Open follow-ups" section with scoped tasks and estimates
developer/developer-journal.md New "May 2 (later)" journal entry documenting PRs #3 and #4, the dialtone_menu reversal, SQL cleanup of orphaned test orders, and the doc refresh — decisions and follow-ups align with AGENTS.md

Reviews (1): Last reviewed commit: "docs: refresh README + AGENTS + journal ..." | Re-trigger Greptile

Captures the May 2 work after PRs #2/#3/#4 merged so picking up cold in
2-3 days doesn't require re-discovering anything.

README.md
- Status bumped from "M1–M7 complete... Next: M8" to "M1–M8 complete,
  Path A demo proven live"
- Stack updated (Telnyx replaces Twilio; Stripe Connect routing now
  M11 not M7)
- "Where things live" table refreshed: planned-migrations now empty,
  added Edge Function + payment + branding entries, called out that
  customer-facing post-payment pages live in admin (not the marketing
  site at dialtone_menu)
- Added pointer to developer/m8-live-demo-checklist.md for the deploy
  runbook + lessons learned

AGENTS.md
- Current state header rewritten — single paragraph covering today's
  four PRs and where to look next
- Conventions extended with five new bullets agents commonly miss:
  - Browser-callable Edge Functions need handlePreflight() (M8 lesson)
  - Auth init must bootstrap from getSession() before subscribing (PR #1)
  - Per-restaurant branding location + access patterns (RPC vs
    useAuth-loaded row) (PRs #3 + #4)
  - Customer-facing /orders/:id/{paid,cancel} live in admin app, not
    marketing site (PR #4)
  - Three-Stripe-environment gotcha (M8 lesson)
- New "Open follow-ups" section at the bottom with three items —
  admin chrome branding, kitchen Ready SMS, Path B Vapi — each with
  scope, estimated effort, and where to start

developer/developer-journal.md
- New dated entry "May 2 (later)" picking up after the existing
  May 2 entry (which only covered through Path A demo). Documents
  PR #3 + PR #4, the dialtone_menu PR #27 reversal, the SQL cleanup
  of orphaned test orders, and the doc refresh itself
- Decisions section: why columns on restaurants over a separate
  table, why RPC scoped by order_id over slug, why helpers extracted
  for testability, why hexToRgba falls back to opaque on bad input
- Follow-ups section mirrors AGENTS.md "Open follow-ups" — same
  three items so journal readers + agent readers see the same plan

220 unit tests still pass; lint + typecheck green.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@ByteStreams-AI ByteStreams-AI merged commit 7293a50 into main May 2, 2026
2 checks passed
ByteStreams-AI added a commit that referenced this pull request May 4, 2026
The deploy workflow ships admin + kitchen + Edge Functions on every
push to main, but does NOT run `pnpm supabase db push --linked`. M10
(PR #14) merged with migration 0012_m10_knowledge_rpcs.sql; the
Edge Function code deployed automatically but the migration never
landed in cloud. Discovered when `knowledge_reindex` returned a
generic 500 — OpenAI embed had been hit successfully (visible in
OpenAI dashboard) but the subsequent `knowledge_replace_chunks` RPC
call hit "function does not exist".

Two doc updates:

- developer/m8-runbook.md — adds a callout at the top of the
  Deployment + rollback section. Operators see this when they look
  up deploy procedure. Includes the verification SQL.
- AGENTS.md — adds Open follow-up #5 documenting the gap and
  proposing a fix path for M12/M13 (a separate `migrate.yml`
  workflow with a manual confirmation gate, not auto-push, since
  destructive migrations need human review).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants