Align documentation with clean baseline

This commit is contained in:
2026-07-31 16:41:37 +02:00
parent facf788ce8
commit 43a3bb0b69
7 changed files with 91 additions and 122 deletions
+4 -4
View File
@@ -559,11 +559,11 @@ PostgreSQL should be introduced when shared multi-user operation, background job
Goal:
After the legacy consumer path has been removed, provide one accurate entry point for developers, contributors and LLM-assisted work.
With the former Consumer path removed, provide one accurate entry point for developers, contributors and LLM-assisted work.
Timing:
- perform the final rewrite after legacy cutover so the documentation describes only the supported architecture
- keep the post-cleanup documentation limited to the supported architecture
- update documentation incrementally during earlier phases, but do not present transitional paths as the long-term design
README target structure:
@@ -618,8 +618,8 @@ Implemented handoff:
- README is a concise setup and project entry point without prototype status lists
- `docs/README.md` separates current, operational, future, specification and archived material
- current runtime and module boundaries are documented without unsupported
upgrade-only data paths
- current runtime and module boundaries are documented without compatibility
paths for unsupported pre-release data formats
- contributor workflow covers clean databases, safe demo data, migrations, tests and commits
- development Compose is clearly separated from the currently unsupported production deployment
- `AGENTS.md` points LLM-assisted work to supported code paths and deferred architecture