Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

docs(skills): document version-range override form

Address Copilot review on #2239. Rule 6 previously forbade version-range-keyed overrides (pkg@>=x <y as a key), but pnpm-workspace.yaml already uses that form for the brace-expansion CVE patch series — internally inconsistent.

Rewrites Rule 6 to enumerate the three valid override-key forms (top-level, parent-scoped, version-range-keyed) with guidance on when each is preferred. Uses the live brace-expansion overrides as the example for the version-range form so the doc and the workspace config stay in lock-step.