feat(standards): integrate auth-server via pinned spec (docs://spec) + auth recipe and template slice

- serve the pinned auth-server OpenAPI contract as the standards MCP resource docs://spec (no auth-server MCP bundle)
- add Auth Integration recipe (14) and wire it into the registry, prompts, index, and nav
- un-defer Auth Server in the library registry (spec/recipe pointers)
- ship the opt-in template auth slice: interfaces/auth/ (placeholder + mergeable bearerAuth security.yaml) and AUTH_SERVER/JWT_SERVER env
- rebuild bundle (13 modules, 44 components); template stays authless by default

standards/lib/index.html

@@ -474,6 +474,28 @@
   
   
   
+    <li class="md-nav__item">
+      <a href="14_auth_integration/" class="md-nav__link">
+        
+  
+  
+  <span class="md-ellipsis">
+    Auth Integration
+    
+  </span>
+  
+
+      </a>
+    </li>
+  
+
+    
+      
+      
+  
+  
+  
+  
     <li class="md-nav__item">
       <a href="13_library_registry/" class="md-nav__link">
         
@@ -540,6 +562,8 @@ patterns, and the internal library catalog that agents consult while coding.</p>
 <li><strong>Human-in-the-Loop</strong> — guardrails and approvals inside automations.</li>
 <li><strong>Infra Adapters</strong> — how infrastructure connects without leaking into domain.</li>
 <li><strong>Genericity Matrix</strong> — what is library-backed, template-provided, or authored.</li>
+<li><strong>Auth Integration</strong> — consuming the shared auth-server service (spec-driven,
+  no auth code).</li>
 <li><strong>Library Registry</strong> — the catalog of internal libraries behind all of it.</li>
 </ul>
 <p>Read the <strong>Wiki</strong> for the philosophy and rationale; these pages are the