docs(onda-9.2): handoff RCA + runbook supabase volumes#125
Merged
Conversation
Persiste no repositório a documentação produzida durante a Onda 9 (recuperação cirúrgica do Vault — 2026-05-09). ## Arquivos novos - docs/handoff-2026-05-09-onda-9-vault-recovery.md (+419 linhas) Doc-mãe: RCA, decisões D1-D11, recovery 24/24, 7 DEFER documentados, backlog de pendências externas. Versão REDACTADA — credenciais sensíveis substituídas por <REDACTED-*>. - docs/runbooks/SUPABASE-VOLUMES-DOS-AND-DONTS.md (+181 linhas) Runbook prático: volumes críticos, operações proibidas (DO NOT), procedimentos corretos (DO), caso histórico Onda 9, plano de migração futura (deprecação pgsodium). ## Por que dois arquivos - doc-mãe: histórico/forense da Onda 9 (consultar quando vault quebrar de novo) - runbook: manual operacional (consultar ANTES de tocar no stack supabase) ## Secrets Auditoria pré-commit: zero secrets críticos (api keys, passwords, account IDs) na versão pública. Versão original com plaintext permanece em /workspace/notes/ (acesso restrito). Ref: PR Onda 9.1 (#124) — migration SQL do healthcheck. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
WalkthroughEste PR documenta a recuperação completa do incidente Onda 9: corrupção de 31 ChangesOnda 9 — Vault Recovery & Prevention
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e3942acea1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
Pull request overview
This PR adds two operational documentation files to preserve the Onda 9 Supabase Vault recovery RCA/handoff and to provide a runbook for handling critical Supabase volumes safely (especially supabase_db_config / pgsodium_root.key).
Changes:
- Add a redactada “doc-mãe” detailing Onda 9’s RCA, recovery steps, outcomes, and backlog.
- Add a practical runbook with DOs/DON’Ts and safe procedures for volume backup/healthchecks/redeploys.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.
| File | Description |
|---|---|
| docs/handoff-2026-05-09-onda-9-vault-recovery.md | Incident handoff/RCA + recovery procedure + prevention backlog (redacted) |
| docs/runbooks/SUPABASE-VOLUMES-DOS-AND-DONTS.md | Operational runbook for critical Supabase volumes and safe handling practices |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Owner
Author
|
@coderabbitai full review |
✅ Actions performedFull review triggered. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/handoff-2026-05-09-onda-9-vault-recovery.md`:
- Around line 19-24: Fix the markdownlint warnings by adding explicit language
tags to all fenced code blocks (use ```text for those plain-text blocks) and
disambiguate duplicate headings titled "Estado atual" by renaming them to unique
headings (e.g., "Estado atual (F2)" and "Estado atual (encerramento F4)") so
MD040 and MD024 are resolved; update every occurrence of the triple-backtick
blocks and every "Estado atual" heading in the document and the other flagged
sections so the linter no longer reports missing code languages or duplicate
headings.
- Line 2: Remove all plaintext internal paths and infra location references from
the public handoff (e.g., the literal
'/workspace/notes/onda-9-vault-recovery-2026-05-09.md' shown in the header) and
replace them with non-sensitive, generic placeholders like
'<INTERNAL_NOTE_LOCATION>' or "internal secure storage (access-controlled)";
update any explanatory sentence to state that an internal plaintext copy exists
but do not include exact path or environment identifiers. Apply the same
sanitization to the other flagged ranges (around lines 250, 257-264, and
412-418) to redact hostnames, backup locations, container names, or any
environment-specific IDs, and ensure the file header and any footers mention
"sensitive details removed" rather than exposing infrastructure paths.
- Line 187: Corrija a contagem inconsistente alterando a string literal
"**Coletados: 23/31 | DEFER: 8/31**" para "**Coletados: 23/31 | DEFER: 7/31**"
(ou ajuste o número para refletir o estado final mostrado na lista), e
verifique/atualize quaisquer outras ocorrências do contador "DEFER" no documento
para manter consistência com a lista final.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 8ae22810-0642-4939-87c0-1e21256881a7
📒 Files selected for processing (2)
docs/handoff-2026-05-09-onda-9-vault-recovery.mddocs/runbooks/SUPABASE-VOLUMES-DOS-AND-DONTS.md
## Issue 1 (Major) — Sanitizar paths internos no doc público
CodeRabbit (linha 2): caminhos /workspace/notes/* expostos no doc
público facilitam enumeração de infra. Substituídos por placeholders
genéricos:
/workspace/notes/onda-9-vault-recovery-2026-05-09.md
→ 'armazenamento interno com acesso controlado'
/workspace/notes/runbooks/SUPABASE-VOLUMES-DOS-AND-DONTS.md
→ docs/runbooks/SUPABASE-VOLUMES-DOS-AND-DONTS.md (versionado)
/workspace/notes/backups/supabase_db_config_*.tar.gz
→ <internal-backup-storage>/supabase_db_config_*.tar.gz
/workspace/notes/backups/
→ 'armazenamento interno (acesso controlado)'
7 ocorrências em 6 linhas (2, 250, 257, 264, 307, 412, 418). Auditoria
pós-edit: 0 ocorrências de '/workspace' no documento.
## Issue 2 (Minor) — markdownlint warnings
CodeRabbit (linha 24): code blocks sem linguagem (MD040) + headings
duplicados (MD024).
- 5 code fences de abertura ganharam linguagem 'text' (linhas 19, 91,
234, 256, 396). Os 6 fences de fechamento permanecem sem linguagem
(não exigido pelo lint).
- 3 headings 'Estado atual' renomeados para únicos:
Linha 138: '## Estado atual (pós-F1 RCA)'
Linha 200: '## Estado atual (pós-F3 recovery)'
Linha 301: '## Estado atual (encerramento F4)'
CodeRabbit citou 2 duplicados; encontrei 3 — todos resolvidos.
## Issue 3 (Minor) — Inconsistência factual DEFER 8/31 vs 7/31
CodeRabbit (linha 187): linha 187 dizia 'DEFER: 8/31', mas o resto do
doc mostra 7/31. Bug factual corrigido.
Antes: '**Coletados: 23/31 | DEFER: 8/31**'
Depois: '**Coletados: 23/31 | DEFER: 7/31**'
## Validação final (auditoria 8/8 critérios)
1. Paths internos: 0 ✅
2. Code blocks sem linguagem: 6 (todos closing) ✅
3. Code blocks com linguagem: 6 ✅
4. Heading 'Estado atual' duplicado: 0 ✅
5. Heading 'Estado atual …' único: 3 ✅
6. DEFER: 8/31: 0 ✅
7. DEFER: 7/31: 1 ✅
8. Secrets sensíveis: 0 ✅
Resolves: CodeRabbit review comments #125 (linhas 2, 24, 187)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Owner
Author
|
@coderabbitai obrigado pelo feedback! Aplicadas as 3 correções em Issue 1 (Major) — Sanitizar paths internos ✅7 ocorrências de
Auditoria pós-edit: Issue 2 (Minor) — markdownlint MD040 + MD024 ✅MD040 (code blocks sem linguagem): 5 fences de abertura ganharam linguagem MD024 (headings duplicados): você citou 2 duplicados, encontrei 3. Todos renomeados:
Issue 3 (Minor) — Inconsistência DEFER 8/31 → 7/31 ✅Linha 187 corrigida: Auditoria final (8/8 critérios passaram)Pronto pra re-review. |
|
Iniciando re-review. ✅ Actions performedReview triggered.
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e0e1482fd5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
adm01-debug
added a commit
that referenced
this pull request
May 10, 2026
…128) Após merge dos PRs #124 e #125, descobri 4 review threads abertas de GitHub Copilot e ChatGPT Codex Connector que CodeRabbit não cobriu. Esse PR endereça as 4 críticas reais (P2/Minor mas válidas). ## Issue 1: Migration sem CREATE EXTENSION pg_cron (Copilot, P2) Localização: supabase/migrations/20260510131942_*.sql A migration usa cron.unschedule/cron.schedule mas não garante a extensão pg_cron. 3 outras migrations do projeto seguem o pattern defensivo (precedente): supabase/migrations/20260319134320_*.sql supabase/migrations/20260409013312_*.sql supabase/migrations/20260423174952_*.sql Em prod atual já está instalada (re-aplicação confirmou 'extension already exists, skipping' = no-op idempotente). Em ambiente novo, a anterior 20260423174952 já cria, mas adicionar aqui mantém defensive pattern e evita assumption. ## Issue 2: Vazamento parcial de credencial 429683... (Copilot, P2) Localização: docs/handoff-2026-05-09-onda-9-vault-recovery.md L228 L228 tinha: | F3.14 Test fn_get_vault_secret('evolution_api_key') | ✅ retorna '429683...' | Mesmo prefixo parcial pode ajudar em enumeração. CodeRabbit pediu sanitização similar nas linhas 2/250/257/264/307/412/418 mas não pegou a 228. Substituído por '<REDACTED-evolution-api-key-prefix>'. ## Issue 3: Referência a arquivo inexistente docker-compose-supabase.yml (Copilot, P2) Localização: docs/runbooks/SUPABASE-VOLUMES-DOS-AND-DONTS.md L130 + docs/handoff-2026-05-09-onda-9-vault-recovery.md L272, L390 O runbook recomenda 'docker stack deploy -c docker-compose-supabase.yml' mas esse arquivo não existe no repo. O nome real do compose Supabase self-hosted nesta VPS é '/root/supabase.yaml' (host filesystem), documentado em docs/DEPLOYMENT.md. Corrigido para apontar pra '/root/supabase.yaml'. ## Issue 4: Path interno /workspace/notes/backups/ no runbook L180 Localização: docs/runbooks/SUPABASE-VOLUMES-DOS-AND-DONTS.md L180 + supabase/migrations/20260510131942_*.sql L22 CodeRabbit pediu sanitização similar no handoff (linhas 250, 257, 264, 307, 412, 418 — todas resolvidas no PR #125), mas o runbook L180 e a migration L22 ainda tinham /workspace/notes/. Inconsistência corrigida: L180 → '<internal-backup-storage>/supabase_db_config_*.tar.gz' L22 → '-- Ref: internal incident record (Onda 9)' ## Validação Migration v3 aplicada em produção como idempotency test: NOTICE: extension 'pg_cron' already exists, skipping CREATE EXTENSION CREATE FUNCTION x3 (REPLACE) REVOKE x3 + GRANT x3 (idempotente) CREATE VIEW cron schedule | 51, 52 (reagendados) Smoke test: {'ok': 24, 'fail': 0, 'defer': 7, 'status': 'healthy'} Banco produção continua healthy. ACL hardening preservada. ## Auditoria final 9/9 critérios 1. Migration tem CREATE EXTENSION pg_cron: ✅ 1 ocorrência 2. Migration sem /workspace: ✅ 0 3. Handoff sem 429683: ✅ 0 4. Handoff sem docker-compose-supabase: ✅ 0 5. Handoff sem /workspace: ✅ 0 6. Runbook sem docker-compose-supabase: ✅ 0 7. Runbook sem /workspace: ✅ 0 8. Banco prod healthy pós-apply: ✅ healthy 9. Cron jobs ativos: ✅ 51 + 52 reagendados Resolves: 4 review threads abertas pós-PRs #124 e #125 - copilot-pull-request-reviewer: pg_cron L192, prefixo 429683 L228, docker-compose L130 - (descoberta na auditoria): /workspace L180 runbook, L22 migration 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude <noreply@anthropic.com>
Owner
Author
🧹 Encerramento das review threads (auditoria pós-merge)Auditoria completa realizada. Todas as 9 threads abertas pelos reviewers Copilot e Codex foram avaliadas e marcadas como Resolved: ✅ Endereçadas (correção em main)
🟡 Backlog aceito (não bloqueante)
Validação em produção (hoje): Onda 9 oficialmente arquivada. Documentação consolidada em |
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.
📚 Onda 9.2 — Persistir documentação do Vault Recovery
Companheiro do PR #124 (migration SQL). Este PR persiste no repositório a documentação produzida durante a Onda 9 — protegendo o conhecimento contra perda do container
claude-code(volátil).🎯 O que entra (2 arquivos, +600 linhas)
docs/handoff-2026-05-09-onda-9-vault-recovery.mddocs/runbooks/SUPABASE-VOLUMES-DOS-AND-DONTS.md📖 O que cada arquivo contém
docs/handoff-2026-05-09-onda-9-vault-recovery.mdCaptura forense completa da Onda 9, organizada em fases:
cp -pem 2026-04-29 corrompeu 31 secrets ao postgres reiniciar em 2026-05-06)Serve como referência de consulta quando alguém precisar entender:
DEFERnovault.secretsvault.secrets_snapshot_pre_fix_20260509)docs/runbooks/SUPABASE-VOLUMES-DOS-AND-DONTS.mdRunbook operacional (não-forense) com:
supabase_db_configPra ser consultado antes de tocar no stack supabase — não depois.
🔒 Auditoria de segurança
A doc-mãe original em
/workspace/notes/continha 6 credenciais em plaintext (linhas 155, 161, 165, 166, 178). Antes de copiar pro repo:429683C4...F7D57E11<REDACTED-evolution-api-key>463ef...<REDACTED-evolution-api-key-v1>AWefNN...wCBE<REDACTED-minio-access-key>@Promo2024<REDACTED-minio-password>AtomicaBR<REDACTED-minio-user>cd0f4eee...<REDACTED-r2-account-id>Auditoria pré-commit (
grep -nE "429683C4\|AWefNN\|@Promo2024\|cd0f4eee\|ptr_\|GOCSPX\|sefxwip\|AKIA\|sk-\|github_pat_"):docs/handoff-...md: 0 matchesdocs/runbooks/SUPABASE-VOLUMES...md: 0 matchesURLs públicas (
*.atomicabr.com.br) e o email corporativo (ti04.promobrindes@gmail.com) foram mantidos — são metadados públicos, não credenciais.A versão original com plaintext fica em
/workspace/notes/onda-9-vault-recovery-2026-05-09.md(acesso restrito ao container Claude Code).🎯 Por que está em
docs/e não só em/workspace/notes/Precedente: PR #113 (
docs: handoff completo encerramento faxina pré-deploy) já moveu handoff anterior pro repo pelos mesmos motivos:/workspace/notes/é volátil (container claude-code reseta) — não há garantia de persistênciadocs/é versionado junto com código — sobrevive a clones, deploys, backups🔍 Risco
🟢 Zero. Apenas adições em
docs/, sem mudança de código. Build/lint/CI não tocados.📋 Contexto Onda 9 (3 PRs)
✅ Backlog Onda 9 — pendências externas (não bloqueiam encerramento)
Documentadas no handoff. Dependem de inputs externos:
hf_api_token,openai_api_key,anthropic_api_key,openrouter_api_key) → recovery final 31/31minio_secret_key(MinIO offline, R2 substituiu)restore_test_ingest_token(sem caller localizado)supabase_db_config🤖 Review
@coderabbitai full review
🤖 Generated with Claude Code
Summary by CodeRabbit