docs: add Fastly Next-Gen WAF coverage
New Fastly-Setup and Fastly-Migration pages mirroring the existing
Cloudflare ones, registered in the sidebar. Updated Home,
Getting-Started, Configuration, Commands-Overview, and
CI-CD-Integration to mention Fastly alongside Vercel/Cloudflare
wherever they previously only covered two providers — condition
type/operator/action compatibility tables, env vars, CLI examples,
and the multi-provider CI pipeline example.
Companion to gfargo/doorman#204/#205 (Fastly provider adapter).
docs: fix remaining fabricated CLI flags and stale claims found in follow-up review
Found by a fresh review pass after the earlier wiki cleanup (commit
ac2db93) missed a few instances of the same bug class:
- CI-CD-Integration.md: `doorman validate --strict` doesn't exist
(validate only has --config/-c and --verbose/-v)
- Commands-Overview.md: `doorman init --provider cloudflare
--interactive` doesn't exist (init has no --provider flag at all,
contradicting what Cloudflare-Setup.md already correctly says)
- Commands-Overview.md: "Global Options" claimed --provider/--token/
--verbose are available on "most commands" — --verbose only exists
on validate, --provider/--token only exist on 8 of 14 commands
- Configuration.md: actions table wrongly marked Vercel as supporting
`allow` (Vercel's action enum has no `allow`; the equivalent is
`bypass`)
- Getting-Started.md: action list used `rateLimit`/`rewrite`, neither
of which are real Vercel action values (rate_limit is snake_case;
rewrite is Cloudflare-only)
- Examples.md: IP blocking example omitted `hostname`, a required
field on every ips[] entry, and the linked full example
(ip-block.json) actually demonstrates a different technique
(rules[] + ip_address conditions) than the ips[] array shown inline
- now noted explicitly instead of silently mismatched
- Getting-Started.md: stale "Doorman 2.0" version callout
- Templates.md / Commands-Overview.md: `doorman template` (no name)
launches an interactive select prompt, it doesn't list templates
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: add `remove` command to Commands Overview
docs: add `add` command to Commands Overview and Getting Started
docs: add initial wiki pages for documentation site