Re-pin the document, and place the names the API grew

The pinned document was a month old and predated the compute migration, so
every SDK generated from it described /v1/visor — which the deployment no
longer serves at all. That is how a hand-written console client and a
generated one drifted the same way at the same time.

publish refused until the taxonomy could place what the API now serves. Most
of it was one migration: agents, channels, flags, functions, integrations,
projects and tools each went singular, and visor became compute. Placed the
three that are genuinely new by reading what they serve — ci alongside deploy,
space alongside s3 since it serves drives and files, and market with web3
rather than commerce, because it serves chains, pools and tokens.

crm is grouped nowhere now only because it serves no route yet; the file can
only arrange what the router answers for. It comes back when it does.

capabilities.yaml

@@ -42,7 +42,7 @@ domains:
 
   - id: intelligence
     title: "Intelligence"
-    role: "models · agents · evaluation — the mind of the cloud"
+    role: "models · agent · evaluation — the mind of the cloud"
     # The bare-/v1 inference surface — /v1/chat/completions, /v1/models,
     # /v1/embeddings — is Hanzo AI's OpenAI- and Anthropic-compatible face,
     # where the PATH is the compatibility contract because every vendor SDK
@@ -51,7 +51,7 @@ domains:
     # expect. The hand-declared long tail that used to sit beside them is gone,
     # which is what apps/ai projecting its mounted registry was always going to
     # do to it.
-    tags: [ai, agents, ml, eval, benchmark, prompt, exec, sandbox, tools,
+    tags: [ai, agent, ml, eval, benchmark, prompt, exec, sandbox, tool,
            ask, code, engine, translate, lsp]
 
   - id: data
@@ -64,7 +64,7 @@ domains:
     # vocabulary naming the relations in use, and a rule that says which of two
     # disagreeing assertions is in force. It answers what is true as of an
     # instant, which is a store being read, not a product being used.
-    tags: [s3, base, kv, search, index, catalog, taxonomy, sync, crawl,
+    tags: [s3, space, base, kv, search, index, catalog, taxonomy, sync, crawl,
            websearch, provisioning, knowledge, graph]
 
   - id: streams
@@ -82,7 +82,7 @@ domains:
     # token rotation that keeps it live. What it does is carry data between this
     # cloud and another one, which is `destination` and `webhook`'s family.
     tags: [tasks, pubsub, mq, notify, tel, auto, flow, webhook, event,
-           channels, destination, integrations]
+           channel, destination, integration]
 
   - id: observability
     title: "Observability"
@@ -92,8 +92,7 @@ domains:
   - id: commerce
     title: "Commerce"
     role: "the economy — meter · price · bill · reward"
-    tags: [commerce, marketplace, billing, pricing, books, captable, crm,
-           referral, affiliate, author, licensing, x402, marketing,
+    tags: [commerce, marketplace, billing, pricing, books, captable, referral, affiliate, author, licensing, x402, marketing,
            campaign, ad, experiment, treasury, plan, allowance]
 
   - id: platform
@@ -104,8 +103,8 @@ domains:
     # fabric — the same domain as the rest of what runs work — and not
     # Intelligence's `exec` or `sandbox`, which run code on machines that are
     # OURS. Whose hardware it is decides which of the two a caller wants.
-    tags: [platform, deploy, projects, registry, gateway, ingress, dns,
-           domain, cloudflare, network, flags, visor, node]
+    tags: [platform, deploy, project, ci, registry, gateway, ingress, dns,
+           domain, cloudflare, network, flag, compute, node]
 
   - id: applications
     title: "Applications"
@@ -121,7 +120,7 @@ domains:
     # sends you.
     tags: [git, template, blueprint, bot, world, todo, framework, content,
            guide, help, meet, share, social, esign, dataroom, company,
-           legal, pref, settings, functions, sbom, link, seo, standing]
+           legal, pref, settings, function, sbom, link, seo, standing]
 
   - id: chain
     title: "Chain"
@@ -133,4 +132,4 @@ domains:
     # chain and kept: how far each indexer has caught up, and what the on-chain
     # oracles report. They are not Platform, which is the fabric this cloud RUNS
     # on, and a chain is something it TALKS TO.
-    tags: [web3, explorer]
+    tags: [web3, explorer, market]