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/wiki/01_overview/index.html

@@ -772,7 +772,7 @@ port/adapter binding, performed by the composition root at startup.</p>
 <li><strong>Spec-first.</strong> The HTTP contract is declared in <code>openapi.yaml</code>; route
    handlers are looked up by <code>operationId</code>. There are no decorator routers.</li>
 <li><strong>Reuse the libraries.</strong> Orchestration, DI, Mongo repositories, ingestion,
-   auth, and docs come from internal libraries — see the <a href="../../lib/13_library_registry/">Library
+   auth, and docs come from internal libraries — see the <a href="../../lib/93_library_registry/">Library
    Registry</a>.</li>
 <li><strong>Explicit state machines.</strong> Long-running work moves through explicit,
    durable statuses and can pause for human input.</li>

standards/wiki/03_start_an_app/index.html

@@ -693,7 +693,7 @@ machine-facing checklist lives in the reference page
    the families and their input formats (or "none").</li>
 <li><strong>Auth needed now?</strong> Default <strong>no</strong>. Auth is deferred (<code>py-jwt</code> primitives
    only), and an authless app is just a spec with no <code>security</code> keys — see
-   <a href="../../lib/04_spec_first_routing/#authless-apps">Spec-First Routing → Authless apps</a>.</li>
+   <a href="../../lib/20_spec_first_routing/#authless-apps">Spec-First Routing → Authless apps</a>.</li>
 <li><strong>Integrations.</strong> Mongo, ingestion formats, email, LLM provider.</li>
 </ol>
 <p>If you can state axes 1 and 2, the rest is mechanical.</p>
@@ -721,8 +721,8 @@ machine-facing checklist lives in the reference page
 <h2 id="reference">📚 Reference</h2>
 <ul>
 <li><a href="../../lib/01_build_recipe/">Build Recipe</a> — the deterministic checklist</li>
-<li><a href="../../lib/12_genericity_matrix/">Genericity Matrix</a> — Tier A / B / C</li>
-<li><a href="../../lib/13_library_registry/">Library Registry</a> — the Tier A catalog</li>
+<li><a href="../../lib/92_genericity_matrix/">Genericity Matrix</a> — Tier A / B / C</li>
+<li><a href="../../lib/93_library_registry/">Library Registry</a> — the Tier A catalog</li>
 <li><a href="../02_components/">App Components</a> — the component model</li>
 </ul>
 <hr />

standards/wiki/04_development/02_releasing/index.html

@@ -723,10 +723,10 @@
 
 <h1 id="releasing-versioning">Releasing &amp; Versioning</h1>
 <p>How to cut a release of any Aetos repository. The rule lives in the reference
-page <a href="../../../lib/11_versioning_and_changelog/">Versioning &amp; Changelog</a>; this is the
+page <a href="../../../lib/91_versioning_and_changelog/">Versioning &amp; Changelog</a>; this is the
 runbook you follow.</p>
 <p>Every repository is one of two Drone shapes — a <strong>PyPI package</strong> or a <strong>Docker
-deployment</strong> (<a href="../../../lib/10_drone_pipelines/">Drone Pipelines</a>). Both release the
+deployment</strong> (<a href="../../../lib/90_drone_pipelines/">Drone Pipelines</a>). Both release the
 same way: the version bump and changelog promotion go <strong>in the merge request</strong>,
 and the tag is created on the merged commit.</p>
 <hr />
@@ -851,7 +851,7 @@ outage):</p>
 <hr />
 <h2 id="related">Related</h2>
 <ul>
-<li><a href="../01_testing/">Testing &amp; Quality Gates</a> · <a href="../../../lib/11_versioning_and_changelog/">Versioning &amp; Changelog</a> · <a href="../../../lib/10_drone_pipelines/">Drone Pipelines</a></li>
+<li><a href="../01_testing/">Testing &amp; Quality Gates</a> · <a href="../../../lib/91_versioning_and_changelog/">Versioning &amp; Changelog</a> · <a href="../../../lib/90_drone_pipelines/">Drone Pipelines</a></li>
 </ul>
 
 

standards/wiki/05_mcp_setup/index.html

