2e03b0362b
All checks were successful
Build and deploy / Validate source (push) Successful in 6s
Build and deploy / Integration suite on a real stack (push) Successful in 2m33s
Build and deploy / Secret scan and release gate (push) Successful in 7s
Build and deploy / Publish images (push) Successful in 1m48s
Moves: an order can go back one stage (BACK in app/runtime.py) with an internal reason, flagged in the history as movements.back. The customer is not notified and approved finals stay; "production started" and "ready" are now enqueued once per order, so undoing and redoing a move sends nothing twice. Dragging only goes forward and highlights the allowed column. Move errors are in Portuguese. Lists: the send log, payments (open, resolved as history, all) and quotes are paged on the server with a total, 20 rows by default (10/20/50/100), first/previous/page/next/last. The send log filters by destination, status, event and order. Older finished orders load on demand. The board no longer carries the send log or payment rows, only the open-payment count. Kanban: Pagamentos and Integrações are separate tabs; messages are brief, bottom notifications that clear themselves; wording is shorter. Full CI integration sequence passes locally, with new checks for undo, paging and filters. Co-Authored-By: Claude Opus 5.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.