task-pipeline-skill 1.75.0 → 1.76.1

package/plugins/task-pipeline/skills/task-pipeline/references/artifacts.md

@@ -200,10 +200,18 @@ plugins/task-pipeline/
     templates/                                # skeletons seeded into a host project
       hygiene.sh docgate.sh                 # -> scripts/check-hygiene.sh, check-docs.sh
       README.md                             # the index — and it is the list, not a copy of it
+    scripts/graph.py                          # the work graph, walked so the model never reads it
+  skills/evidence-docs/SKILL.md               # the ten canons, as a navigator
+  skills/project-audit/                       # a whole project as the subject
+    SKILL.md                                  #   the six phases, cold start
+    references/probes.md                      #   the probe catalogue, by stack and shape
+    scripts/audit.py                          #   discovery, registry, HTML + JSON sidecar
+  commands/project-audit.md                   # /project-audit
 cursor/rules/task-pipeline.mdc                # Cursor channel (self-contained rule)
 bin/task-pipeline.js                          # npx installer (package task-pipeline-skill)
 install.sh                                    # POSIX installer
 test/validate.py                              # structural validator (npm test)
+test/graph_test.py  test/project_audit_test.py  # the other two halves of `npm test`
 .github/workflows/{validate,release}.yml      # CI + toggleable release automation
 .github/ISSUE_TEMPLATE/  .github/PULL_REQUEST_TEMPLATE.md
 package.json  .gitignore

package/plugins/task-pipeline/skills/task-pipeline/references/audit.md

@@ -34,6 +34,14 @@ whose whole job is "audit X" runs nothing else.
 | [`acceptance.md`](acceptance.md) | stage 10 | did everything **on the list** ship, with evidence? |
 | [`loop-guard.md`](loop-guard.md) | any **editing** loop churns | is this pass undoing the last one? |
 | **this file** | any **audit** pass | what is broken or missing that nobody has compared? |
+| the `project-audit` skill | a **whole project** is the subject | what is true of this repository today — from a cold start, with no brief |
+
+**`project-audit` is the cold-start caller of this file, not a second copy of
+it.** This ladder needs a REQ row and a module map to walk; most repositories
+have neither, and *"your spine is missing"* is a true first finding and a useless
+audit. That skill discovers what the project is, probes it, reads the production
+evidence a repository cannot hold, and hands phase 4 back here — so the method
+below stays the one place it is written.
 
 `loop-guard.md` governs loops that *change* things — the fix loop, a re-entered
 stage. Its trip means a decision is being re-litigated at the wrong altitude. This