feat: renumber lib reference into 4-pillar anatomy

Renumber the 15 reference docs into pillar groups (recipe -> anatomy):
- 01 Build Recipe (entry), 02 Composition Root
- domains: 10 Layering Rules
- contract: 20 Spec-First Routing, 21 CRUD Template, 22 Auth Integration
- interfaces/infra: 30 Infra Adapters
- UI: 40 UI: Auto-Rendered Admin & Custom Pages (new; @aetoskia packages,
  client template, x- catalog via react-openapi MCP module)
- pipelines: 50 Pipeline Scaffold, 51 Worker & Progress, 52 Human-in-the-Loop
- delivery/meta: 90 Drone Pipelines, 91 Versioning & Changelog,
  92 Genericity Matrix, 93 Library Registry, 94 Repository Inventory

MCP module names are unchanged (NN_ prefix stripped); all cross-references
(wiki, templates, hooks, registry) updated; lib index rewritten pillar-first;
build recipe bootstraps the client template. Bundle + HTML sites regenerated.

standards/src/wiki/04_development/02_releasing.md

@@ -1,11 +1,11 @@
 # Releasing & Versioning
 
 How to cut a release of any Aetos repository. The rule lives in the reference
-page [Versioning & Changelog](../lib/11_versioning_and_changelog/); this is the
+page [Versioning & Changelog](../lib/91_versioning_and_changelog/); this is the
 runbook you follow.
 
 Every repository is one of two Drone shapes — a **PyPI package** or a **Docker
-deployment** ([Drone Pipelines](../lib/10_drone_pipelines/)). Both release the
+deployment** ([Drone Pipelines](../lib/90_drone_pipelines/)). Both release the
 same way: the version bump and changelog promotion go **in the merge request**,
 and the tag is created on the merged commit.
 
@@ -122,4 +122,4 @@ outage):
 
 ## Related
 
-- [Testing & Quality Gates](01_testing.md) · [Versioning & Changelog](../lib/11_versioning_and_changelog/) · [Drone Pipelines](../lib/10_drone_pipelines/)
+- [Testing & Quality Gates](01_testing.md) · [Versioning & Changelog](../lib/91_versioning_and_changelog/) · [Drone Pipelines](../lib/90_drone_pipelines/)