nerftools 2.0.0__tar.gz → 2.1.0__tar.gz

{nerftools-2.0.0 → nerftools-2.1.0}/.claude/agents/nerftool-manifest-reviewer.md

@@ -149,41 +149,34 @@ Beyond outright security: rough edges that bite users.
 
 ### 9. Bash hint coverage (package-level `bash_hints`)
 
-`bash_hints` is a list of regex patterns at the package level that drive a
-pre-bash redirect hook on plugin targets that support one: when an agent
-calls raw bash with a command matching any pattern, the hook denies the
-call and points the agent at the nerf skill instead. Patterns are matched
-anywhere in the command. The hook automatically skips when it detects an
-actual wrapper invocation -- it splits the command on shell separators
-(``&&``, ``||``, ``;``, ``|``, ``&``), finds the first non-env-var token
-in each segment, and checks whether that token's basename starts with the
-wrapper prefix. So ``cd /repo && nerf-git status`` and
-``/abs/path/nerf-git-add .`` skip cleanly; ``git log --grep nerf-X`` does
-not (the prefix appears only at arg position, not at an executable
+`bash_hints` is a list of regex patterns at the package level that drive a pre-bash redirect hook on
+plugin targets that support one: when an agent calls raw bash with a command matching any pattern,
+the hook denies the call and points the agent at the nerf skill instead. Patterns are matched
+anywhere in the command. The hook automatically skips when it detects an actual wrapper invocation
+-- it splits the command on shell separators (`&&`, `||`, `;`, `|`, `&`), finds the first
+non-env-var token in each segment, and checks whether that token's basename starts with the wrapper
+prefix. So `cd /repo && nerf-git status` and `/abs/path/nerf-git-add .` skip cleanly;
+`git log --grep nerf-X` does not (the prefix appears only at arg position, not at an executable
 position).
 
-- **Coverage**: every CLI binary that this package's tools wrap must be
-  covered by at least one pattern. E.g., a package that wraps both `git`
-  and `gh` must declare patterns for both. A tool whose underlying command
-  isn't matched by any hint will silently let the agent reach for raw
-  bash without redirection -- file it as a gap.
-- **Anchoring**: prefer word-boundary anchors (`\bgit\b`) over start-of-line
-  (`^git`). Compound commands like `foo && git status` only match
-  word-boundary patterns. Start-anchored patterns miss those cases.
-- **Specificity vs. breadth**: package-level patterns are coarse on purpose
-  -- they redirect to a skill, not a specific tool. `\baz boards\b` is fine
-  even if the package doesn't yet wrap every `az boards` subcommand; the
-  hint says "the skill may wrap this," and the agent learns which tools
+- **Coverage**: every CLI binary that this package's tools wrap must be covered by at least one
+  pattern. E.g., a package that wraps both `git` and `gh` must declare patterns for both. A tool
+  whose underlying command isn't matched by any hint will silently let the agent reach for raw bash
+  without redirection -- file it as a gap.
+- **Anchoring**: prefer word-boundary anchors (`\bgit\b`) over start-of-line (`^git`). Compound
+  commands like `foo && git status` only match word-boundary patterns. Start-anchored patterns miss
+  those cases.
+- **Specificity vs. breadth**: package-level patterns are coarse on purpose -- they redirect to a
+  skill, not a specific tool. `\baz boards\b` is fine even if the package doesn't yet wrap every
+  `az boards` subcommand; the hint says "the skill may wrap this," and the agent learns which tools
   exist by loading the skill.
-- **No false positives on the wrapper**: do NOT add a pattern that would
-  match the wrapper's own name when called by its absolute path. The
-  executable-position exclusion in the hook covers normal wrapper calls,
-  but an over-eager pattern (e.g. `git` without word boundaries) can still
-  misfire on unrelated substrings in env exports or paths.
-- **Extensions**: if this manifest is an extension of an existing package
-  (same `package.name` in a different file), `bash_hints` is unioned across
-  manifests. An extension may declare additional patterns covering its new
-  surface (e.g. `\bgit lfs\b`) without restating the base patterns.
+- **No false positives on the wrapper**: do NOT add a pattern that would match the wrapper's own
+  name when called by its absolute path. The executable-position exclusion in the hook covers normal
+  wrapper calls, but an over-eager pattern (e.g. `git` without word boundaries) can still misfire on
+  unrelated substrings in env exports or paths.
+- **Extensions**: if this manifest is an extension of an existing package (same `package.name` in a
+  different file), `bash_hints` is unioned across manifests. An extension may declare additional
+  patterns covering its new surface (e.g. `\bgit lfs\b`) without restating the base patterns.
 
 ### 10. Description, intro, and metadata hygiene
 

nerftools-2.1.0/.cspell-version

@@ -0,0 +1 @@
+10.0.0

{nerftools-2.0.0 → nerftools-2.1.0}/.cspell.json

@@ -2,8 +2,7 @@
   "version": "0.2",
   "language": "en",
   "words": [
-    "agentic",
-    "Agentworks",
+    "agentworks",
     "bunx",
     "codegen",
     "coreutils",
@@ -11,50 +10,42 @@
     "dataclasses",
     "errexit",
     "esac",
-    "footgun",
-    "footguns",
     "execdir",
     "exitcode",
+    "footguns",
     "lookaheads",
     "metacharacter",
     "metacharacters",
-    "myapp",
     "mypy",
     "mywi",
     "nerfctl",
-    "nerftool",
     "nerftools",
     "okdir",
     "oneline",
     "permissioning",
     "pipefail",
-    "passthroughs",
     "pkgrun",
-    "pnpx",
-    "pyproject",
     "pytest",
     "rulesync",
-    "Rulesync",
     "stdutils",
     "subshell",
-    "TOCTOU",
+    "toctou",
     "typer",
     "uncompilable",
     "unioned",
     "upgen",
-    "uppercased",
-    "wiql",
-    "WIQL"
-  ],
-  "ignoreRegExpList": [
-    "`[^`\\r\\n]+`"
+    "uppercased"
   ],
+  "ignoreRegExpList": ["`[^`\\r\\n]+`"],
   "ignorePaths": [
     "node_modules",
     "out/",
     "CHANGELOG.md",
     "**/*.yaml",
     "**/*.yml",
-    "**/*.py"
+    "**/*.py",
+    "**/*.toml",
+    "**/*.json",
+    "**/*.jsonc"
   ]
 }

