docs: update SKILL.md now that #261/#262 (Vercel operator/action gaps) are fixed - #282
Merged
Merged
Conversation
…) are fixed ne/not_contains/not_in and allow/block were documented as known-bugs to avoid on Vercel; both are now correctly handled (neg-flag composition and bypass/deny remapping respectively, per #279/#280). gt/ge/lt/le remain a genuine platform gap -- Vercel has no numeric-comparison operator at all -- but that's now a documented, safe drop-with-warning rather than a silent bug to avoid.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
SKILL.md(loaded by any AI agent using the doorman skill) told users to avoidne/not_contains/not_in/gt/ge/lt/leandallow/blockin a Vercel-targeted config, citing #261/#262 as known bugs. Both were fixed and merged yesterday (#279, #280) — leaving the warnings in place would actively steer people away from functionality that now works correctly.Updated both bold-warning lines to reflect current, accurate behavior:
ne/not_contains/not_inare now fully supported on Vercel (via its positive-operator +neg-flag model).gt/ge/lt/leremain unsupported — that part hasn't changed — but reframed as a genuine platform limitation (Vercel has no numeric-comparison operator at all, safely dropped-with-warning) rather than a bug to avoid.allow/blockare now automatically mapped tobypass/deny— no workaround needed.Also audited the rest of
skills/doorman/references/*.mdand the GitHub Wiki'sConfiguration.mdfor the same class of staleness from today's other fixes (#263/#269/#270/#271):cloudflare.md's keyed-query-condition docs and the rate-limit field table inrules.mdwere already accurate (updated by the PRs that shipped those fixes) — no changes needed there.Configuration.md(wiki) had the identical #261/#262 staleness plus a stalekeynote for #263's query fix; pushed that correction directly to the wiki (no PR flow there) in a separate commit.Docs-only change, no code/test/schema touched.