[repo-truth] reconcile stale operational docs - #424
Merged
Conversation
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.
Stale claim
docs/architecture/current.mdstill says production Supabase migrations are manual operator actions after merge, including an explicitdb push --dry-run/ operatordb pushsequence.Canonical evidence
Current
.github/workflows/ci.ymlowns production migration application throughdeploy-supabase-migrationson non-PR runs. The job:productionenvironment;supabase-production-migrations;supabase db push --dry-run;supabase db push;deploy-fly, so Fly deployment waits for migrations.This is repository-defined behavior; no production-only state is inferred.
Outcome
Update — change only the architecture ownership wording so production migration apply/verify belongs to the CI migration job rather than a manual laptop/operator path. Keep
supabase/migrations/as migration-history source of truth and do not duplicate pooler/credential mechanics.Why this is not speculation
The old architecture text directly contradicts the checked-in CI workflow. The correction describes only behavior encoded in
ci.ymland does not add policy beyond that workflow.Other reviewed candidates
SOCIAL_RELEASE_SLOTS/ daily-cap contract rather than changing that contract.AGENTS.mdexception. Landing remains static, account-engine owns the bounded public persistence route, and Control Center reads demand evidence. No second copy of those details is added here.mainrepository truth.Scope
Docs-only:
docs/architecture/current.md, 3 additions / 3 deletions. No implementation, tests, workflows, migrations, config, CI/security/coverage/dead-code/duplicate gates, or secrets changed.