doc-weaver init and cross wiki-lib links fixes

standards/src/lib/13_library_registry.md

@@ -24,6 +24,7 @@ can read a library's full API by connecting to its MCP and reading
 | Mail Intake | `mail_intake` | Provider-agnostic read-only email ingestion | Gmail OAuth + MIME parsing | `:8002` |
 | Py JWT | `jwtlib` | JWT auth primitives (register/login/introspect) | password hashing + token code | `:8005` |
 | Doc Forge | `docforge` | Docstring compiler → MkDocs + MCP docs | custom doc generators | `:8001` |
+| Doc Weaver | `doc-weaver` | JSDoc compiler → TypeDoc + MCP docs (React/TS) | custom TypeScript doc generators | `:8010` |
 | Auth Server | *(service)* | Central identity service (register/login/me/logout/introspect) | building auth endpoints yourself | spec: `docs://spec` |
 
 ## How to choose
@@ -38,6 +39,7 @@ can read a library's full API by connecting to its MCP and reading
 | ingest email | Mail Intake |
 | authenticate users / verify tokens | Py JWT (+ Auth Server) |
 | generate documentation | Doc Forge |
+| generate React/TypeScript documentation | Doc Weaver |
 
 ## Discovery
 
@@ -58,5 +60,9 @@ any infrastructure.
   via `docs://spec` and wire it by declaring a `bearerAuth` security scheme in
   the app's own spec (see **Auth Integration**); `py-jwt` covers the
   low-level token path.
+- **Doc Weaver** is the TypeScript counterpart to **Doc Forge**: it reads
+  JSDoc comments and emits a TypeDoc site plus the same doc-forge-shaped MCP
+  bundle for React packages. Its convention is **RDFC** (the React Doc-forge
+  Convention), the JSDoc parallel to GSDFC.
 - Library MCP servers expose **documentation resources** (not executable tools):
   they tell an agent the available API surface so it does not invent code.