chore: remove the abandoned prototypes and archive what described them

portal/, kanban/ and agente/ were 2,034 lines implementing the original
Tiny-first model: token upload links, a second SQLite Kanban, a factory agent.
Nothing imported or started any of it, and several endpoints took the acting
user from the request body with no authentication at all. Their real cost was
that a reader arriving at this repository found two Kanbans and two portals and
had to work out which one was real. The root schema.sql and .env.exemplo went
with them: both code paths load local/schema.sql, and having .env.exemplo beside
.env.example differing by one letter was a trap rather than a convenience.

The documents describing that model are archived rather than deleted. They
record decisions and reasoning the current documents do not repeat, so they are
worth keeping as background, with a header saying plainly that they are not
instructions.

README.md keeps its business case — the capacity figures and the cost argument
are still the reason this project exists — but now states where the prototype
documentation begins and that the code it describes is gone.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

CONTEXT.md

@@ -4,7 +4,7 @@
 
 Read this document before changing code, documentation, architecture, or scope.
 It is the current English source of truth for the project. It supersedes older
-decisions in `README.md`, `ESPECIFICACAO.md`, `schema.sql`, and the existing
+decisions in `README.md`, `docs/historico/ESPECIFICACAO.md`, `schema.sql`, and the existing
 prototype code whenever they conflict.
 
 Update this file whenever the team makes a material product, process, or
@@ -340,7 +340,7 @@ as references and are not imported or started by Compose.
   activation remain incomplete. Deployment plumbing exists but cannot pass its
   release gate yet. No factory automation or pre-flight is added.
 
-See `IMPLEMENTATION_REPORT.md` for verification, `PRODUCTION_INPUTS.md` for the
+See `docs/historico/IMPLEMENTATION_REPORT.md` for verification, `PRODUCTION_INPUTS.md` for the
 decisions and evidence required before staging or production connection, and
 `PORTAINER.md` for the production delivery contract.
 The client roadmap promises are unchanged, so its PDF source is not regenerated
@@ -348,13 +348,15 @@ for this local implementation checkpoint.
 
 ### Existing assets
 
-- `dtf-site.html`: rich static front-end prototype. It includes the current
-  commercial rules, client-side artwork analysis, current-session cart, and
-  delivery UI. The localhost checkout bridge connects it to the new local API.
-- `portal/`: early FastAPI prototype for the original Tiny-first, token-link
-  upload flow.
-- `kanban/`: early FastAPI/SQLite Kanban prototype.
-- `agente/`: factory-side agent prototype; out of current MVP scope.
+- `dtf-site.html`: the Site. Commercial rules, artwork analysis, cart and
+  delivery UI; its behaviour lives in `local/static/site-*.js`.
+- `docs/historico/`: the original specification, endpoint sketch, task plan and
+  status report. Background only — they describe a model this system does not
+  implement.
+
+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.