Put the developer docs under docs/dev and index the folder for users first

docs/ had 26 developer documents flat beside the manual, and the two audiences are very differently sized: most readers want the manual and the gesture reference, a few want the register, the designs and the measurements. The manual and gestures.md stay at the top; everything for someone changing the code moves to docs/dev/, and the two documents that name their own successors — the v0.1 milestone and the UI-refinement plan — go to docs/dev/archive/ rather than being deleted, since both are still cited. docs/README.md is the index, users first. Every reference follows: code comments, Cargo manifests, the workflows, the pre-commit hook, the bench and traceability tools (which locate the repo root by docs/dev/requirements.md now), packaging, the Docker READMEs, CLAUDE.md, CONTRIBUTING.md and the README. The matrix links one level deeper and is regenerated. Links out of the moved documents into the tree gain a level; a link checker over every Markdown file finds none broken.
2026-09-20 16:20:15 +02:00
parent 08727cff5a
commit 6b1aac477d
137 changed files with 658 additions and 572 deletions
@@ -22,7 +22,7 @@
 //! the catalog holds has authoritative backing outside it, which is what makes
 //! a rebuild survivable — but a manual collection is a set of images the user
 //! assembled by hand and nothing in the filesystem records it
-//! (`docs/catalog.md` §8.1). So the labels say which one loses them, and the
+//! (`docs/dev/catalog.md` §8.1). So the labels say which one loses them, and the
 //! rebuild is not given the affirmative styling while a restore is on offer.
 //!
 //! # Why the scan is held back