DOCS-AUDIT

DOCS-AUDIT

Recursive docs pass for dev-docs only.

Task:
- inspect the relevant app route groups and schema-backed entities
- compare current dev-docs notes against the codebase status
- update markdown docs only
- do not modify application code
- keep old versions by moving them into the nearest archive/ folder
- add missing canonical docs for real schema-backed systems
- reduce duplication across sibling files
- keep each folder focused on one feature set or entity cluster

Rules:
- preserve all existing notes non-destructively
- prefer one active canonical note per topic
- use hub README files only as short folder entry points
- put deeper implementation details in the matching feature folder
- if a system exists in Prisma but is undocumented, add a contract doc
- if a note repeats another note, move the duplicate into archive
- write links so they resolve under the app's `/md/...` route
- avoid raw `http://localhost:3000/...` targets in markdown links

Output:
- updated markdown files
- new hub/contract docs where needed
- a brief status summary listing what was changed and what remains

1. Run the DOCS-AUDIT prompt.
2. Inspect app/ route groups and Prisma entities.
3. Update the matching dev-docs/ folder.
4. Move replaced versions into archive folders.
5. Stop after the first stable pass and report the delta.