doc-weaver init and cross wiki-lib links fixes

standards/lib/13_library_registry/index.html

@@ -820,6 +820,13 @@ can read a library's full API by connecting to its MCP and reading
 <td><code>:8001</code></td>
 </tr>
 <tr>
+<td>Doc Weaver</td>
+<td><code>doc-weaver</code></td>
+<td>JSDoc compiler → TypeDoc + MCP docs (React/TS)</td>
+<td>custom TypeScript doc generators</td>
+<td><code>:8010</code></td>
+</tr>
+<tr>
 <td>Auth Server</td>
 <td><em>(service)</em></td>
 <td>Central identity service (register/login/me/logout/introspect)</td>
@@ -869,6 +876,10 @@ can read a library's full API by connecting to its MCP and reading
 <td>generate documentation</td>
 <td>Doc Forge</td>
 </tr>
+<tr>
+<td>generate React/TypeScript documentation</td>
+<td>Doc Weaver</td>
+</tr>
 </tbody>
 </table>
 <h2 id="discovery">Discovery</h2>
@@ -888,6 +899,10 @@ any infrastructure.</p>
   via <code>docs://spec</code> and wire it by declaring a <code>bearerAuth</code> security scheme in
   the app's own spec (see <strong>Auth Integration</strong>); <code>py-jwt</code> covers the
   low-level token path.</li>
+<li><strong>Doc Weaver</strong> is the TypeScript counterpart to <strong>Doc Forge</strong>: it reads
+  JSDoc comments and emits a TypeDoc site plus the same doc-forge-shaped MCP
+  bundle for React packages. Its convention is <strong>RDFC</strong> (the React Doc-forge
+  Convention), the JSDoc parallel to GSDFC.</li>
 <li>Library MCP servers expose <strong>documentation resources</strong> (not executable tools):
   they tell an agent the available API surface so it does not invent code.</li>
 </ul>