chore: declare api.ooxml.dev custom domain and refresh README intro

wrangler.toml now claims api.ooxml.dev as a custom_domain so the next
deploy moves ownership from ecma-spec-mcp to ooxml-mcp via the
Cloudflare API, bypassing the dashboard's "could not be added" error.

README intro now mentions the MCP server alongside live previews and
implementation notes, since the prose-search + schema-lookup tools are
a first-class part of the offering after PR #4.

Author: caiopizzol

README.md

@@ -8,7 +8,7 @@ The OOXML spec, explained by people who actually implemented it.
 
 ## What is this?
 
-An interactive reference for ECMA-376 (Office Open XML) built by the [SuperDoc — DOCX editing and tooling](https://superdoc.dev) team. Every page combines XML structure, live rendered previews, and implementation notes that tell you what the spec doesn't.
+An interactive reference for ECMA-376 (Office Open XML), built by the team behind [SuperDoc](https://superdoc.dev). Every page combines XML structure, live rendered previews, and implementation notes the spec leaves out. The MCP server exposes the same knowledge to AI assistants: prose search across the spec PDFs and deterministic schema lookup over the parsed XSDs.
 
 - **Live previews** - Edit XML and see it render in real-time. Every example is a working document.
 - **Implementation notes** - Where Word diverges from the spec, what will break your code, and what to do about it.

apps/mcp-server/wrangler.toml

@@ -3,6 +3,12 @@ main = "src/index.ts"
 compatibility_date = "2026-01-28"
 compatibility_flags = ["nodejs_compat"]
 
+# Custom domain. Wrangler claims api.ooxml.dev for this worker on deploy and
+# manages the DNS record on Cloudflare's side; we don't add it manually.
+routes = [
+	{ pattern = "api.ooxml.dev", custom_domain = true }
+]
+
 # Secrets (set via wrangler secret):
 # wrangler secret put DATABASE_URL
 # wrangler secret put VOYAGE_API_KEY