enigma-cli 1.35.4 → 1.35.5

package/assets/commands/gate.md

@@ -151,14 +151,15 @@ model while review keeps the strong one.
    - `auto-fix` - mechanical, low-risk; authorize on your own judgment with
      `--action fix`.
    - `no-op` - informational; nothing to do.
-   - `ask-user` - a judgment call only the user can make. STOP and escalate it
-     (see below) before responding.
+   - `ask-user` - the review could not settle it mechanically. Apply the
+     escalation bar below before deciding whether it is really the user's call.
 
    The gate object also carries `fix_policy`, the user's standing answer to "who
    decides?". Follow it - the `help` line spells out what it means for the gate in
    front of you, and it is the user's setting, not a suggestion:
    - `assisted` (default) - anything mechanical was already settled before this
-     gate reached you, so what is left is the judgment call. Escalate it.
+     gate reached you. Escalate what is left only if it clears the bar below;
+     otherwise fix it yourself.
    - `ask` - the user wants every finding put to them, `auto-fix` ones included.
      Relay them and let the user choose instead of authorizing anything yourself.
    - `auto` - the user asked you to settle everything. Respond without checking back.
@@ -194,11 +195,27 @@ acknowledge those and list each fix.
 
 ## Escalate ask-user findings
 
-A finding marked `ask-user` is the user's decision, not yours. Relay it verbatim
-(its `id`, `file`, full `description`) - do not paraphrase or pre-judge - ask how
-to proceed, then translate their answer into the matching `respond` call. The
-exceptions are `fix_policy: auto` and `--yes` (below), both of which are standing
-consent to drive every gate unattended.
+**"Should I fix this?" is not an escalation.** Under `assisted` the user already
+said fix, and ask about the rest - the rest being a genuine doubt, not permission
+to repair a defect the review just proved. A finding clears the bar only when the
+answer is not already yes:
+
+- fixing it would contradict what the user asked for, or undo a decision they
+  made deliberately;
+- fixing it changes agreed product behavior, or breaks something else;
+- the fix is a very large change, not a repair.
+
+Everything else - a bug, a regression, a rollback that reopens what the change
+closed, a missing guard - you authorize yourself with `--action fix` and real
+`--instructions`. Recommending a fix and then asking permission for it is the
+same question twice: if your own answer is "fix it", respond `fix`. Under `ask`
+the bar does not apply: everything goes back to the user. Under `auto`, nothing
+does.
+
+When a finding does clear the bar, relay it verbatim (its `id`, `file`, full
+`description`) - do not paraphrase or pre-judge - ask how to proceed, then
+translate the answer into the matching `respond` call. Batch every such finding
+into ONE question rather than one gate per round trip.
 
 If you have clear consent to drive the whole run automatically, pass `--yes` to
 `axi run` or `axi respond`: it treats every actionable finding (auto-fix and

package/assets/memory/AGENTS.md

@@ -98,13 +98,13 @@ Prose to the user is compressed at level **{{output-level}}**. It shapes the ANS
 <!-- enigma:gate:start -->
 ### AI Quality Gate (Automatic)
 
-- The AI quality gate is active. When you finish a code task and the changes are committed, drive the gate yourself before reporting the work done - on WHATEVER branch the work is on, the default branch included. The user should not have to ask for it or run any setup command.
-- Skip automatic driving only when: the user told you to skip it, the repo's `.enigma.json` sets `gate: false`, there is nothing committed to validate, or `axi run` refuses the branch as protected (`gate-protected-branches`) - then say so and leave the work unvalidated rather than switching branches on your own. To stop it for good the user runs `/gate off` (this project) or `enigma config gate off -g` (everywhere); offer that instead of quietly not running it.
-- Those are the only exits and each has to be NAMED. Asking is not one of them: the gate being on is already the decision, so "the gate has not run, tell me if you want me to launch it" ends a turn on a question with one answer. Ending unvalidated and silent is worse. `enigma verify` denies the stop both ways - on a message that reports the gate as skipped, and on commits no run ever saw.
-- On the default branch the pipeline opens no PR and its push lands directly on that branch. That is the intended behavior there; report it as the outcome instead of waiting for a PR link.
-- If the repo is not initialized yet (`enigma gate axi` says so), run `enigma gate init` once yourself, then proceed - an uninitialized repo is a setup step you can perform, never a reason to stop or ask. If `enigma gate` itself misbehaves, `enigma gate doctor` reports why.
-- Drive it through the `/gate` workflow (`enigma gate axi run --intent "<what the user set out to accomplish>"`). A gate it hands back carries `fix_policy`, the user's standing answer to who decides - follow it: under `assisted` (the default) escalate the `ask-user` findings verbatim, under `ask` put every finding to the user before authorizing anything, under `auto` settle them all yourself. Do NOT pass `--yes` (the setting is how the user grants that) and do NOT merge the PR yourself - on `checks-passed`, leave the PR ready and ask the user to review and merge it.
-- While a run is active never edit code to fix a finding; the pipeline owns the fixes (respond with `--action fix`). The full command reference lives in the gate skill / `/gate` command.
+- The AI quality gate is active. When you finish a code task and the changes are committed, drive the gate yourself before reporting the work done - on WHATEVER branch the work is on, the default branch included. The user should not have to ask for it.
+- Skip automatic driving only when: the user told you to skip it, the repo's `.enigma.json` sets `gate: false`, there is nothing committed to validate, or `axi run` refuses the branch as protected (`gate-protected-branches`) - then say so and leave the work unvalidated rather than switching branches on your own. To stop it for good the user runs `/gate off` (this project) or `enigma config gate off -g` (everywhere); offer that instead of silently skipping it.
+- Those are the only exits and each has to be NAMED. Asking is not one of them: the gate being on is already the decision, so "tell me if you want me to launch it" ends a turn on a question with one answer. Ending unvalidated and silent is worse. `enigma verify` denies the stop both ways - on a message that reports the gate as skipped, and on commits no run ever saw.
+- On the default branch the pipeline opens no PR and its push lands directly on that branch. That is intended there; report it as the outcome instead of waiting for a PR link.
+- If the repo is not initialized yet (`enigma gate axi` says so), run `enigma gate init` once yourself, then proceed - it is a setup step you can perform, never a reason to stop or ask. If `enigma gate` misbehaves, `enigma gate doctor` reports why.
+- Drive it through the `/gate` workflow (`enigma gate axi run --intent "<what the user set out to accomplish>"`). A gate it hands back carries `fix_policy`, the user's standing answer to who decides: under `assisted` (the default) escalate only what contradicts the request, undoes a deliberate decision, changes agreed behavior, or needs a very large change, and fix the rest yourself ("should I fix this?" is never the question); under `ask` put every finding to the user first; under `auto` settle them all yourself. Do NOT pass `--yes` (the setting is how the user grants it) and do NOT merge the PR yourself - on `checks-passed`, leave it ready for the user to review and merge.
+- While a run is active never edit code to fix a finding; the pipeline owns the fixes (respond with `--action fix`). Full command reference: the gate skill / `/gate` command.
 <!-- enigma:gate:end -->
 
 ---

package/assets/memory/CLAUDE.md

@@ -98,13 +98,13 @@ Prose to the user is compressed at level **{{output-level}}**. It shapes the ANS
 <!-- enigma:gate:start -->
 ### AI Quality Gate (Automatic)
 
-- The AI quality gate is active. When you finish a code task and the changes are committed, drive the gate yourself before reporting the work done - on WHATEVER branch the work is on, the default branch included. The user should not have to ask for it or run any setup command.
-- Skip automatic driving only when: the user told you to skip it, the repo's `.enigma.json` sets `gate: false`, there is nothing committed to validate, or `axi run` refuses the branch as protected (`gate-protected-branches`) - then say so and leave the work unvalidated rather than switching branches on your own. To stop it for good the user runs `/gate off` (this project) or `enigma config gate off -g` (everywhere); offer that instead of quietly not running it.
-- Those are the only exits and each has to be NAMED. Asking is not one of them: the gate being on is already the decision, so "the gate has not run, tell me if you want me to launch it" ends a turn on a question with one answer. Ending unvalidated and silent is worse. `enigma verify` denies the stop both ways - on a message that reports the gate as skipped, and on commits no run ever saw.
-- On the default branch the pipeline opens no PR and its push lands directly on that branch. That is the intended behavior there; report it as the outcome instead of waiting for a PR link.
-- If the repo is not initialized yet (`enigma gate axi` says so), run `enigma gate init` once yourself, then proceed - an uninitialized repo is a setup step you can perform, never a reason to stop or ask. If `enigma gate` itself misbehaves, `enigma gate doctor` reports why.
-- Drive it through the `/gate` workflow (`enigma gate axi run --intent "<what the user set out to accomplish>"`). A gate it hands back carries `fix_policy`, the user's standing answer to who decides - follow it: under `assisted` (the default) escalate the `ask-user` findings verbatim, under `ask` put every finding to the user before authorizing anything, under `auto` settle them all yourself. Do NOT pass `--yes` (the setting is how the user grants that) and do NOT merge the PR yourself - on `checks-passed`, leave the PR ready and ask the user to review and merge it.
-- While a run is active never edit code to fix a finding; the pipeline owns the fixes (respond with `--action fix`). The full command reference lives in the gate skill / `/gate` command.
+- The AI quality gate is active. When you finish a code task and the changes are committed, drive the gate yourself before reporting the work done - on WHATEVER branch the work is on, the default branch included. The user should not have to ask for it.
+- Skip automatic driving only when: the user told you to skip it, the repo's `.enigma.json` sets `gate: false`, there is nothing committed to validate, or `axi run` refuses the branch as protected (`gate-protected-branches`) - then say so and leave the work unvalidated rather than switching branches on your own. To stop it for good the user runs `/gate off` (this project) or `enigma config gate off -g` (everywhere); offer that instead of silently skipping it.
+- Those are the only exits and each has to be NAMED. Asking is not one of them: the gate being on is already the decision, so "tell me if you want me to launch it" ends a turn on a question with one answer. Ending unvalidated and silent is worse. `enigma verify` denies the stop both ways - on a message that reports the gate as skipped, and on commits no run ever saw.
+- On the default branch the pipeline opens no PR and its push lands directly on that branch. That is intended there; report it as the outcome instead of waiting for a PR link.
+- If the repo is not initialized yet (`enigma gate axi` says so), run `enigma gate init` once yourself, then proceed - it is a setup step you can perform, never a reason to stop or ask. If `enigma gate` misbehaves, `enigma gate doctor` reports why.
+- Drive it through the `/gate` workflow (`enigma gate axi run --intent "<what the user set out to accomplish>"`). A gate it hands back carries `fix_policy`, the user's standing answer to who decides: under `assisted` (the default) escalate only what contradicts the request, undoes a deliberate decision, changes agreed behavior, or needs a very large change, and fix the rest yourself ("should I fix this?" is never the question); under `ask` put every finding to the user first; under `auto` settle them all yourself. Do NOT pass `--yes` (the setting is how the user grants it) and do NOT merge the PR yourself - on `checks-passed`, leave it ready for the user to review and merge.
+- While a run is active never edit code to fix a finding; the pipeline owns the fixes (respond with `--action fix`). Full command reference: the gate skill / `/gate` command.
 <!-- enigma:gate:end -->
 
 ---

package/assets/skills/anti-overengineering-policy/skill.json

@@ -7,6 +7,6 @@
     "minimalCode"
   ],
   "updated": "2026-07-17T00:17:02+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "3f0dcc28341bb0407860534f7ce9314cfc91b5e673f8f3d13b89d61851ed75f6"
 }