{nerftools-2.0.0 → nerftools-2.1.0}/.github/agents/nerftool-manifest-reviewer.md

@@ -151,41 +151,34 @@ Beyond outright security: rough edges that bite users.
 
 ### 9. Bash hint coverage (package-level `bash_hints`)
 
-`bash_hints` is a list of regex patterns at the package level that drive a
-pre-bash redirect hook on plugin targets that support one: when an agent
-calls raw bash with a command matching any pattern, the hook denies the
-call and points the agent at the nerf skill instead. Patterns are matched
-anywhere in the command. The hook automatically skips when it detects an
-actual wrapper invocation -- it splits the command on shell separators
-(``&&``, ``||``, ``;``, ``|``, ``&``), finds the first non-env-var token
-in each segment, and checks whether that token's basename starts with the
-wrapper prefix. So ``cd /repo && nerf-git status`` and
-``/abs/path/nerf-git-add .`` skip cleanly; ``git log --grep nerf-X`` does
-not (the prefix appears only at arg position, not at an executable
+`bash_hints` is a list of regex patterns at the package level that drive a pre-bash redirect hook on
+plugin targets that support one: when an agent calls raw bash with a command matching any pattern,
+the hook denies the call and points the agent at the nerf skill instead. Patterns are matched
+anywhere in the command. The hook automatically skips when it detects an actual wrapper invocation
+-- it splits the command on shell separators (`&&`, `||`, `;`, `|`, `&`), finds the first
+non-env-var token in each segment, and checks whether that token's basename starts with the wrapper
+prefix. So `cd /repo && nerf-git status` and `/abs/path/nerf-git-add .` skip cleanly;
+`git log --grep nerf-X` does not (the prefix appears only at arg position, not at an executable
 position).
 
-- **Coverage**: every CLI binary that this package's tools wrap must be
-  covered by at least one pattern. E.g., a package that wraps both `git`
-  and `gh` must declare patterns for both. A tool whose underlying command
-  isn't matched by any hint will silently let the agent reach for raw
-  bash without redirection -- file it as a gap.
-- **Anchoring**: prefer word-boundary anchors (`\bgit\b`) over start-of-line
-  (`^git`). Compound commands like `foo && git status` only match
-  word-boundary patterns. Start-anchored patterns miss those cases.
-- **Specificity vs. breadth**: package-level patterns are coarse on purpose
-  -- they redirect to a skill, not a specific tool. `\baz boards\b` is fine
-  even if the package doesn't yet wrap every `az boards` subcommand; the
-  hint says "the skill may wrap this," and the agent learns which tools
+- **Coverage**: every CLI binary that this package's tools wrap must be covered by at least one
+  pattern. E.g., a package that wraps both `git` and `gh` must declare patterns for both. A tool
+  whose underlying command isn't matched by any hint will silently let the agent reach for raw bash
+  without redirection -- file it as a gap.
+- **Anchoring**: prefer word-boundary anchors (`\bgit\b`) over start-of-line (`^git`). Compound
+  commands like `foo && git status` only match word-boundary patterns. Start-anchored patterns miss
+  those cases.
+- **Specificity vs. breadth**: package-level patterns are coarse on purpose -- they redirect to a
+  skill, not a specific tool. `\baz boards\b` is fine even if the package doesn't yet wrap every
+  `az boards` subcommand; the hint says "the skill may wrap this," and the agent learns which tools
   exist by loading the skill.
-- **No false positives on the wrapper**: do NOT add a pattern that would
-  match the wrapper's own name when called by its absolute path. The
-  executable-position exclusion in the hook covers normal wrapper calls,
-  but an over-eager pattern (e.g. `git` without word boundaries) can still
-  misfire on unrelated substrings in env exports or paths.
-- **Extensions**: if this manifest is an extension of an existing package
-  (same `package.name` in a different file), `bash_hints` is unioned across
-  manifests. An extension may declare additional patterns covering its new
-  surface (e.g. `\bgit lfs\b`) without restating the base patterns.
+- **No false positives on the wrapper**: do NOT add a pattern that would match the wrapper's own
+  name when called by its absolute path. The executable-position exclusion in the hook covers normal
+  wrapper calls, but an over-eager pattern (e.g. `git` without word boundaries) can still misfire on
+  unrelated substrings in env exports or paths.
+- **Extensions**: if this manifest is an extension of an existing package (same `package.name` in a
+  different file), `bash_hints` is unioned across manifests. An extension may declare additional
+  patterns covering its new surface (e.g. `\bgit lfs\b`) without restating the base patterns.
 
 ### 10. Description, intro, and metadata hygiene
 

nerftools-2.1.0/.github/dependabot.yml

@@ -0,0 +1,53 @@
+# Dependabot configuration.
+#
+# Two ecosystems are covered:
+#   - "pip" for the Python package at the repo root (reads pyproject.toml).
+#     Caveat: this repo uses uv, and Dependabot's pip ecosystem does NOT
+#     update uv.lock. Each Dependabot PR will need a follow-up `uv lock`
+#     to refresh the lockfile before CI passes. When GitHub's native `uv`
+#     ecosystem is GA, switch package-ecosystem to "uv" and drop this caveat.
+#   - "github-actions" for the workflows under .github/workflows/.
+#
+# commit-message blocks ensure Dependabot's PRs land as valid Conventional
+# Commits (the repo enforces this via release-please).
+#
+# Major-version bumps for each are kept as standalone PRs because they
+# usually need review (release notes, breaking changes); patches and
+# minors are grouped to keep the PR queue manageable.
+version: 2
+updates:
+  - package-ecosystem: pip
+    directory: /
+    schedule:
+      interval: weekly
+      day: monday
+    open-pull-requests-limit: 3
+    labels:
+      - dependencies
+      - python
+    commit-message:
+      prefix: chore
+      include: scope
+    groups:
+      python-patch-and-minor:
+        update-types:
+          - patch
+          - minor
+
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly
+      day: monday
+    open-pull-requests-limit: 3
+    labels:
+      - dependencies
+      - ci
+    commit-message:
+      prefix: chore
+      include: scope
+    groups:
+      actions-patch-and-minor:
+        update-types:
+          - patch
+          - minor

nerftools-2.1.0/.github/workflows/ci.yml

@@ -0,0 +1,121 @@
+name: CI
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+permissions:
+  contents: read
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+
+      - uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+
+      - name: Install dependencies
+        run: uv sync --frozen
+
+      - name: Ruff check
+        run: uv run ruff check nerftools/ tests/
+
+      - name: Mypy
+        run: uv run mypy nerftools/
+
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+
+      - uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+
+      - name: Install dependencies
+        run: uv sync --frozen
+
+      - name: Pytest
+        run: uv run pytest tests/ -v
+
+  # File-quality linters (prettier, markdownlint, cspell) run via the same
+  # script contributors use locally (./scripts/lint-files.sh). That keeps CI
+  # and local behavior in lockstep; the version pins, ignore lists, and
+  # exit semantics are defined exactly once.
+  lint-files:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+
+      - uses: actions/setup-node@v6
+        with:
+          node-version-file: .node-version
+
+      - name: ./scripts/lint-files.sh
+        run: ./scripts/lint-files.sh
+
+  rulesync:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+
+      - uses: actions/setup-node@v6
+        with:
+          node-version-file: .node-version
+
+      - name: Regenerate rulesync outputs
+        run: ./scripts/rulesync-upgen.sh
+
+      - name: Verify generated outputs match committed
+        run: |
+          if ! git diff --quiet; then
+            echo "::error::Rulesync output is out of sync with sources."
+            echo "Run ./scripts/rulesync-upgen.sh locally and commit the result."
+            git diff --stat
+            exit 1
+          fi
+          if [ -n "$(git ls-files --others --exclude-standard)" ]; then
+            echo "::error::Rulesync produced files outside the committed standard set."
+            echo "Either add the path to .gitignore (personal-target output) or commit it (new standard target)."
+            git ls-files --others --exclude-standard
+            exit 1
+          fi
+
+  # The plugin drift check runs the same script contributors use locally
+  # (./scripts/generate-plugins.sh --check). That keeps CI and local behavior
+  # in lockstep; the generate-and-diff semantics are defined exactly once.
+  plugins-drift:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+
+      - uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+
+      - name: Install dependencies
+        run: uv sync --frozen
+
+      - name: ./scripts/generate-plugins.sh --check
+        run: ./scripts/generate-plugins.sh --check
+
+  # Umbrella job: require this single check in branch protection on main.
+  # Adding a new job to CI means adding it to `needs:` below, so the
+  # required-checks list lives in the workflow file (alongside the jobs)
+  # rather than in GitHub settings that can drift silently.
+  ci-success:
+    if: always()
+    needs: [lint, test, lint-files, rulesync, plugins-drift]
+    runs-on: ubuntu-latest
+    steps:
+      - name: Verify all required jobs passed
+        run: |
+          if [[ "${{ contains(needs.*.result, 'failure') || contains(needs.*.result, 'cancelled') }}" == "true" ]]; then
+            echo "::error::One or more required CI jobs failed or were cancelled."
+            exit 1
+          fi
+          echo "All required CI jobs passed."

{nerftools-2.0.0 → nerftools-2.1.0}/.github/workflows/release-please.yml

@@ -3,6 +3,10 @@ name: Release Please
 on:
   push:
     branches: [main]
+  # Manual trigger lets us rebuild the release PR without pushing to main --
+  # useful when the open release PR conflicts with main (e.g. after a reformat
+  # touches the same line release-please bumps) and needs a clean regenerate.
+  workflow_dispatch:
 
 jobs:
   release-please:
@@ -23,7 +27,7 @@ jobs:
           app-id: ${{ vars.RELEASE_APP_ID }}
           private-key: ${{ secrets.RELEASE_APP_PRIVATE_KEY }}
 
-      - uses: googleapis/release-please-action@v4
+      - uses: googleapis/release-please-action@v5
         id: release
         with:
           token: ${{ steps.app-token.outputs.token }}
@@ -37,7 +41,19 @@ jobs:
           branch=$(echo '${{ steps.release.outputs.pr }}' | jq -r .headBranchName)
           echo "pr_branch=$branch" >> "$GITHUB_OUTPUT"
 
-  regenerate-dist:
+  sync-version-artifacts:
+    # release-please bumps the version in pyproject.toml and nerf.yaml, which
+    # leaves two artifacts mechanically stale:
+    #   - uv.lock: pins the local package version, so `uv sync --frozen` would
+    #     fail in CI until re-locked.
+    #   - out/*/plugin.json: nerf.yaml's version is baked into plugin.json at
+    #     generation time, so CI's plugins-drift check would fail until
+    #     regenerated.
+    # Both are mechanical consequences of the version bump release-please
+    # already made -- so we apply them on the release PR branch automatically.
+    # Contributor-driven changes (manifests, generator code, dependencies)
+    # still go through the verify-in-CI path: they must be committed by the
+    # author and CI fails if they're out of sync.
     needs: release-please
     if: needs.release-please.outputs.pr_branch
     runs-on: ubuntu-latest
@@ -58,23 +74,20 @@ jobs:
         with:
           enable-cache: true
 
-      - name: Sync lockfile and install dependencies
-        run: uv sync
+      - name: Re-lock (preserves existing pins; only the workspace version moves)
+        run: uv lock
 
-      - name: Regenerate Claude Code plugin
-        run: uv run nerf generate --target claude-plugin -c nerf.yaml --outdir ./out/claude-plugin
+      - name: Regenerate plugins (picks up new version in plugin.json)
+        run: ./scripts/generate-plugins.sh
 
-      - name: Regenerate Codex plugin
-        run: uv run nerf generate --target codex-plugin -c nerf.yaml --outdir ./out/codex-plugin
-
-      - name: Commit updated plugins and lockfile
+      - name: Commit version-bump artifacts if changed
         run: |
           git config user.name "nerftools-release[bot]"
           git config user.email "nerftools-release[bot]@users.noreply.github.com"
-          git add out/claude-plugin/ out/codex-plugin/ uv.lock
+          git add uv.lock out/claude-plugin/ out/codex-plugin/
           if git diff --cached --quiet; then
-            echo "No changes to plugin output or lockfile"
+            echo "Version-bump artifacts already in sync"
           else
-            git commit -m "build: regenerate plugins for release"
+            git commit -m "chore: sync version-bump artifacts (uv.lock, plugin outputs)"
             git push
           fi

{nerftools-2.0.0 → nerftools-2.1.0}/.github/workflows/release.yml

@@ -6,7 +6,7 @@ on:
 
 permissions:
   contents: read
-  id-token: write  # Required for trusted publishing via OIDC
+  id-token: write # Required for trusted publishing via OIDC
 
 jobs:
   verify-tag-on-main:

{nerftools-2.0.0 → nerftools-2.1.0}/.gitignore

@@ -44,6 +44,11 @@ htmlcov/
 # tmuxinator config is personal
 .tmuxinator.yml
 
+# Claude Code session-local state. Note: .claude/agents/ is rulesync-generated
+# and IS committed (see below); only transient/per-session files belong here.
+# settings.local.json is already covered by Claude Code's global ignore.
+.claude/scheduled_tasks.lock
+
 # Rulesync personal target overrides (gitignored; see rulesync.local.jsonc.example).
 rulesync.local.jsonc
 

nerftools-2.1.0/.markdownlint-cli2-version

@@ -0,0 +1 @@
+0.22.1

nerftools-2.1.0/.markdownlint-cli2.jsonc

@@ -0,0 +1,16 @@
+{
+    "config": {
+        "default": true,
+        "MD013": {
+            "line_length": 100,
+            "code_blocks": false,
+            "tables": false,
+        },
+        "MD024": {
+            "siblings_only": true,
+        },
+        "MD033": false,
+        "MD060": false,
+    },
+    "ignores": ["out/**", "CHANGELOG.md"],
+}

nerftools-2.1.0/.node-version

@@ -0,0 +1 @@
+24

nerftools-2.1.0/.prettier-version

@@ -0,0 +1 @@
+3.8.3

nerftools-2.1.0/.prettierignore

@@ -0,0 +1,17 @@
+# Auto-generated by release-please; never hand-formatted.
+**/CHANGELOG.md
+
+# Auto-generated by rulesync. Source files live in .rulesync/; edit those instead.
+# rulesync emits its own formatting and we round-trip these files on every
+# `rulesync generate`, so letting prettier reformat them would cause perpetual
+# drift between the two tools.
+.claude/agents/
+.github/agents/
+
+# Generated plugin outputs (regenerated via ./scripts/generate-plugins.sh).
+# nerf generate owns the formatting; prettier reformatting would cause drift
+# on every regen.
+out/
+
+# uv lockfile is machine-generated and managed by uv.
+uv.lock

nerftools-2.1.0/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "2.1.0"
+}

