Fix legacy rule shape shown as universal; document managed rule groups
Configuration.md's Rules section showed the legacy (Vercel-only)
conditionGroup/active/mitigate.action shape as if it applied to every
provider. A config with provider/providers set (required for
Cloudflare/Fastly) needs a structurally different shape
(conditions/enabled/action:{type}) -- verified empirically that the
old example fails real schema validation when provider is set.
Rewrote the Rules section with both shapes clearly labeled, correct
per-provider field/operator/action support tables (verified against
each provider's translator source, not guessed), and flagged real
Vercel translator bugs found along the way (doorman#261, #262) rather
than silently documenting broken combinations as if they work.
Also:
- Documented the new managedRules config surface (Cloudflare-only)
- Added a format-shape note to Examples.md and Getting-Started.md,
whose rule examples are genuinely legacy-format (matching the real
examples/ files) but weren't labeled as such
- Added a Managed Rule Groups section to Cloudflare-Setup.md
docs: add Vercel Setup guide, cross-link from Cloudflare/Fastly
Vercel had no dedicated setup guide even though it's the default
provider — general instructions were folded into Getting-Started.md
while Cloudflare and Fastly each got their own thorough guide
(credentials, day-to-day commands, provider quirks, troubleshooting,
security). Adds parity, verified against real CLI source (init.ts,
VercelProvider.ts, providerHelper.ts, promptForCredentials.ts, setup.ts)
rather than copied from the other guides' assumptions.
Notably documents that VERCEL_TEAM_ID is required in practice today,
despite setup.ts/README describing it as optional for personal
accounts — the runtime throws if it's missing.
docs: fix wiki pages documenting nonexistent commands/flags (#89, #90, #99)
- Cloudflare-Migration.md documented a `doorman migrate` command that
doesn't exist (unbuilt "Phase 6" roadmap item per RELEASE-2.0.md).
Added a clear "not yet available" banner and a new manual-migration
workflow using commands that exist today (backup, download, hand-edit,
validate, sync), and marked the automated-workflow content as planned.
- Home.md and Cloudflare-Setup.md called Cloudflare support "stable"/
"production-ready", contradicting CLAUDE.md/AGENTS.md's "(beta)"
label. Updated both to say beta.
- Fixed several documented-but-nonexistent flags/subcommands:
`template add <name> --provider cloudflare` (no `add` subcommand or
`--provider` flag on template), `init --provider cloudflare`
(init has no --provider flag or Cloudflare support at all),
`validate --strict`/`--provider`, `diff --source/--target`
(diff doesn't do cross-provider comparison), `list --verbose`
(use --debug), `backup --name` (backups use an auto-generated
timestamped filename, controlled via --output).
docs: sync wiki for the vercel-doorman -> @gfargo/doorman rename
Install/npx examples now reference @gfargo/doorman, already-installed
binary examples (CI YAML, package.json scripts) use the doorman bin
name, and GitHub/npm links point at gfargo/doorman. Also drops the
"when Cloudflare support lands" line in Getting-Started since
Cloudflare WAF support has already shipped.
docs: update config filename references to .doorman.json
docs: add Cloudflare setup and migration guides, update sidebar