package/assets/skills/anti-overengineering-review/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "On-demand over-engineering review - diff review, whole-repo audit, and enigma: debt-marker ledger (tags delete/stdlib/native/yagni/shrink, line/dep scoring); lists cuts, applies nothing.",
   "updated": "2026-06-16T11:24:30+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "f742a2be3f328b9ea1ff9a35a449177c2cbec35ad16e46f7054b7a873a2ab017"
 }

package/assets/skills/backend-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Backend/API architecture: controller-service-repository layering, modern TypeScript project configuration (module resolution, strict flags, @/* path alias), API and request optimization (batching, avoiding redundant calls, skipping no-op writes), server-side caching (Redis), and Zod boundary validation.",
   "updated": "2026-08-02T19:59:01+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "652637f818b4ce4f4d5d83fa68fa57fe7842e32fb179523958c5496af54bb938"
 }

package/assets/skills/ciphera-style-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Ciphera code style conventions (formatting, naming, imports incl. namespace imports for wide module surfaces, path-alias specifiers and no file extensions, comments, code-level anti-patterns; TypeScript-first, language-agnostic).",
   "updated": "2026-08-02T19:59:01+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "3beb0383a9cb0331ef8a579308a2517d24d57a8ba33751ad17d16d0a4f66e344"
 }

package/assets/skills/code-review-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Pre-delivery self-review gate, prioritized review dimensions, and change-quality criteria.",
   "updated": "2026-08-02T04:15:47+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "b35f0bb4a29f2346d9a1b00a4bfee9557a9b6a44116d9e6e59abcd945466dbcb"
 }

package/assets/skills/core-engineering-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Core engineering execution policy and harness orchestration (highest-authority rules), including the generalization rule that treats a named example as a class to sweep and fix.",
   "updated": "2026-08-02T04:28:51+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "95091678d4e72e3a9b1ef3ad0514e503a2a631f0d134bf772b4a1b3c66881995"
 }

package/assets/skills/database-expert/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Senior database architecture policy: engine selection (PostgreSQL by default, SQLite only for local-first/embedded stores), ORM selection (Prisma in TypeScript/JavaScript), query optimization, anti-duplication/normalization, scalability, and RGPD/GDPR encryption.",
   "updated": "2026-08-04T18:33:27+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "26fddc14caf697e830448a2cc453ddc470fe83d098d50bd67b278effba63274e"
 }

package/assets/skills/debugging-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Reproduce-isolate-fix debugging methodology with root-cause discipline and regression verification.",
   "updated": "2026-08-02T04:15:47+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "968876bcac9ce6e5a20be05c89ac97191b112c9e08679a8dc506d150c375fec4"
 }

package/assets/skills/dependency-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Dependency and supply-chain security: lockfiles and reproducible installs, version pinning, vulnerability auditing, vetting/minimizing packages, vendoring, and SBOM/provenance.",
   "updated": "2026-06-01T00:45:28+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "6375d835c2aef2c9bd31ce116444dc3d796f510f9970a213aa3ac4696d7e21b9"
 }

package/assets/skills/email-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Transactional email: React Email templates instead of hand-written HTML tables, server-side rendering, one send module behind the provider SDK, plain-text alternatives, idempotent background sending, link safety, and deliverability (SPF/DKIM/DMARC, bounce suppression, unsubscribe).",
   "updated": "2026-07-30T19:29:19+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "c9724fdbcdbeab99573be3fd44d4cdd97c2a394d99f3c4395f118f17356b00ed"
 }

package/assets/skills/frontend-design/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one.",
   "updated": "2026-07-29T01:18:36+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "9e30ee7d8a1a1e8c6e7f4e043857cd01841c68a427752e45bc0cad9ec5cfa279"
 }

package/assets/skills/frontend-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Frontend architecture: reusable components, abstraction thresholds, state management, no-op detection (skip any operation whose result equals current state, not just form saves; dirty means different from the loaded snapshot, not touched), instant first paint (render the shell, load data async, skeletons), perceived performance (prefetch on intent, debounce/throttle, cancel stale requests, avoid waterfalls, lazy widgets), large-list rendering (infinite scroll is the preferred default, pagination the deliberate exception when the design or the user calls for it, virtualization, skeletons, progressive loading), data views that ship their own affordances by default (a log, expense, transaction or history table is not done when the rows render: fuse.js search, the filters its column kinds imply, a date range, sort, filter state in the URL, and an export of the filtered set), every reference to an entity being a way into it (a name, id, project or path in a row links to that record, reveals it in a hover card, or at minimum copies and filters by it, never inert text; machine codes get human labels and raw payloads are never dumped into a cell), optimistic UI with rollback, visual restraint (one card level, spacing before borders, one elevation scale), icon actions (repeated row/card actions are icon-only buttons with aria-label plus title, not text labels), responsive/adaptive layout (fluid units, breakpoints, no overlap/overflow, viewport meta, touch targets), form fields that declare their keyboard and casing (autocapitalize/autocomplete/inputmode per field kind, set once in the shared Input, normalized on blur), variable-length text (min-width:0 in flex/grid, wrap vs truncate, long unbroken strings, worst-case content checks), auth screens (breached-password feedback, strength meter, cookie consent before login/register), and AI chat/agent interfaces via Vercel's AI Elements registry instead of hand-rolled message threads.",
   "updated": "2026-08-04T14:11:26+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "e5fbf094be2e7a00e40d02fd7611b7333b1249d7ac951029b8944e359135aa21"
 }

package/assets/skills/git-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Git & contribution policy (senior engineering standards).",
   "updated": "2026-08-04T20:04:42+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "f55f4ed5474d5c6e7fd0804d88ac38fb3c9c3cd863519645d1415c02f4416db7"
 }

package/assets/skills/logo-sourcing-policy/skill.json

@@ -7,6 +7,6 @@
     "logoColorPolicy"
   ],
   "updated": "2026-07-17T00:17:02+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "09cdbefd98625b02a7d03685e5deed128238ff8454a83fe22279610fe3ef8ddf"
 }

package/assets/skills/security-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Application and AI-agent security: secrets, authn/authz (least privilege), credential flows with breach-checked passwords (Have I Been Pwned), OWASP Top 10, transport/crypto baseline, cookies and consent, secure logging, and agent/MCP/tool-use safety.",
   "updated": "2026-08-02T19:59:01+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "3201b6d41437626eb7bf45648c0d7f8c419dc4de87fbd9d4ca83c5ae3b6b6edf"
 }

package/assets/skills/skill-creator/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Create new skills, modify and improve existing skills, and measure skill performance with evals and benchmarks.",
   "updated": "2026-08-03T00:16:54+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "a49f6166f57d734e0f13487332da37903e925f32257447856af0fbd6a5f1dc84"
 }

package/assets/skills/task-completion-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Exhaustive completion discipline for long/multi-item tasks - inventory, coverage ledger, verified done.",
   "updated": "2026-08-02T04:15:47+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "4c2197954135dd3375f32d839238b82a95c0e93e976ddf5a9cbc4a0cf0146e97"
 }

package/assets/skills/technical-writing-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Concise, realistic technical copy - UI microcopy, descriptions, hints, empty/error states, and README/doc prose that informs without over-explaining or restating the obvious, and never uses a typographic dash.",
   "updated": "2026-07-28T20:30:23+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "a4b792103eb1f9dad93b9d70ea79dc18fe9cbbc318facf5adb47ae5907d842f9"
 }

package/assets/skills/testing-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Test strategy, coverage gates, deterministic tests, mocking discipline, regression-first bug fixing, and test-suite organization (layout by type/domain, mirrored paths, file naming, fixture/helper placement).",
   "updated": "2026-06-16T17:11:49+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "3bdf591057b760f674fb2b1425f63acb426cda2c4f042e1a74c5a5d3807df664"
 }

package/assets/skills/validation-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Strict frontend + backend schema validation, normalization before validation (shared normalizers: trim, lowercase email, capitalize names, canonicalize links and handles), schema consistency, and safe client-facing error handling.",
   "updated": "2026-08-01T17:44:16+02:00",
-  "cliVersion": "1.35.4",
+  "cliVersion": "1.35.5",
   "sha": "225e1e26f4a49fac70714b1bebc104ea42143203cc8fcc9e3330b29f05b6e025"
 }

package/bin/checksums.json

@@ -1,6 +1,6 @@
 {
-  "enigma-darwin-arm64": "bd603ee8e1ea1e0d2fe1c0a7aaf87ba467073f314d067c33a46c78078759c49e",
-  "enigma-linux-arm64": "e621d92ce01a4e3e69b0a6ef2ca7ad337b79fcbbe72ada59ab578bcf13bf1cdd",
-  "enigma-linux-x64": "431171223a57a7a99f1e5ed4be7227394ffdca46103b1f4c80afdd5a22f30312",
-  "enigma-win32-x64.exe": "7296654a8cf971a7fbf6b3f330d6e99a85cb1a9e06932b7c4ae93fb794ce50cd"
+  "enigma-darwin-arm64": "d7d63db677ae99b63effa0b77934b215a249ac20fe5947fc15726e09efbed287",
+  "enigma-linux-arm64": "bc34aa1d504ac722b3175ee244d18790939293f7f46f3dad1902bf36c2812a26",
+  "enigma-linux-x64": "02ef0201bea472f239a48785157588366e7a4ac8917b61eda297a3679e8ff66f",
+  "enigma-win32-x64.exe": "2d6cdf067e8af9821e58c66cedd28a681b4e513f970ad4dba2d180406a8cd502"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "enigma-cli",
-  "version": "1.35.4",
+  "version": "1.35.5",
   "description": "Everything you need to work with a coding agent: install shared policy skills for Claude Code, OpenAI Codex and opencode, and set up portable git security hooks.",
   "type": "module",
   "bin": {