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: 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: 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 initial wiki pages for documentation site