docs: re-collect wiki sites (doc-forge, openapi-first)

Reflect rebuilt consumer wikis in the hub: doc-forge gains the MkDocs cross-kind link notes; openapi-first gains the codegen --template-style content. Purely cosmetic (toolchain escaping) and sitemap mtime deltas were left out.

doc-forge/wiki/05_development/05_mkdocs_configs/index.html

@@ -675,6 +675,15 @@
     </span>
   </a>
   
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#cross-kind-links" class="md-nav__link">
+    <span class="md-ellipsis">
+      🔗 Cross-kind links
+    </span>
+  </a>
+  
 </li>
       
         <li class="md-nav__item">
@@ -782,6 +791,17 @@ built-in templates entirely.</p>
 </ul>
 <p>Commit <code>docs/mkdocs.{kind}.yml</code> so served docs are reproducible from source.</p>
 <hr />
+<h2 id="cross-kind-links">🔗 Cross-kind links</h2>
+<p>Kinds are separate MkDocs sites served side by side under <code>/&lt;repo&gt;/&lt;kind&gt;/</code>,
+so a wiki page may link to the library reference with a source-relative path
+such as <code>../lib/13_library_registry/</code>. MkDocs only rewrites links that point
+inside <code>docs_dir</code>; anything reaching a sibling kind is emitted verbatim and,
+under <code>use_directory_urls</code>, resolves into <code>&lt;kind&gt;/&lt;kind&gt;/</code> and breaks.</p>
+<p>The <code>docforge-linkfix</code> plugin (part of doc-forge, enabled in the wiki
+template) fixes this at render time: it rewrites <code>../lib/</code>, <code>../api/</code>, and
+<code>../wiki/</code> links to climb to the repository root, so they resolve correctly
+however deeply the page is nested.</p>
+<hr />
 <h2 id="related">Related</h2>
 <ul>
 <li><a href="../04_mcp_guide/">04 – MCP Guide</a></li>