arc42-synclisted

# arc42 sync arc42 fails in a predictable way: twelve chapters get created, three are filled, nine keep their template prose, and within two quarters the three that were filled are wrong. Nobody notices, because nothing checks them. The fix is to treat the chapters as three different kinds of document. Some are derivable from the code and therefore checkable. Some are human knowledge that no amount of analysis produces. Confusing the two is what fills a repository with confident, stale prose. ## The three kinds of chapter Every chapter carries its kind in its header. The drift check only fires on **generated** ones. | # | Chapter | Kind | Source | |---|---|---|---| | 1 | Einführung und Ziele | **human** | Stakeholders, quality goals — nothing in the code says why the system exists | | 2 | Randbedingungen | **assisted** | Tech constraints from manifests and CI; organisational ones from people | | 3 | Kontextabgrenzung | **generated** | External systems from config, base URLs, third-party SDKs, auth provider | | 4 | Lösungsstrategie | **human** | The reasoning behind the approach | | 5 | Bausteinsicht | **generated** | Project list and dependency graph from `docs/agent/repo-map.md` | | 6 | Laufzeitsicht | **assisted** | Scenarios traced with `feature-trace`; which scenarios matter is a human call | | 7 | Verteilungssicht | **generated** | CI/CD pipelines, infrastructure config, deployment targets | | 8 | Querschnittliche Konzepte | **assisted** | Auth, error handling, i18n