chore(ci): Postgres real no CI + regressão FTS + paridade da instrução#146
Merged
Conversation
…a instrução
A suíte tinha 1248+ testes mas o CI rodava `npm test` SEM Postgres/Voyage: a fatia
DB-dependente se auto-pulava (cobertura fantasma). Foi exatamente o que deixou o
bug do FTS (config divergente) passar despercebido.
- ci.yml: novo job `db-test` (não obrigatório ainda) com service pgvector:pg16 +
`npm run migrate` (cria unaccent + a config portuguese_unaccent) rodando a suíte
de storage contra Postgres real. Promover a obrigatório quando estável.
- storage.test.ts: teste de regressão real `searchKeyword('ervilha')` recupera o
doc (gateado por HAS_PG; roda no db-test). Guarda o "ervilha vazio".
- mcp-account-config.test.ts: paridade — owner E friend advertem brain_get_document
e proíbem remontar via brain_search.
build+test verdes (1267/1267).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…que ela depende) O CI com Postgres revelou que o migrate do zero falhava: 0001 (versão atual) já cria a config portuguese_unaccent + a coluna tsv que depende dela; 0002 então tentava DROP da config com a coluna ainda existindo -> erro de dependência. Em prod nunca apareceu porque o runner rastreia schema_migrations e não re-roda 0002. Reordena: dropa índice+coluna tsv ANTES de dropar/recriar a config. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Bloco B do plano pós-diagnóstico
O CI rodava
npm testsem Postgres/Voyage: a fatia DB-dependente se auto-pulava (cobertura fantasma) — exatamente o que deixou o bug do FTS passar.db-test(novo job, não obrigatório ainda): servicepgvector:pg16+npm run migrate(criaunaccent+ configportuguese_unaccent) rodando a suíte de storage contra Postgres real.searchKeyword('ervilha')recupera o doc (gateado porHAS_PG).brain_get_documente proíbem remontar viabrain_search.npm run build+npm testverdes (1267/1267). Odb-testvalida o fix de FTS do PR #145 contra Postgres real.🤖 Generated with Claude Code