pi-gauntlet 5.2.1 → 5.2.2

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## v5.2.2 - 2026-09-01
+
+- `linear` skill: the once-per-session `linearis issues usage` sweep no longer requires authentication. `usage` prints local help and makes no API call, so gating it on `auth status` skipped the cheap staleness check exactly when the agent was already degraded; it now runs whenever the binary is present. Also drops a dead "or the MCP path is in use" skip clause - the sweep sits inside the present-binary branch, and MCP is the fallback only when the binary is missing. Prose only, no code or config surface. Follow-up to #22; spec `doc/specs/2026-09-01-gh-22-linear-cli-verification.md` amended to match.
+
 ## v5.2.1 - 2026-09-01
 
 - `linear` skill: seven `linearis` invocations corrected against the installed CLI (2026.7.0) - the nonexistent `issues comment-edit` becomes `issues edit <comment>`, `reply` takes a root discussion thread ID, `edit-reply` takes `<reply>`, `files upload` takes `<file>` (two occurrences), `attachments create`'s issue positional is optional, and gotcha (e) now documents two distinct relation flag sets (`relations add` has no `--blocked-by`). Setup is **preferred, not required**: a missing or unauthenticated `linearis` degrades and reports instead of blocking the run (MCP stays the fallback for a missing binary only). Drift resistance added in place - a once-per-session `linearis issues usage` consult for the issue-domain rows, a visible verified-against stamp under the quick-reference table, and one narrow parser-shape row in the failure table. Fixes #22. Spec: `doc/specs/2026-09-01-gh-22-linear-cli-verification.md`.

package/package.json

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

package/skills/linear/SKILL.md

@@ -38,15 +38,16 @@ No `linearis` and no MCP: report inability, never fabricate. MCP is the fallback
 **missing binary only** (`command -v linearis` fails); an installed-but-unauthenticated
 `linearis` re-auths rather than rerouting to MCP.
 
-**Session sweep.** When `linearis` is present and authenticated, run
-`linearis issues usage` once per session, before the first issue operation, and treat
-its output as ground truth for the **issue-domain rows** of the section 3 table (Read,
-Search, List, Create, Update, Discuss, Reply, Edit). Non-issue domains such as labels,
-teams, users, cycles, projects, attachments, files are outside this call's coverage and
-fall to the section 8 backstop, same as any row the sweep didn't run or couldn't reach.
-If the call errors, returns nothing, or the MCP path is in use, note once that the
-issue-domain rows are unverified this session and continue. The sweep lives inside this
-branch only - strictly after the override check above - so
+**Session sweep.** When `linearis` is present, run `linearis issues usage` once per
+session, before the first issue operation, and treat its output as ground truth for the
+**issue-domain rows** of the section 3 table (Read, Search, List, Create, Update,
+Discuss, Reply, Edit). Non-issue domains such as labels, teams, users, cycles, projects,
+attachments, files are outside this call's coverage and fall to the section 8 backstop,
+same as any row the sweep didn't run or couldn't reach. Authentication is not required -
+`usage` prints local help and makes no API call, so the sweep still runs on an
+installed-but-unauthenticated CLI. If the call errors or returns nothing, note once that
+the issue-domain rows are unverified this session and continue. The sweep lives inside
+the present-binary branch only - strictly after the override check above - so
 `tracker: github | none | <unknown>` still means zero probing.
 
 Optional: each `## Issue tracker` override key below, with its degradation.