@@ -738,7 +738,7 @@ portal runs each one as a FastMCP <strong>streamable-http</strong> app bound to
 <p>Connect your agent to the <strong><code>standards</code></strong> server first: it answers
 <code>find_library</code>, <code>list_repos</code>, and the <code>start_app</code> prompt, so the agent reaches
 for an internal library instead of reimplementing one (see the
-<a href="../../lib/13_library_registry/">Library Registry</a>).</p>
+<a href="../../lib/93_library_registry/">Library Registry</a>).</p>
 <hr />
 <h2 id="run-the-servers-locally">▶️ Run the servers locally</h2>
 <p>From the <code>docs</code> checkout:</p>
@@ -1328,7 +1328,7 @@ Client Configuration → Copy HTTP Stream Config</strong>.</p>
 <hr />
 <h2 id="reference">📚 Reference</h2>
 <ul>
-<li><a href="../../lib/13_library_registry/">Library Registry</a> — the catalog each server
+<li><a href="../../lib/93_library_registry/">Library Registry</a> — the catalog each server
   mirrors, and where <code>find_library</code> resolves</li>
 <li><a href="../03_start_an_app/">Start an App</a> — connect <code>standards</code>, then invoke
   <code>start_app</code></li>
@@ -1337,7 +1337,7 @@ Client Configuration → Copy HTTP Stream Config</strong>.</p>
 <hr />
 <h2 id="related">Related</h2>
 <ul>
-<li><a href="../03_start_an_app/">Start an App</a> · <a href="../04_development/01_testing/">Testing &amp; Quality</a> · <a href="../../lib/13_library_registry/">Library Registry</a></li>
+<li><a href="../03_start_an_app/">Start an App</a> · <a href="../04_development/01_testing/">Testing &amp; Quality</a> · <a href="../../lib/93_library_registry/">Library Registry</a></li>
 </ul>
 
 

standards/wiki/index.html

@@ -718,15 +718,19 @@ Query <code>find_library</code> before writing any infrastructure.</p>
 </tbody>
 </table>
 <p><strong>Reference</strong> (separate site, mirrors the MCP bundle): the enforceable
-rules — <a href="../lib/01_build_recipe/">Build Recipe</a>, <a href="../lib/02_layering_rules/">Layering</a>, <a href="../lib/03_composition_root/">Composition
-Root</a>, <a href="../lib/04_spec_first_routing/">Spec-First
-Routing</a>, <a href="../lib/05_crud_template/">CRUD
-Template</a>, <a href="../lib/06_pipeline_scaffold/">Pipeline
-Scaffold</a>, <a href="../lib/07_worker_and_progress/">Worker &amp;
-Progress</a>, <a href="../lib/08_human_in_loop/">Human-in-the-Loop</a>,
-<a href="../lib/09_infra_adaptors/">Infra Adapters</a>, <a href="../lib/12_genericity_matrix/">Genericity
-Matrix</a>, <a href="../lib/13_library_registry/">Library
-Registry</a>.</p>
+anatomy — start at the <a href="../lib/01_build_recipe/">Build Recipe</a>, then the
+pillars: domains (<a href="../lib/10_layering_rules/">Layering</a>), the OpenAPI
+contract (<a href="../lib/02_composition_root/">Composition Root</a>,
+<a href="../lib/20_spec_first_routing/">Spec-First Routing</a>, <a href="../lib/21_crud_template/">CRUD
+Template</a>, <a href="../lib/22_auth_integration/">Auth
+Integration</a>), interfaces &amp; infra (<a href="../lib/30_infra_adaptors/">Infra
+Adapters</a>), UI (<a href="../lib/40_ui_admin/">Auto-Rendered
+Admin</a>), the optional pipelines layer (<a href="../lib/50_pipeline_scaffold/">Pipeline
+Scaffold</a>, <a href="../lib/51_worker_and_progress/">Worker &amp;
+Progress</a>, <a href="../lib/52_human_in_loop/">Human-in-the-Loop</a>),
+and delivery/meta (<a href="../lib/92_genericity_matrix/">Genericity
+Matrix</a>, <a href="../lib/93_library_registry/">Library
+Registry</a>).</p>
 <hr />
 <h2 id="related-resources">🔗 Related Resources</h2>
 <ul>