{nerftools-2.0.0 → nerftools-2.1.0}/.rulesync/subagents/nerftool-manifest-reviewer.md

@@ -150,41 +150,34 @@ Beyond outright security: rough edges that bite users.
 
 ### 9. Bash hint coverage (package-level `bash_hints`)
 
-`bash_hints` is a list of regex patterns at the package level that drive a
-pre-bash redirect hook on plugin targets that support one: when an agent
-calls raw bash with a command matching any pattern, the hook denies the
-call and points the agent at the nerf skill instead. Patterns are matched
-anywhere in the command. The hook automatically skips when it detects an
-actual wrapper invocation -- it splits the command on shell separators
-(``&&``, ``||``, ``;``, ``|``, ``&``), finds the first non-env-var token
-in each segment, and checks whether that token's basename starts with the
-wrapper prefix. So ``cd /repo && nerf-git status`` and
-``/abs/path/nerf-git-add .`` skip cleanly; ``git log --grep nerf-X`` does
-not (the prefix appears only at arg position, not at an executable
+`bash_hints` is a list of regex patterns at the package level that drive a pre-bash redirect hook on
+plugin targets that support one: when an agent calls raw bash with a command matching any pattern,
+the hook denies the call and points the agent at the nerf skill instead. Patterns are matched
+anywhere in the command. The hook automatically skips when it detects an actual wrapper invocation
+-- it splits the command on shell separators (`&&`, `||`, `;`, `|`, `&`), finds the first
+non-env-var token in each segment, and checks whether that token's basename starts with the wrapper
+prefix. So `cd /repo && nerf-git status` and `/abs/path/nerf-git-add .` skip cleanly;
+`git log --grep nerf-X` does not (the prefix appears only at arg position, not at an executable
 position).
 
-- **Coverage**: every CLI binary that this package's tools wrap must be
-  covered by at least one pattern. E.g., a package that wraps both `git`
-  and `gh` must declare patterns for both. A tool whose underlying command
-  isn't matched by any hint will silently let the agent reach for raw
-  bash without redirection -- file it as a gap.
-- **Anchoring**: prefer word-boundary anchors (`\bgit\b`) over start-of-line
-  (`^git`). Compound commands like `foo && git status` only match
-  word-boundary patterns. Start-anchored patterns miss those cases.
-- **Specificity vs. breadth**: package-level patterns are coarse on purpose
-  -- they redirect to a skill, not a specific tool. `\baz boards\b` is fine
-  even if the package doesn't yet wrap every `az boards` subcommand; the
-  hint says "the skill may wrap this," and the agent learns which tools
+- **Coverage**: every CLI binary that this package's tools wrap must be covered by at least one
+  pattern. E.g., a package that wraps both `git` and `gh` must declare patterns for both. A tool
+  whose underlying command isn't matched by any hint will silently let the agent reach for raw bash
+  without redirection -- file it as a gap.
+- **Anchoring**: prefer word-boundary anchors (`\bgit\b`) over start-of-line (`^git`). Compound
+  commands like `foo && git status` only match word-boundary patterns. Start-anchored patterns miss
+  those cases.
+- **Specificity vs. breadth**: package-level patterns are coarse on purpose -- they redirect to a
+  skill, not a specific tool. `\baz boards\b` is fine even if the package doesn't yet wrap every
+  `az boards` subcommand; the hint says "the skill may wrap this," and the agent learns which tools
   exist by loading the skill.
-- **No false positives on the wrapper**: do NOT add a pattern that would
-  match the wrapper's own name when called by its absolute path. The
-  executable-position exclusion in the hook covers normal wrapper calls,
-  but an over-eager pattern (e.g. `git` without word boundaries) can still
-  misfire on unrelated substrings in env exports or paths.
-- **Extensions**: if this manifest is an extension of an existing package
-  (same `package.name` in a different file), `bash_hints` is unioned across
-  manifests. An extension may declare additional patterns covering its new
-  surface (e.g. `\bgit lfs\b`) without restating the base patterns.
+- **No false positives on the wrapper**: do NOT add a pattern that would match the wrapper's own
+  name when called by its absolute path. The executable-position exclusion in the hook covers normal
+  wrapper calls, but an over-eager pattern (e.g. `git` without word boundaries) can still misfire on
+  unrelated substrings in env exports or paths.
+- **Extensions**: if this manifest is an extension of an existing package (same `package.name` in a
+  different file), `bash_hints` is unioned across manifests. An extension may declare additional
+  patterns covering its new surface (e.g. `\bgit lfs\b`) without restating the base patterns.
 
 ### 10. Description, intro, and metadata hygiene