beb6ddc5e5
All docs moved with git mv so --follow preserves history. Flattens the single-folder layout into goal-oriented folders and adds a README.md index at every level. - docs/README.md — new landing page with "I want to…" intent table - docs/architecture/ — overview, data-model, app-design - docs/features/ — billing-payments, cpe-management, vision-ocr, flow-editor - docs/reference/ — erpnext-item-diff, legacy-wizard/ - docs/archive/ — HANDOFF-2026-04-18, MIGRATION, status-snapshots/ - docs/assets/ — pptx sources, build scripts (fixed hardcoded path) - roadmap.md gains a "Modules in production" section with clickable URLs for every ops/tech/portal route and admin surface - Phase 4 (Customer Portal) flipped to "Largely Shipped" based on audit of services/targo-hub/lib/payments.js (16 endpoints, webhook, PPA cron, Klarna BNPL all live) - Archive files get an "ARCHIVED" banner so stale links inside them don't mislead readers Code comments + nginx configs rewritten to use new doc paths. Root README.md documentation table replaced with intent-oriented index. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
1.3 KiB
1.3 KiB
Archive
Do not edit these files. They're frozen snapshots kept for historical context. Internal links inside archived docs still point at the pre-reorganization paths (e.g.
ARCHITECTURE.md) — that's intentional so they read as they did at the time.
For the current state of the system, go back to docs/README.md or roadmap.md.
Contents
| File | What it is |
|---|---|
| HANDOFF-2026-04-18.md | The single-page doc index as it stood before the 2026-04-22 reorganization |
| MIGRATION.md | Legacy gestionclient (MariaDB) → ERPNext migration: table-by-table mapping, completion log |
| LEGACY-ACCOUNTING-ANALYSIS.md | April 2026 audit of the legacy PHP/MariaDB accounting system, informed the migration plan |
| status-snapshots/ | Dated "state of the system" write-ups from individual work sessions |
Why these still exist
Old snapshots capture context that doesn't belong in the evergreen docs: what someone was worried about on a specific date, what tradeoffs we considered and rejected, what shipped in a given sprint. When reading, assume code examples and doc paths have drifted — verify in the current code before acting on them.