Domain Dns Ops

**Judgment:** High-value, specialized skill tightly coupled to Peter’s local repo and Cloudflare/DNS tooling. Excellent for its intended environment, but not portable or general-purpose. **Strengths:** - Clear golden path for domain → Cloudflare → redirect, with strong reliance on ~/Projects/manager as the source of truth. - Supports multiple redirect strategies (Page Rules, Rulesets/Bulk Redirects, Worker) and includes verification and sanity checks. - Git workflow and guardrails (don’t touch lore domains, verify after each step) help reduce operational mistakes. **Risks / Limitations:** - Hard dependency on local files, scripts, and profiles in ~/Projects/manager; largely unusable outside Peter’s exact setup. - Operations have high blast radius (nameservers, redirects, workers) if invoked on the wrong domain or without reading DOMAINS.md/DNS.md carefully. - Requires familiarity with Cloudflare APIs, cli4, and registrar behavior; non-owners of this infra will struggle. **Recommended Scenarios:** - Peter (or trusted collaborators) managing his own domains and redirects, strictly following the documented checklists. - Routine onboarding of new vanity domains to Cloudflare and setting consistent HTTPS redirects. - Maintenance of redirect-worker mappings and AI bot blocking settings where the local manager repo and tokens are known to be correctly configured.