Repository navigation
Description
Refs: #16982
Split from the changelog release issue(s) above under the owner's decision of 2026-11-21 (melodic-software/architecture#148): one issue per handoff row, rows that edit the same file grouped.
Route: lane work. Basis: corrections to match current upstream; criteria.md defers to what permission-patterns.sh matches, so one PR.
Problem
harness-config: permission-patterns misses path and version forms of package runners and three newer auto-mode drop classes
plugins/harness-config/lib/permission-patterns.sh encodes which allow rules auto mode drops. It matches only bare package-runner names, and lists five classes:
:38CCPERM_RUNNER_BODYand:74CCPERM_P1_RUNNER_ERE: no path prefix, no@version. SoBash(/usr/bin/npm run:*)andBash(pnpm@9 dlx *)go unmatched, while the interpreter ERE at:73does take a path prefix.:25-29: the comment lists five dropped classes.
What is true now:
- Changelog 2.1.327 (item 2.1.327-139): auto mode drops rules that run any package, including path and version forms of runner rules. The docs do not state this yet (docs-lag).
- https://code.claude.com/docs/en/permission-modes#how-auto-mode-evaluates-actions now also lists wrapper-plus-wildcard rules, rules that start with a wildcard, and some wildcarded paths. None of the patterns match these.
audit-permission-state/scripts/automode-entry-diff.sh (around line 255) and audit-permission-grants/scripts/permission-rule-check.sh P1 use these patterns, so both under-report.
harness-config: audit-permission-state's entry-diff criteria name the old auto-mode drop classes
plugins/harness-config/skills/audit-permission-state/reference/criteria.md:235-238 says auto mode drops rules "letting a package manager run project scripts", and lists five classes in all. What is true now:
- Changelog 2.1.327 (item 2.1.327-139): auto mode drops rules that run any package (for example
pnpm dlx), including path and version forms. The permission-modes page does not state this yet (docs-lag), so the change cites the changelog. - https://code.claude.com/docs/en/permission-modes#how-auto-mode-evaluates-actions also lists wrapper-plus-wildcard rules, rules that start with a wildcard, and some wildcarded paths.
The section's recheck trigger (:243, "a release note or that section adds, removes or narrows a dropped class") fires. Its As-of date is 2026-08-26.
docs: permission-rule-hygiene contract quotes a five-class auto-mode drop list; the docs now list eight
docs/contracts/permission-rule-hygiene/README.md:66-70 (Anti-pattern 1) quotes the permission-modes page's list of allow rules auto mode drops, re-fetched 2026-08-26, as five classes. What is true now:
- https://code.claude.com/docs/en/permission-modes#how-auto-mode-evaluates-actions lists eight. It adds wrapper-plus-wildcard rules, rules that start with a wildcard, and some wildcarded paths.
- Changelog 2.1.327 (item 2.1.327-139) widens the package-runner class to any package-running rule, including path and version forms. The page does not state this yet (docs-lag).
The contract sits outside any one owner plugin. It defines the shape that harness-config's detectors implement.
Done when
-
CCPERM_P1_RUNNER_EREmatches path-prefixed and@versionrunner forms, and the shared patterns cover each class the permission-modes section lists now, or the comment names a class left out on purpose and says why. - The lib's tests (or the consuming drivers' fixtures) gain one matched and one narrow, unmatched case per new form, and
Bash(npm test)still does not match. - The entry-diff section states the current dropped classes. It either points at the permission-modes section or lists the classes and cites changelog 2.1.327 for the package-runner widening, and its As-of date is updated.
- The text agrees with whatever
plugins/harness-config/lib/permission-patterns.shmatches after the sibling issue for that file. - Anti-pattern 1 quotes or points at the current dropped-rule list, with a new fetch date, and cites changelog 2.1.327 for the package-runner widening.
- The contract's anti-pattern list says whether each new class is in scope for the P1 detectors.
Metadata
Metadata
Assignees
Labels
Type
Fields
Work status
Priority
Activity
github-actions commentedon Nov 21, 2026
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Blast radius: harness-config's permission-patterns.sh, its tests, the audit-permission-state criteria doc, and the permission-rule-hygiene contract; read by the two audit drivers and by maintainers.
Reversible: yes; revert the pull request.
Open questions: none
I understood this as one change to update the P1 detector patterns for path and version runner forms and the three newer auto-mode drop classes, add matching tests, and bring the criteria and contract text in line with the eight-class list. The done-when items are exact. No duplicate or merged fix found. Related context: #16982.
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 21, 2026
{"v":1,"actor_id":337595936,"title_sha256":"90f7f79b5993c253cd867bf22f0d2b6e5dbd6f8bdb301417266a17ec030ed6f8","body_sha256":"7249c9af8edbe4b52f8c1c3f2340c9d27dab29099ca546569bd5b44116e005a2"}
melodic-automation-lanes commentedon Nov 21, 2026
This records a re-fire of an earlier stop, not a new one. The start gate stopped run 44933048930, the work-resolve-issue run that
agent-readystarted, before any model turn, because the GITHUB_TOKEN budget was under its start-gate share, or the window was projected to have under its start-project share of the header's limit left by the run's expected end (github-token start-gate, start-project and start-run-minutes in rate-limits.json; the run's start-gate notice names which); that run ended at 2026-11-21T18:25:15Z. work-unblock has now removed and addedagent-readyback to start a fresh run. A budget stop is the lanes' load, not a fault in this issue: it never counts toward limits.limit-stops-per-issue or thekill-switchwait.github-actions commentedon Nov 21, 2026