mycocloudflare-worker-infrastructure-lifecyclelisted

# Cloudflare Worker Infrastructure Lifecycle > **Scope note:** The legacy Cloudflare team-sync stack (D1/Vectorize deployment, the cloud > MCP server that ran alongside it) is retired. Team functionality now lives in Team Host, > built into the main `myco` binary — see `docs/team-host.md`. The old worker/CLI > (`packages/myco-team`) is preserved in-repo, dormant, typecheck-only, and no longer > published; do not deploy it or extend it for new work. This skill instead covers the one > Cloudflare Worker package that is still a real, maintained artifact: **Collective** > (`packages/myco-collective`). Collective is itself dormant — not wired into the daemon, > pending redesign against the Team Host architecture — but it still builds and still > receives routine dependency updates, so its deploy/operate mechanics stay relevant to > whoever maintains it. ## Prerequisites - Cloudflare account with Workers (D1 + KV bindings) - Wrangler CLI installed and authenticated (`wrangler auth login`) - `packages/myco-collective/worker/wrangler.toml` for the worker config; `packages/myco-collective/src/cli.ts` for the operator CLI (`myco-collective`) ## Procedure A: Collective Worker Structure and Deployment The Collective worker is a standalone package with three parts: ``` packages/myco-collective/ ├── src/cli.ts # myco-collective operator CLI (install/upgrade/status/add-project/rotate-tokens/destroy) ├── worker/ │ ├── src/ # Worker source: auth.ts, fanout.ts, inde