@tech-leads-club/harness-toolkit 0.10.4 → 0.10.5

package/docs/concepts.md

@@ -353,7 +353,7 @@ most common way a new rule reads as protection and is not:
 | proof | what it names | how it matches |
 |---|---|---|
 | `subagent(<type>)` | the *declared type* of a spawn that finished, not the name the spawning agent gave it | exact string |
-| `command(<pattern>)` | a shell command that ran and did not fail | the pattern's words, in order, as a contiguous run inside the command — `command(gh pr create)` matches `gh pr create --fill`, not `gh api pulls`|
+| `command(<pattern>)` | a shell command that ran and did not fail | the pattern's words, in order, as a contiguous run inside the command — `command(gh pr create)` matches `gh pr create --fill`, not `gh api pulls`. A word with no `/` of its own also matches a path ending in it: `command(build.sh)` matches `./scripts/build.sh` and `/opt/tools/build.sh` alike, never a different file that merely ends the same way |
 | `gate(<name>)` | one of this harness's own gates *passing* — never just running | exact string; the only names a gate ever reports are `lint`, `test`, `docs` |
 | `file(<pattern>)` | a file edited by a write tool | exact path, **or** `*<suffix>` (a leading `*`, matched against the path's end), **or** `<dir>/` (a trailing `/`, matched as a prefix) — three shapes, not a glob engine |
 

package/docs/log.md

@@ -16,6 +16,7 @@ newest first. For what landed in which npm release, see `CHANGELOG.md` at the re
 ## 2026-08-30
 
 - **AD-120** — A rule denial names the directory and sha it actually checked ([/decisions/ad-120.md](/decisions/ad-120.md))
+- **AD-121** — command(<pattern>) matches a bare word against a path ending in it, not only an exact word ([/decisions/ad-121.md](/decisions/ad-121.md))
 
 ## 2026-08-29
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tech-leads-club/harness-toolkit",
-  "version": "0.10.4",
+  "version": "0.10.5",
   "type": "module",
   "description": "Multi-provider agent steering: gates, follow-up, handoff, policy",
   "keywords": [

package/src/core/rules/rules.trigger.ts

@@ -75,6 +75,24 @@ function matchesShape(words: readonly string[], shape: ShellShape): boolean {
   return !shape.excludeIfAny?.some((flag) => words.includes(flag));
 }
 
+/**
+ * why a basename fallback: a token with no `/` of its own names an act, not a location — `build.sh` is the
+ * same script whether it runs as `build.sh`, `./scripts/build.sh` or `/home/user/tools/scripts/build.sh`.
+ * Confirmed live: a real `command(<script>)` proof stayed unsatisfied forever because every recorded
+ * invocation ran the script by its full installed path, and a whole word is never `===` one of its own path
+ * segments ([/decisions/ad-121.md](/decisions/ad-121.md)).
+ *
+ * why the `/` guard and not a bare suffix check: a token that already contains a `/` is the operator naming a
+ * location, and a location is exact or it is the wrong one — treating `not_review.py` as a match for
+ * `review.py` would turn a word boundary into a substring scan.
+ */
+function tokenMatches(word: string | undefined, token: string): boolean {
+  if (word === undefined) {
+    return false;
+  }
+  return word === token || (!token.includes("/") && word.endsWith(`/${token}`));
+}
+
 /**
  * why a phrase and not a word: an operator writes `command(gh pr review)`, meaning those words in that order.
  * Matching the raw string against the whole command would let a heredoc or an unrelated argument satisfy it.
@@ -84,7 +102,7 @@ export function matchesPhrase(words: readonly string[], pattern: string): boolea
   if (phrase.length === 0) {
     return false;
   }
-  return words.some((_, start) => phrase.every((token, index) => words[start + index] === token));
+  return words.some((_, start) => phrase.every((token, index) => tokenMatches(words[start + index], token)));
 }
 
 export function triggerMatches(trigger: RuleTrigger, context: TriggerContext): boolean {