#101: Rebuild the repository's pages to one page structure

.claude/rules/docs-lifecycle.md

@@ -11,10 +11,15 @@ When a PR implements a `SPEC.md` section, that same PR must:
 1. **Delete** the implemented content from `SPEC.md` (the whole section, or the specific
    subsections that are now shipped).
 2. **Add** the equivalent, "what actually exists" description to the live docs:
-   - `README.md` for user-facing usage and examples: the action's commands, inputs and output;
-   - `DEVELOPER.md` for local-dev workflow, the quality gates and CI;
-   - the package's own `README.md` (`packages/core/README.md`, `apps/cli/README.md`, or a new
-     package's) for package-specific behaviour.
+   - `docs/action.md` for the action's commands, inputs, output and run-level errors;
+     `README.md` only lists them at a glance and links there;
+   - the package's own `README.md` (`packages/core/README.md`, `apps/cli/README.md`, a
+     command's `packages/services/<command>/README.md`, or a new package's) for
+     package-specific behaviour;
+   - `DEVELOPER.md` for local-dev workflow, the quality gates and CI.
+
+   Write the new text to the page rules in `DEVELOPER.md`, "Writing documentation", and add each new
+   fact's `path::symbol` to the page's code map, the `## Code map` of the `CONTEXT.md` beside its code.
 
 This is a **move**, not a copy. After the PR, the information exists in exactly one place —
 the live docs — and `SPEC.md` is smaller. `SPEC.md` trends toward its process-only skeleton