docs: governance reset + operational status sync#45
Closed
ByteStreams-AI wants to merge 1 commit intomainfrom
Closed
docs: governance reset + operational status sync#45ByteStreams-AI wants to merge 1 commit intomainfrom
ByteStreams-AI wants to merge 1 commit intomainfrom
Conversation
| See [docs/project-status.md](docs/project-status.md) for milestone tracking and [developer/developer-journal.md](developer/developer-journal.md) for the chronological narrative. | ||
| **May 5, 2026 governance reset.** After PR #28→#30 regressed the voice-call path twice in a single afternoon, the team installed an operational gate around shipping. New baseline: | ||
|
|
||
| - Two-environment topology: `main` deploys to a staging cloud (`mxhyvvgjtqllohpvrwon` Supabase + `*-staging.dialtone.menu` Workers + `+1 629 250 3998` Telnyx); `prod` deploys to production (`klzznfagrtormretqsgb` + `*.dialtone.menu` + `+1 629 600 1047`). Releases are PRs `main → prod` after staging verification. Branch protection on `prod` enforces PR + CI + linear history + squash-only. |
Contributor
There was a problem hiding this comment.
Live Telnyx phone numbers committed to the repository
The staging (+1 629 250 3998) and production (+1 629 600 1047) Telnyx numbers are new additions to the repo via this PR. If the repository is public (or becomes public), these numbers are discoverable and could attract spam/robocall traffic or testing abuse. Supabase project refs (mxhyvvgjtqllohpvrwon, klzznfagrtormretqsgb) are already present across many other files so this is not a new exposure for those — but the phone numbers only appear in the files touched by this PR.
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #44
Sync AGENTS and developer journal with the May 5 governance reset and staging/prod operating model, plus local Claude settings update.
Greptile Summary
Documentation-only sync following the May 5, 2026 governance reset: AGENTS.md and the developer journal are brought up to date with the new two-environment staging/prod topology, four governance rules, and a day's worth of voice-path bisect work.
.claude/settings.jsonaddsgit fetch *to the permitted Bash command list.AGENTS.mdgains the governance-reset block (two-environment topology, four rules, pointers todocs/project-status2.mdanddocs/git-policy.md), marks known-issue docs: refresh README + AGENTS + journal for end-of-day handoff #5 as fixed in PR PR - infra: stand up staging environment (separate Supabase + Telnyx + Vapi) #36, and adds known-issue feat(vapi): Path B — rewrite vapi_call_start to Vapi server-URL contract #8 documenting the Telnyx SIP Connection vs Voice API Application name-collision gotcha that caused a multi-hour debug on May 5.developer/developer-journal.mdadds a detailed May 5 entry covering governance reset (PR docs: clean-start project status + git policy #35), staging env provisioning (PR PR - infra: stand up staging environment (separate Supabase + Telnyx + Vapi) #36 + cloud-side sub-tasks A–F), prod branch as deploy gate (PRs PR - chore(ci): run CI on push to prod branch #40, chore(infra): create prod branch + branch protection rule #39), three rounds of voice-path bisect, and the Telnyx routing misconfig discovery.Confidence Score: 4/5
Safe to merge — all three files are documentation or local settings with no functional code changes.
The only concern introduced by this PR is committing live Telnyx phone numbers (staging and production) into the repository for the first time. Everything else — the governance narrative, journal entry, and git fetch permission — is straightforward documentation housekeeping with no code impact.
AGENTS.md — contains the newly committed phone numbers; worth a quick decision on whether this is intentional given the repo's visibility.
Security Review
+1 629 250 3998(staging) and+1 629 600 1047(production) Telnyx numbers appear inAGENTS.mdanddeveloper/developer-journal.mdfor the first time. If the repository is or becomes public these numbers are discoverable and could attract abuse traffic.mxhyvvgjtqllohpvrwon,klzznfagrtormretqsgb) are already widely present across the codebase pre-PR and are not a new exposure here.Important Files Changed
git fetch *to the allowed Bash commands list — a routine and low-risk addition.Reviews (1): Last reviewed commit: "update docs" | Re-trigger Greptile