Cloudflare Worker & edge

npm create cloudflare@latest my-mumm-gateway -- --type=hello-world --ts
cd my-mumm-gateway
npm install @rebilder/gateway

"routes": [
  { "pattern": "example.com/*", "zone_name": "example.com" },
  { "pattern": "www.example.com/*", "zone_name": "example.com" }
]

npx wrangler login
npx wrangler deploy

Set up a Cloudflare Worker that puts @rebilder/gateway in front of my site.

WHAT IT DOES
The Worker sits on a route in front of the origin. When an AI agent requests a
URL with `Accept: text/markdown` AND that URL is one I have described, it
answers with clean markdown rendered from typed data. Everything else is
forwarded to the origin unchanged: humans, Googlebot, URLs I have not described.

STEPS
1. Scaffold a TypeScript Worker and add the dependency:
     npm create cloudflare@latest my-mumm-gateway -- --type=hello-world --ts
     cd my-mumm-gateway && npm install @rebilder/gateway
2. Read node_modules/@rebilder/gateway/README.md before writing anything. Do
   not work from memory of this prompt.
3. Create `src/content.ts`: a `Map<string, DocumentSource>` keyed by pathname,
   and a `Map<string, CollectionSource>` for index pages. Read real values
   from authoritative business sources, following the rules below.
4. Create `src/gateway-config.ts` exporting a `GatewayConfig` whose `document`
   and `collection` resolvers are `Map.get` on the normalised pathname, plus a
   pure synchronous `match` router returning 'document', 'collection', or null.
5. Make `src/index.ts`:
     import { createGatewayFetchHandler } from '@rebilder/gateway/edge'
     export default { fetch: createGatewayFetchHandler(gatewayConfig) }
6. In wrangler.jsonc, set `routes` to my zone. Use the configured hostname.
   Ask only if the deployment target is missing or ambiguous.

IMPLEMENTATION REQUIREMENTS
- Never invent a substantive value. Read prices, opening hours, turnaround
  times, what a service includes and whether booking is required from
  authoritative business sources. Ask only for unavailable facts the task
  needs. Do not write a plausible-looking placeholder into content.ts; it will
  ship, and an agent will quote it.
- Money is in MINOR UNITS. { amount: 180, currency: 'GBP' } is £1.80, not £180.
  Use the currency’s minor-unit exponent when converting major units. Keep
  decimal arithmetic exact and reject unsupported precision.
- Serve the described pages from bundled or cached sources. If remote
  resolution is needed, bound its timeout, verify freshness and keep the origin
  fallback.
- A resolver returns null when the URL is not that kind of page. null means
  "forward to the origin", which is always a safe answer.
- Forward the origin's response as-is. Do not rewrite its status, do not turn a
  502 into a friendly page, do not follow its redirects inside the Worker.
- Do not change the origin. Keep a rollback path that removes the Worker route
  and restores direct origin serving.

WHEN YOU ARE DONE
Tell me which pathnames now serve markdown and which pages I still need to
describe. Then verify against the deployed site, one real URL of each kind:

  curl -sI https://MY-DOMAIN/PATH -H 'Accept: text/markdown'   # expect text/markdown
  curl -sI https://MY-DOMAIN/PATH                              # expect my normal HTML
  npx rebilder check https://MY-DOMAIN/PATH                        # grades the page

If you cannot answer "which URLs now serve markdown", the setup is not done.

// worker.ts: deploy on a route in front of your site, e.g. example.com/*
import { createGatewayFetchHandler } from '@rebilder/gateway/edge'
import { gatewayConfig } from './gateway-config'

export default { fetch: createGatewayFetchHandler(gatewayConfig) }