chore: untrack deliverables committed by mistake, and home the stray files

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>

.gitignore

@@ -35,8 +35,12 @@ deploy/portainer.env
 output/local/
 output/security/
 
-# Keep the roadmap generator, not its extracted text or render-review scratch.
-tmp/*
-!tmp/pdfs/
-tmp/pdfs/*
-!tmp/pdfs/generate_dtf_report.py
+# Scratch only. The roadmap generator moved to tools/, the PDFs to docs/.
+tmp/
+
+# Client deliverables and scratch inputs live here but are not the repository's
+# to version: they are produced for a specific week, or dropped in to test with.
+Relatorio-*.docx
+Relatorio-*.pdf
+imagem-teste.*
+output/documents/

CONTEXT.md

@@ -357,10 +357,9 @@ for this local implementation checkpoint.
 The prototypes they describe (`portal/`, `kanban/`, `agente/`, the root
 `schema.sql` and `.env.exemplo`) were removed on 2026-09-21 once nothing
 referenced them; recover from Git history if ever needed.
-- `tmp/pdfs/generate_dtf_report.py`: generator for the current client-facing
-  roadmap PDF.
-- `output/pdf/dtf-plano-producao-e-roadmap.pdf`: current generated roadmap.
-- `Reunião iniciada às 2026_09_09 09_39 GMT-03_00 - Anotações do Gemini.pdf`:
+- `tools/generate_dtf_report.py`: generator for the client-facing roadmap PDF.
+- `docs/roadmap-cliente.pdf`: the generated roadmap, as last sent.
+- `docs/reuniao-2026-09-09-anotacoes.pdf`:
   meeting notes that established the business direction. Treat it as context;
   the latest decisions in this document define the active scope.
 
@@ -384,8 +383,7 @@ referenced them; recover from Git history if ever needed.
 
 `context.md` is the compact operating context for agents. The current
 client-facing narrative, diagrams, and formatting live in
-`output/pdf/dtf-plano-producao-e-roadmap.pdf`, generated from
-`tmp/pdfs/generate_dtf_report.py`.
+`docs/roadmap-cliente.pdf`, generated from `tools/generate_dtf_report.py`.
 
 When a decision changes, update both the relevant implementation context here
 and the roadmap source when it changes what the client-facing plan promises.

ROADMAP.md

@@ -1,8 +1,8 @@
 # DTF System — Working Roadmap
 
 > Internal engineering tracker. Not a client document, not a promise sheet.
-> The client-facing narrative lives in `output/pdf/dtf-plano-producao-e-roadmap.pdf`
-> and in the weekly report (`Relatorio-Semana-1-DTF.docx`).
+> The client-facing narrative lives in `docs/roadmap-cliente.pdf` and in the weekly
+> report, which is a deliverable and is not versioned here.
 >
 > Update the **Current step** line and the item status every time something moves.
 > Add new findings at the bottom of the relevant block rather than rewriting history.

docs/README.md

@@ -0,0 +1,15 @@
+# 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.