infinity-harness 2.0.2 → 2.0.4

package/CHANGELOG.md

@@ -4,6 +4,31 @@ All notable changes to this project are documented here.
 Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versions follow
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.0.4] — 2026-08-23
+
+### Changed
+
+- **A domain skill now has to be pulled in by the task's own vocabulary.** Run against a real project
+  the matcher offered `cli-design` for *"serialise plan writes so two workers cannot race on the
+  lock"* — because the goal above it read "ship the payments rewrite behind a flag", and `flags` is
+  on that skill's tag list. One incidental word is not vocabulary. A `domain` or `meta` skill must
+  now clear the bar on tag hits alone; the phase ranks it but never qualifies it. `process` skills
+  are unchanged — belonging to the phase is the whole point of them.
+
+---
+
+## [2.0.3] — 2026-08-23
+
+### Fixed
+
+- **`npm test` failed in any project that had actually been used.** The surface guard added in 2.0.2
+  walked the filesystem for documents to check, so it also read the files the harness *writes* —
+  `harness/session-handoff.md`, `harness/.run-prompt.md` — which are git-ignored scratch carrying
+  whatever commands were current when they were generated. It now asks git what the repository
+  ships. A test that fails because you ran the tool is a test people turn off.
+
+---
+
 ## [2.0.2] — 2026-08-23
 
 Everything here is one bug: the package told people to run commands it does not have. 2.0.1 fixed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "infinity-harness",
-  "version": "2.0.2",
+  "version": "2.0.4",
   "description": "A pi agent extension that runs a gated build pipeline unattended \u2014 enforces phases, validates with deterministic gates, and keeps working for hours or days without losing the plan.",
   "type": "module",
   "keywords": [

package/src/core/skills.ts

@@ -330,25 +330,26 @@ export function matchSkills(skills: SkillMeta[], options: MatchOptions = {}): Sk
       if (hit && !hits.includes(t)) hits.push(t);
     }
 
-    const position = phase ? skill.phases.indexOf(phase) : -1;
-    const phaseCounts = position >= 0 && (skill.kind === "process" || hits.length > 0);
-    if (phaseCounts) {
-      score += Math.max(1, PHASE_WEIGHT - position);
-      reasons.push(`${phase} phase`);
+    // `meta` is on every meta skill's tag list, so counting it like any other
+    // hit would surface all of them constantly. They have to be asked for.
+    const counted = skill.kind === "meta" ? hits.filter((h) => h !== "meta") : hits;
+    const tagScore = TAG_WEIGHT * Math.min(counted.length, MAX_TAG_HITS);
+
+    // A domain skill has to be pulled in by the task's own vocabulary, and one
+    // incidental word is not vocabulary. "Ship the payments rewrite behind a
+    // flag" should not summon the CLI-design skill because `flags` is on its
+    // tag list. The phase ranks a domain skill; it never qualifies one.
+    if (skill.kind !== "process" && tagScore < MIN_SCORE) continue;
+
+    score += tagScore;
+    if (counted.length) {
+      reasons.push(`matches ${counted.slice(0, MAX_TAG_HITS).map((h) => `"${h}"`).join(", ")}`);
     }
 
-    if (hits.length && skill.kind !== "meta") {
-      score += TAG_WEIGHT * Math.min(hits.length, MAX_TAG_HITS);
-    } else if (hits.length) {
-      // A meta skill has to be asked for: `meta` is on all of their tag lists,
-      // so counting it like any other hit would surface all four constantly.
-      const real = hits.filter((h) => h !== "meta");
-      if (real.length === 0) continue;
-      score += TAG_WEIGHT * Math.min(real.length, MAX_TAG_HITS);
-    }
-    if (hits.length) {
-      const shown = hits.filter((h) => h !== "meta" || skill.kind !== "meta").slice(0, MAX_TAG_HITS);
-      if (shown.length) reasons.push(`matches ${shown.map((h) => `"${h}"`).join(", ")}`);
+    const position = phase ? skill.phases.indexOf(phase) : -1;
+    if (position >= 0 && (skill.kind === "process" || counted.length > 0)) {
+      score += Math.max(1, PHASE_WEIGHT - position);
+      reasons.unshift(`${phase} phase`);
     }
 
     // Naming the skill in the task means it, and outranks any guess.