@davidbalzan/groundwork 0.4.5 → 0.4.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@davidbalzan/groundwork",
-  "version": "0.4.5",
+  "version": "0.4.7",
   "description": "Groundwork — an installable AI development workflow (skills + doc methodology) you bolt onto any repo.",
   "type": "module",
   "bin": {
@@ -29,7 +29,7 @@
   "author": "David Balzan",
   "license": "UNLICENSED",
   "dependencies": {
-    "@davidbalzan/groundwork-seam": "0.1.8"
+    "@davidbalzan/groundwork-seam": "0.1.10"
   },
   "scripts": {
     "groundwork": "node src/cli.mjs",

package/src/commands/doctor.mjs

@@ -1123,8 +1123,21 @@ export function doctor(targetDir, opts = {}) {
 
 // ---------- helpers ----------
 function phaseNumberFromDir(label) {
-  const m = String(label).match(/^phase(\d+)/i);
-  return m ? Number(m[1]) : null;
+  // THE PHASE TOKEN CAN HAVE A MINOR PART, and truncating it is the b-clause
+  // defect at a second granularity. There the ID token was too narrow — `3.3b`
+  // matched as `3.3`. Here the PHASE token is: `phase5.1` matched as `5`, so
+  // every box in phase 5.1 was keyed under phase 5 and the citation that names
+  // the phase correctly — `Phase 5.1 Task 7.1` — parsed as nothing at all.
+  //
+  // The consequence was worse than a miss: the citation that LOOKS right is the
+  // one that does not tie, so a correct-looking record reports unevidenced
+  // ticks. Every 5.1 citation had to be written in a form contradicting the
+  // phase's own name.
+  //
+  // Returned as a STRING, because "5.1" is not a number and Number("5.1")
+  // silently collides `phase5.1` with any future `phase5.10`.
+  const m = String(label).match(/^phase(\d+(?:\.\d+)?)/i);
+  return m ? m[1] : null;
 }
 
 function roadmapPhaseComplete(roadmapText, n) {

package/src/lib/artifacts.mjs

@@ -54,6 +54,7 @@ export const ARTIFACTS = [
   // it as claimable work. The whole point of the file is that its contents
   // are the items the fleet CANNOT pick up.
   { path: "docs/DAVID_TASKS.md", scope: "project", purpose: "Standing list of what is blocked on David — his hands, accounts, money, or ruling", writtenBy: "aide (coordinator may append)", readBy: "David, /start-session", rules: "Not a queue: no `- [ ] (Pn)` lines. Items the fleet can do belong in QUEUE.md" },
+  { path: "docs/improvements.md", scope: "project", purpose: "Improvements found by USING the kit, not by reviewing it — each entry records how it was hit", writtenBy: "aide (any agent may append an encounter)", readBy: "David (walkthrough), /plan-phase", rules: "An entry requires an ENCOUNTER: how it was hit, in the tool, by whom. A proposal with no encounter belongs in QUEUE.md. Entries keep their line after the fix lands and gain a reference, so the record of what using it felt like survives the repair. Includes a do-not-improve section: surfaces measured as working, which an in-flight phase must not regress." },
   { path: "docs/WORKSTREAMS.md", grammar: "workstreams.v1", scope: "project", purpose: "Live state of parallel streams", writtenBy: "/update-workstreams + coordinator", readBy: "everyone, /start-session", rules: "One row per active stream" },
   { path: "docs/QUEUE.md", grammar: "queue.v1", scope: "project", purpose: "Inbound queue (phases + ad-hoc)", writtenBy: "/plan-phase + human", readBy: "/start-session, coordinator", rules: "Single writer per file: human/proxy only; executors never edit it" },
   { path: "docs/DONE.md", grammar: "done.v1", scope: "project", purpose: "Completion log", writtenBy: "executor (solo you or coordinator)", readBy: "/start-session, humans", rules: "Append-only; sole executor write in the queue seam; pinned em-dash+middot line format" },