8dd60cf962
* docs(A6): freshness audit da #27 no plano de dobradinhas 2026 electionInsights.ts foi deletado no Pass 2 W4a (modulo puro novo), electionAlliances.ts nao nasce (campoParties + electionPartySpectrum ja carregam a taxonomia), questoes em aberto resolvidas (tiers, score, proporcionais, lockdown de lideranca), card na aba Eleicoes, overview da lista fora de escopo, cache election-tse com bust na conciliacao Fase 5. Co-authored-by: Francisco Solla <fsolla@users.noreply.github.com> * feat(A6): insight de dobradinhas 2026 na aba Eleicoes do municipio Lista ranqueada de candidatos proporcionais que concorrem de novo em 2026 (runningAgain2026=sim) por geografia do municipio: score 0,6 alinhamento (campo 2026 + espectro Bolognesi) + 0,4 forca local normalizada pelo maximo do conjunto. Estado pendente ate a conciliacao pos-15/08; Solla excluido (referencia, nao parceiro); leitura derivada sem escrita; loader cacheado sob a tag election-tse como os irmaos; link para /campanha/dobradinhas como caminho de registro operacional. Co-authored-by: Francisco Solla <fsolla@users.noreply.github.com> * test(A6): cobertura unit/int do insight + lease das colecoes eleitorais Unit: tiers (campo/espectro/falha-para-o-meio), score, ordenacao, empates, limite, zero votos. Int: pending2026 sem conciliacao (mesmo com votos locais), so adversarios, misto com exclusao de Solla/nao e geografia alheia. Lease advisory election-collections serializa os dois specs que tratam as colecoes eleitorais como test-owned (o import wipe-all apagaria as fixtures do novo spec no meio do assert, 48-way paralelo). Co-authored-by: Francisco Solla <fsolla@users.noreply.github.com> * refactor(A6): fixes do /simplify (3 reviewers paralelos) P1: campo coalition morto removido do input/select/mapping (sem consumidor). P1: hooks do lease com timeout explicito de 120s nos dois specs eleitorais (o wait advisory passa dos 10s default do Vitest sob contencao — flake em ambas as direcoes). P2: sonda de conciliacao via payload.count (idioma da casa), desempate final por candidateNumber (ordem deterministica), geography como prop na secao (sem lookup duplicado), casing Dep. Federal/Estadual alinhado, marcador 1313 via BASELINE_TICKET_2022, entrada no CHANGELOG. Declinados com justificativa: zones como tupla nao-vazia (churn em tipo compartilhado por assert provada no catalogo) e early-start da promise antes do Promise.all (loader-dentro-do-Suspense e o idioma da casa; ganho so em cache frio). Co-authored-by: Francisco Solla <fsolla@users.noreply.github.com> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: Francisco Solla <fsolla@users.noreply.github.com> |
||
|---|---|---|
| .agents/skills | ||
| .cursor | ||
| .github | ||
| .husky | ||
| .impeccable | ||
| .vscode | ||
| .zed | ||
| docker/postgres/init | ||
| docs | ||
| public | ||
| scripts | ||
| src | ||
| tests | ||
| .cursorignore | ||
| .env.example | ||
| .env.test | ||
| .gitignore | ||
| .npmrc | ||
| .prettierignore | ||
| .prettierrc.json | ||
| .yarnrc | ||
| AGENTS.md | ||
| components.json | ||
| DESIGN.md | ||
| docker-compose.yml | ||
| Dockerfile | ||
| eslint-legacy-ignores.mjs | ||
| eslint-local-rules.mjs | ||
| eslint.config.mjs | ||
| knip.json | ||
| next.config.mjs | ||
| package.json | ||
| playwright.config.ts | ||
| pnpm-lock.yaml | ||
| postcss.config.mjs | ||
| PRODUCT.md | ||
| README.md | ||
| skills-lock.json | ||
| tailwind.config.ts | ||
| test.env | ||
| tsconfig.json | ||
| vercel.json | ||
| vitest.config.mts | ||
| vitest.setup.ts | ||
| vitest.unit.config.mts | ||
Teqo
Cheatsheet de operação agentic (humanos) — o fluxo em 5 linhas:
- O agente roda
pnpm agent:claime pega a próxima Issuereadypor prioridade (prio:P0..P3).- Ele implementa, roda o fast gate (
lint + typecheck + unit) e abre PR parastage— sozinho, e para aí.- CI verde → o PR mergeia em
stageautomaticamente; o merge roda o CI de stage contra o clone Neon de prod.- Você promove quando quiser:
pnpm agent:promote -- --i-am-human(PRstage→main, merge só com CI stage + PR green).- Semanalmente:
pnpm db:refresh:stagerenova o snapshot do stage a partir de prod (humano, requerNEON_API_KEY).Comandos:
pnpm agent:claim | agent:register | agent:prioritize | agent:file-miss | agent:promoteepnpm db:seed:minimal | db:refresh:stage. Labels: estadoready|in-progress|blocked|done|in-prod,prio:P0..P3,kind:*,needs:migration|consent,requirements-changed. Agente faz sozinho: claim → implementar → PR → stage. Só humano: promotestage→main, refresh do stage, envs Vercel/Neon,pnpm buildcontra banco remoto. Tudo em detalhe:docs/AGENT-OPS.md· CI:.github/workflows/ci-pr.yml+ci-stage.yml+ci.yml.
Teqo starts as the official digital platform for deputado Jorge Solla and evolves into a white-label civic engagement platform for politicians in Brazil.
The goal is to help political teams build direct, durable relationships with their base without depending on Big Tech social platforms as the primary channel.
Mission
- Strengthen direct communication between representatives and citizens.
- Reduce platform dependency risk by owning audience and data channels.
- Provide reusable building blocks so each political team can launch quickly.
Product Direction
Phase 1: Jorge Solla Website
Initial delivery focuses on Jorge Solla's public website, editorial CMS, and the internal /campanha tool:
- Public-facing content and updates (news/
post+taglive) - Institutional pages and biography (still pending a
Pagescollection) - Internal campaign operations: electoral nuclei, leaderships, estimates, updates, WhatsApp invites
- Editorial operations through Payload CMS
Phase 2: White-Label Platform
Teqo then becomes a configurable base product for other politicians in Brazil:
- Multi-tenant and reusable architecture
- Brand and content customization per mandate/campaign
- Shared core modules for communication and engagement
- Operational autonomy with self-hosted owned channels
Local Development
Production safety: the production database is a live Neon Postgres holding real citizens' data. Local development and tests run against a local Postgres and must never point at production.
pnpm devrefuses to start against a non-local database, and the test suite refuses any database whose name doesn't end in_test.
First-time setup
- Install dependencies:
pnpm install - Create your env file:
cp .env.example .env.local - Start Docker, then start the local database:
pnpm db:start- This runs Postgres 17 (matching production) and auto-creates a
teqo_testdatabase for the test suite.
- This runs Postgres 17 (matching production) and auto-creates a
- Make sure
DATABASE_URLin.env.localpoints at local:DATABASE_URL=postgresql://teqo:teqo@localhost:5432/teqo - Load a schema + content into the local database — pick one:
- Mirror production content (recommended):
PROD_DATABASE_URL="<unpooled Neon URL>" pnpm db:pullCopies production's schema and content into local. It only reads production and excludes supporter PII (contact/signature/subscriptiondata). - Empty schema from migrations:
pnpm migrate
- Mirror production content (recommended):
- Start the dev server:
pnpm dev - Open:
http://localhost:3000
Useful scripts: pnpm db:start / pnpm db:stop (local Postgres), pnpm db:pull (refresh local content from prod), pnpm db:seed:posts (import news posts/tags fresh from the live jorgesolla.com.br site into the local db; idempotent by slug, refuses a non-local database), pnpm db:seed:tse (import TSE 2014/2018/2022 Bahia election results into the local db; idempotent per year/office/turn scope, refuses a non-local database), pnpm build:election-aggregates (regenerate the committed TSE aggregate artifact in src/lib/electionAggregates/ from locally seeded data).
Content & cache revalidation
Public news pages (/[type], /[type]/[category], articles, and the home news list) are cached under a shared posts tag. Editing a post or tag in the deployed admin self-revalidates via afterChange hooks. Any write that bypasses the deployed runtime — a direct-DB seed (pnpm db:seed:posts), SQL, Onda 0 migrations, or a restore — does not bust production's cache, so afterwards call the secured endpoint:
# News (default tag: posts)
curl -X POST "https://<prod-domain>/api/revalidate" -H "x-revalidate-secret: $REVALIDATE_SECRET"
# Privacy policy after Onda 0 provision (tag: global_privacy-policy)
curl -X POST "https://<prod-domain>/api/revalidate?tag=global_privacy-policy" -H "x-revalidate-secret: $REVALIDATE_SECRET"
REVALIDATE_SECRET must be set in the Vercel production env (see .env.example). See the "Posts & Tags" section of AGENTS.md for the full model.
Database migrations
Schema is managed by committed Payload migrations (src/migrations/); push is disabled everywhere.
To change the schema:
- Edit the collection/global/field config.
- Generate a migration:
pnpm migrate:create <name> - Review and commit the generated files in
src/migrations/(both.tsand.json, plusindex.ts). - Apply it locally:
pnpm migrate(check status anytime withpnpm migrate:status).
Deploying to production: pnpm build runs payload migrate before building, so every Vercel deploy automatically applies pending migrations to the production database. Do not run migrations against production by hand.
Running tests
Tests use the isolated teqo_test database (config in .env.test). Prepare its schema once with:
DATABASE_URL=postgresql://teqo:teqo@localhost:5432/teqo_test pnpm migrate
Then run:
pnpm test— unit + integrationpnpm test:e2e— Playwright (requires the test DB schema and a free port)pnpm test:all— unit + integration + E2E
Quality gates (also enforced by CI on the GitHub mirror): pnpm lint (zero warnings — --max-warnings=0), pnpm typecheck, and pnpm exec knip (dead files/dependencies fail; delete what your change orphaned). Standards: .cursor/rules/engineering-standards.mdc.
Tech Stack
- Payload CMS
- Next.js
- PostgreSQL (via
@payloadcms/db-postgres) - TypeScript
Campaign (/campanha)
Internal campaign tool for electoral nuclei, local leaderships, vote estimates, field updates, and WhatsApp invites. Authenticated separately from /admin via the campaignUser collection (geral / coordenador / lideranca). Operational status and decisions: .cursor/rules/projects/nucleos-eleitorais.mdc. Conventions and deploy checklist: AGENTS.md (“Campaign auth” / “Campaign nuclei MVP”).
Production blocker: do not load real leadership data or enable invites until counsel-approved Consent.key = 'lideranca-autopreenchimento' exists. Absolute invite URLs require NEXT_PUBLIC_SITE_URL as an exact HTTPS DNS origin in production.
Roadmap
Backlog and future plans live as tracked GitHub Issues (spec + deps + prio + model per issue; flow skills: plan-issue → work-issue → project-status; docs/roadmap.md is a frozen legacy stub).