List all fabrics on docs index; rename Network fabric to Proxy fabric

Author: arkkln

app/(home)/tools/invisibles/page.tsx

@@ -145,15 +145,15 @@ export default function InvisiblesPage() {
             lede={
               <>
                 <code>invisibles</code> is the foundation under{' '}
-                <code>nu.proxy</code>, the network fabric. Bind a fabric in
+                <code>nu.proxy</code>, the proxy fabric. Bind a fabric in
                 one process, use it from another; same Refs, over TCP or
                 Unix socket.
               </>
             }
           />
           <Section>
             <LinkGrid>
-              <LinkCard href="/fabrics/proxy" name="nu.proxy" hue="plum" tagline="Network fabric.">
+              <LinkCard href="/fabrics/proxy" name="nu.proxy" hue="plum" tagline="Proxy fabric.">
                 The fabric that puts other fabrics on the network. Built on
                 invisibles.
               </LinkCard>

content/docs/index.mdx

@@ -116,7 +116,12 @@ Each fabric binds Refs to a real backend and unlocks a new capability.
 | [`nu.mem`](/docs/reference/fabrics/mem) | In-memory state fabric. Perfect for cache, hot state, and in-process coordination. |
 | [`nu.kv`](/docs/reference/fabrics/kv) | Persistent state fabric. Refs over a KV backend (RocksDB, LMDB); transactions, snapshots, and change notifications, built in. |
 | [`nu.ui`](/docs/reference/fabrics/ui) | Web UI fabric. Same fabric shape as the others, but the Refs are widgets (text, buttons, tables) rendered in the browser and live-updated as your state changes. |
-| [`nu.proxy`](/docs/reference/fabrics/proxy) | Network fabric. Puts other fabrics on the network. Bind a fabric in one process, use it from another; same Refs, same interactions, over TCP or Unix socket. |
+| [`nu.proxy`](/docs/reference/fabrics/proxy) | Proxy fabric. Puts other fabrics on the network. Bind a fabric in one process, use it from another; same Refs, same interactions, over TCP or Unix socket. |
+| [`nu.http`](/docs/reference/fabrics/http) | HTTP fabric: expose Nu Refs as endpoints, or build on top of any HTTP service. |
+| [`nu.service`](/docs/reference/fabrics/service) | In-process service fabric: any Python object as a tree of Refs. |
+| [`nu.llm`](/docs/reference/fabrics/llm) | OpenAI-compatible chat fabric: one wire, N providers. |
+| [`nu.cc`](/docs/reference/fabrics/cc) | Claude Code as a Ref: prompts from your Nu tree, session brackets, text and metadata back. |
+| [`nu.mp`](/docs/reference/fabrics/mp) | Local multiprocessing fabric: teleport subtrees onto spawned worker processes. |
 | [`nu.cluster`](/docs/reference/fabrics/cluster) | Cluster compute fabric. Teleport a Nu tree to any worker in your cluster; it runs there and returns the result. Ray under the hood. |
 
 ## Go deeper

content/docs/reference/fabrics/index.md

@@ -11,7 +11,7 @@ A **Fabric** is the substrate a Ref lives on. One page per Fabric: the Refs it s
 | [cluster](cluster.md) | `nu.cluster` | Distributed fabric backed by Ray actors and object refs. |
 | [llm](llm.md) | `nu.llm` | OpenAI-compatible chat fabric: one wire, N providers. |
 | [mem](mem.md) | `nu.mem` | In-process fabric: plain nested Python dicts as the data bag. Zero setup. |
-| [proxy](proxy.md) | `nu.proxy` | Network fabric: transparent remote objects, local calls, remote execution. |
+| [proxy](proxy.md) | `nu.proxy` | Proxy fabric: transparent remote objects, local calls, remote execution. |
 | [http](http.md) | `nu.http` | HTTP fabric: expose Nu Refs as endpoints, or build on top of any HTTP service. |
 | [service](service.md) | `nu.service` | In-process service fabric: any Python object as a tree of Refs. |
 | [cc](cc.md) | `nu.cc` | Claude Code as a Ref: prompts from your Nu tree, session brackets, text and metadata back. |

content/docs/reference/fabrics/proxy.md

@@ -2,7 +2,7 @@
 title: nu.proxy
 ---
 
-Network fabric: transparent remote objects, local calls, remote execution.
+Proxy fabric: transparent remote objects, local calls, remote execution.
 Pure transport over TCP or Unix socket. No new refs, no new interactions.
 Method calls on a client proxy travel the wire and land on the server-side
 bound fabric, dispatched by the same `FabricRef` machinery that works locally.

lib/fabrics.ts

@@ -121,7 +121,7 @@ const SPECS: FabricSpec[] = [
     name: 'nu.proxy',
     slug: 'proxy',
     hue: 'plum',
-    tagline: 'Network fabric.',
+    tagline: 'Proxy fabric.',
     description:
       'Puts other fabrics on the network. Bind a fabric in one process, use it from another; same Refs, over TCP or Unix socket.',
     navDesc: 'Fabrics over the network.',