pi-gauntlet 4.8.1 → 4.8.2

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## v4.8.2 - 2026-08-14
+
+Tracker-neutral skill wording - Linear is an example, not the canonical vocabulary.
+
+- `brainstorming`: `## Linear Ticket Handling` renamed to `## Ticket Handling` (consumer overrides matching by name/topic keep working - the substring survives); filename convention now `With ticket: YYYY-MM-DD-<ticket-id>-<topic>.md` with `<ticket-id>` defined as a filename-safe slug of the tracker reference (Linear keys verbatim, e.g. `gh-123` for GitHub issue `#123`); plan headers and commit messages use the tracker's native reference form.
+- `writing-plans`: plan header field `**Linear:** E-XXXX` -> `**Ticket:** <ticket-id>`; "same Linear ID" -> "same ticket ID"; commit example `(ref E-XXXX)` -> `(ref <ticket-id>)`.
+- `finishing-a-development-branch`: squash-commit example `(ref E-XXXX)` -> `(ref <ticket-id>)`.
+- AGENTS core: no-new-machinery rule added to the shared Code & Documentation Discipline section.
+
 ## v4.8.1 - 2026-08-12
 
 Fix-loop escalation now tracks convergence, not just round count (#7).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-gauntlet",
-  "version": "4.8.1",
+  "version": "4.8.2",
   "description": "Opinionated, gated workflow skills, subagent personas, and runtime extensions for the pi coding agent.",
   "author": "Jacek Juraszek",
   "type": "module",

package/skills/brainstorming/SKILL.md

@@ -180,7 +180,7 @@ Cover at minimum:
 
 Be ready to go back and clarify when something doesn't make sense.
 
-## Linear Ticket Handling
+## Ticket Handling
 
 When a ticket ID is given, fetch the ticket and treat it as **guidance, not the sole source of truth**. Propose changes to scope, approach, or acceptance criteria when they don't align with the codebase. Surface deviations in the spec doc.
 
@@ -213,8 +213,8 @@ If the change truly is mechanical and contained (rename, formatter run, dependen
 
 Spec lives in the project's `doc/specs/` (see [Project Routing](#project-routing)) with one of:
 
-- With Linear ticket: `YYYY-MM-DD-E-12345-<topic>.md`
-- Without Linear ticket: `YYYY-MM-DD-<topic>.md`
+- With ticket: `YYYY-MM-DD-<ticket-id>-<topic>.md` — `<ticket-id>` is a filename-safe slug of the tracker reference (e.g. `E-12345` for Linear, used verbatim; `gh-123` for GitHub issue `#123`). Plan headers and commit messages use the tracker's native reference form, not the filename slug.
+- Without ticket: `YYYY-MM-DD-<topic>.md`
 
 `<topic>` is a short kebab-case slug (3–6 words). Do **not** append `-design` or any other suffix.
 

package/skills/finishing-a-development-branch/SKILL.md

@@ -178,7 +178,7 @@ git merge --squash <feature-branch>
 git rm doc/plans/<plan-file>.md   # or <service>/doc/plans/<plan-file>.md
 
 # Single commit covering spec + code + review fixes.
-git commit -m "<imperative summary> (ref E-XXXX)"
+git commit -m "<imperative summary> (ref <ticket-id>)"
 
 # Verify tests on merged result
 <Step 1 command for the service(s) touched>

package/skills/writing-plans/SKILL.md

@@ -19,7 +19,7 @@ Before drafting the plan, call `phase_tracker({ action: "start", phase: "plan" }
 
 **Input:** an approved spec in `<project>/doc/specs/<filename>.md` — produced by `/skill:brainstorming` in this session, or handed off from another session (see "Resuming with a spec in hand").
 
-**Save plans to:** the sibling `doc/plans/` directory next to the spec. The plan filename matches the spec filename exactly — same date, same Linear ID (if any), same topic slug, no `-design` suffix.
+**Save plans to:** the sibling `doc/plans/` directory next to the spec. The plan filename matches the spec filename exactly — same date, same ticket ID (if any), same topic slug, no `-design` suffix.
 
 | Spec path | Plan path |
 |---|---|
@@ -185,7 +185,7 @@ Each step is **one action, 2-5 minutes**:
 
 **Verification:** `<full verification command set — tests + style + format; a single bundling entrypoint, or the listed individual commands; from the recon report / project overrides>`
 
-**Linear:** `E-XXXX` (omit if no ticket)
+**Ticket:** `<ticket-id>` (omit if none)
 
 ---
 ```
@@ -240,7 +240,7 @@ Each task uses `- [ ]` checkbox steps so execution tools (and humans) can track
 
   ```bash
   git add tests/path/test.py src/path/file.py
-  git commit -m "<imperative subject> (ref E-XXXX)"
+  git commit -m "<imperative subject> (ref <ticket-id>)"
   ```
 ```