66ddb17f02
All checks were successful
Build and deploy / Validate source (push) Successful in 10s
Build and deploy / Integration suite on a real stack (push) Successful in 1m47s
Build and deploy / Secret scan and release gate (push) Successful in 7s
Build and deploy / Publish images and notify Portainer (push) Successful in 1m38s
The previous commit used git add -A and swept in four binaries that were deliberately untracked: the week-1 client report as .docx and .pdf, a duplicate of it under output/documents, and imagem-teste.jpg, an input dropped in to test with. None of them are the repository's to version. They are untracked here, left on disk, and covered by .gitignore so the mistake cannot repeat. Three files had no sensible home. The meeting notes sat at the repository root under a 78-character name with spaces and accents, the roadmap generator lived in tmp/ — a directory otherwise ignored as scratch — and its output in output/, which is otherwise generated evidence. They are now docs/reuniao-2026-09-09- anotacoes.pdf, tools/generate_dtf_report.py and docs/roadmap-cliente.pdf, with CONTEXT.md and ROADMAP.md updated to match and a docs/README.md saying what each document is for. .gitignore no longer needs four rules to keep one generator out of an ignored directory; tmp/ is scratch again. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Documents
| File | What it is |
|---|---|
reuniao-2026-09-09-anotacoes.pdf |
Meeting notes that set the business direction: the bottleneck, the 24h goal, the automation and payment decisions. Still the record of what was asked for. |
roadmap-cliente.pdf |
The client-facing plan, as last sent. Generated by tools/generate_dtf_report.py; regenerate rather than edit. |
historico/ |
The original specification and prototype documents. Background only — they describe a model this system does not implement. |
Current engineering documents live at the repository root: CONTEXT.md for how
the system works, ROADMAP.md for what is outstanding, LOCAL_SETUP.md to run
it, PORTAINER.md to deploy it, SECURITY_REPORT.md and PRODUCTION_INPUTS.md
for the security position and the decisions still owed by the client.
Weekly client reports are deliverables, not repository content. They are produced for a specific week and are deliberately not versioned here.