docs: add react-auth, react-openapi, vet sites; update standards registry and MCP setup
This commit is contained in:
@@ -827,6 +827,20 @@ can read a library's full API by connecting to its MCP and reading
|
||||
<td><code>:8010</code></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>React Auth</td>
|
||||
<td><code>react-auth</code></td>
|
||||
<td>JWT-backed React auth UI: provider, login page, profile screens, bearer axios client</td>
|
||||
<td>hand-rolled auth contexts and token handling in React apps</td>
|
||||
<td><code>:8011</code></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>React OpenAPI</td>
|
||||
<td><code>react-openapi</code></td>
|
||||
<td>Spec-driven React admin UI (CRUD, tables, forms, SSE) derived from an OpenAPI document</td>
|
||||
<td>per-resource hand-written admin screens</td>
|
||||
<td><code>:8012</code></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Auth Server</td>
|
||||
<td><em>(service)</em></td>
|
||||
<td>Central identity service (register/login/me/logout/introspect)</td>
|
||||
@@ -880,6 +894,14 @@ can read a library's full API by connecting to its MCP and reading
|
||||
<td>generate React/TypeScript documentation</td>
|
||||
<td>Doc Weaver</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>authenticate a React front-end</td>
|
||||
<td>React Auth (+ Auth Server)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>build a React admin UI from an OpenAPI spec</td>
|
||||
<td>React OpenAPI</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="discovery">Discovery</h2>
|
||||
@@ -903,6 +925,10 @@ any infrastructure.</p>
|
||||
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><strong>React Auth</strong> and <strong>React OpenAPI</strong> are front-end libraries (TypeScript,
|
||||
React 18 + MUI + React Router peers), not Python services — they consume the
|
||||
<strong>Auth Server</strong> and an OpenAPI document rather than serving one. Each ships
|
||||
a wiki, a TypeDoc site and an MCP bundle like every other library above.</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>
|
||||
|
||||
File diff suppressed because one or more lines are too long
Reference in New Issue
Block a user