Skip to content

[repo-truth] reconcile stale operational docs - #424

Merged
i-xtsu-sixyou-ken-mei merged 1 commit into
mainfrom
docs/repository-truth-20260909
Sep 9, 2026
Merged

[repo-truth] reconcile stale operational docs#424
i-xtsu-sixyou-ken-mei merged 1 commit into
mainfrom
docs/repository-truth-20260909

Conversation

@i-xtsu-sixyou-ken-mei

Copy link
Copy Markdown
Collaborator

Stale claim

docs/architecture/current.md still says production Supabase migrations are manual operator actions after merge, including an explicit db push --dry-run / operator db push sequence.

Canonical evidence

Current .github/workflows/ci.yml owns production migration application through deploy-supabase-migrations on non-PR runs. The job:

  • runs in the production environment;
  • serializes under supabase-production-migrations;
  • links the production project;
  • runs supabase db push --dry-run;
  • runs supabase db push;
  • verifies no migrations remain pending;
  • is a dependency of 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.yml and does not add policy beyond that workflow.

Other reviewed candidates

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.

@i-xtsu-sixyou-ken-mei
i-xtsu-sixyou-ken-mei merged commit da74d7f into main Sep 9, 2026
12 checks passed
@i-xtsu-sixyou-ken-mei
i-xtsu-sixyou-ken-mei deleted the docs/repository-truth-20260909 branch September 9, 2026 01:49
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.

1 participant