enigma-cli 1.63.0 → 1.63.1

package/assets/commands/gate.md

@@ -164,14 +164,21 @@ model while review keeps the strong one.
    enigma gate axi run --intent "<what the user set out to accomplish>"
    enigma gate axi run --intent "..." --quick   # small, or already tested: no test/document
    ```
-   `axi run` and every `axi respond` block synchronously - review, test, and CI
-   can each take several minutes, so a single call may not return for a while.
-   That is normal; allow a long timeout and do not cancel or re-issue it. To
-   check progress, use `enigma gate axi status` from a separate call. When status
-   shows `awaiting_agent: parked <duration>`, the run is parked at a gate waiting
-   for your `axi respond`. When it shows `blocked_on_user: <action>`, the run is
-   waiting on the USER, not on you or on the pipeline - say so instead of reporting
-   it as still running.
+   `axi run` and every `axi respond` block until the next decision point or the
+   outcome - review, test, and CI can each take several minutes, so one call can
+   run for half an hour. Start it as a **background** command when your runtime
+   has one (Claude Code: `run_in_background`); the runtime tells you when it
+   exits, and the user can talk to you in the meantime. A foreground call holds
+   the whole thread hostage for that time. Do not cancel or re-issue it.
+
+   **Never wait in a loop.** A `sleep` + `axi status` loop in the foreground blocks
+   the user exactly like the foreground run it replaces, and it only re-reads
+   what the backgrounded `axi run` will report anyway. `enigma gate axi status`
+   is a one-shot read for when you need the detail now. When it shows
+   `awaiting_agent: parked <duration>`, the run is parked at a gate waiting for
+   your `axi respond`. When it shows `blocked_on_user: <action>`, the run is
+   waiting on the USER, not on you or on the pipeline - say so instead of
+   reporting it as still running.
 2. If the output contains a `gate:` object, the pipeline is waiting on you. Read
    its `findings` table. Each finding has an `action`:
    - `auto-fix` - mechanical, low-risk; authorize on your own judgment with

package/assets/memory/AGENTS.md

@@ -107,13 +107,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.
+- 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.
 - Skip automatic driving only when: the user told you to skip or bypass it, the repo's `.enigma.json` sets `gate: false`, there is nothing committed to validate, `axi run` refuses the branch as protected (`gate-protected-branches`), or it declines a trivial change (`gate-trivial-lines`: push that as is, no branch or PR for it) - say so and leave the work unvalidated rather than switching branches on your own. The user's skip is final for that work: do not run it anyway, do not re-offer next turn. 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 pushes straight to it. That is intended; 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` yourself, then proceed - 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; 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). `checks-passed` means the run waits on the USER to merge: report that, not "still running", and merge (`axi merge`) only if asked.
-- While a run is active never edit code to fix a finding; the pipeline owns the fixes (respond with `--action fix`). Full reference: the gate skill / `/gate`.
+- On the default branch the pipeline opens no PR and pushes straight to it. Report that as the outcome, not a missing PR.
+- If the repo is not initialized yet (`enigma gate axi` says so), run `enigma gate init` yourself, then proceed - 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; 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). Start `axi run`/`axi respond` in the background, never a foreground `sleep` + `axi status` loop: it locks the user out for the whole run. `checks-passed` means the run waits on the USER to merge: report that, not "still running", and merge (`axi merge`) only if asked.
+- While a run is active never edit code to fix a finding; the pipeline owns the fixes (respond with `--action fix`). Reference: `/gate`.
 <!-- enigma:gate:end -->
 
 ---

package/assets/memory/CLAUDE.md

@@ -107,13 +107,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.
+- 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.
 - Skip automatic driving only when: the user told you to skip or bypass it, the repo's `.enigma.json` sets `gate: false`, there is nothing committed to validate, `axi run` refuses the branch as protected (`gate-protected-branches`), or it declines a trivial change (`gate-trivial-lines`: push that as is, no branch or PR for it) - say so and leave the work unvalidated rather than switching branches on your own. The user's skip is final for that work: do not run it anyway, do not re-offer next turn. 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 pushes straight to it. That is intended; 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` yourself, then proceed - 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; 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). `checks-passed` means the run waits on the USER to merge: report that, not "still running", and merge (`axi merge`) only if asked.
-- While a run is active never edit code to fix a finding; the pipeline owns the fixes (respond with `--action fix`). Full reference: the gate skill / `/gate`.
+- On the default branch the pipeline opens no PR and pushes straight to it. Report that as the outcome, not a missing PR.
+- If the repo is not initialized yet (`enigma gate axi` says so), run `enigma gate init` yourself, then proceed - 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; 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). Start `axi run`/`axi respond` in the background, never a foreground `sleep` + `axi status` loop: it locks the user out for the whole run. `checks-passed` means the run waits on the USER to merge: report that, not "still running", and merge (`axi merge`) only if asked.
+- While a run is active never edit code to fix a finding; the pipeline owns the fixes (respond with `--action fix`). Reference: `/gate`.
 <!-- 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.63.0",
+  "cliVersion": "1.63.1",
   "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.63.0",
+  "cliVersion": "1.63.1",
   "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.63.0",
+  "cliVersion": "1.63.1",
   "sha": "652637f818b4ce4f4d5d83fa68fa57fe7842e32fb179523958c5496af54bb938"
 }

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

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "CI/CD pipelines on any provider: faster and cheaper without dropping a check - measure first, one pipeline per commit, input-hashed caches never saved from a failed build, no duplicate checks, sharding, change filters that keep required checks green, flakes fixed not retried, and workflow security.",
   "updated": "2026-10-10T17:38:23+02:00",
-  "cliVersion": "1.63.0",
+  "cliVersion": "1.63.1",
   "sha": "87e141d1fb2dff2441a157a784fa7b57a66d6382b44d2ce74f24ad4865111407"
 }

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.63.0",
+  "cliVersion": "1.63.1",
   "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-19T12:37:59+02:00",
-  "cliVersion": "1.63.0",
+  "cliVersion": "1.63.1",
   "sha": "6b8a924cc11b61d4b45b73384aeb095ce622229359b7cc2c6ce4bb0cf3015ed7"
 }

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

@@ -7,6 +7,6 @@
     "codeGraph"
   ],
   "updated": "2026-10-10T17:38:23+02:00",
-  "cliVersion": "1.63.0",
+  "cliVersion": "1.63.1",
   "sha": "c277b1bbe9fa0849f6b8cb06d5255dd0197c9ae21a815b73bd68f5abd90e8e20"
 }

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.63.0",
+  "cliVersion": "1.63.1",
   "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.63.0",
+  "cliVersion": "1.63.1",
   "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.63.0",
+  "cliVersion": "1.63.1",
   "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-09-28T21:34:15+02:00",
-  "cliVersion": "1.63.0",
+  "cliVersion": "1.63.1",
   "sha": "648c7ae3d95d5a033f4955a87613e20b40b265bfcc24d41a5732d415abe778f9"
 }

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-09-28T21:34:15+02:00",
-  "cliVersion": "1.63.0",
+  "cliVersion": "1.63.1",
   "sha": "5d532c2dc467f960ff800c5cd7021db09911599347959cd04481f2054abd9baa"
 }

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

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Frontend architecture: reusable components, abstraction thresholds, state management, real-time form validation where an emptied or not-yet-filled field is incomplete rather than invalid (a `*` on the label and an aria-disabled submit, never \"email is not valid\" over an empty input), 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-10-02T12:11:30+02:00",
-  "cliVersion": "1.63.0",
+  "cliVersion": "1.63.1",
   "sha": "2571746934548e64ee30348bbf29b1d971d3afa0a7b32277b137150bf8803f90"
 }

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

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Git & contribution policy (senior engineering standards).",
   "updated": "2026-10-05T14:00:39+02:00",
-  "cliVersion": "1.63.0",
+  "cliVersion": "1.63.1",
   "sha": "3863620f77993eff848d52da383cabb658a14a370f4a977929e60af216eb6d8d"
 }

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

@@ -7,6 +7,6 @@
     "logoColorPolicy"
   ],
   "updated": "2026-07-17T00:17:02+02:00",
-  "cliVersion": "1.63.0",
+  "cliVersion": "1.63.1",
   "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, object- and role-level checks), credential flows with breach-checked passwords (Have I Been Pwned), OWASP Top 10 with vetted helpers for SSRF, redirects and uploads, transport/crypto baseline, cookies and consent, secure logging, and agent/MCP/tool-use safety.",
   "updated": "2026-09-28T21:34:15+02:00",
-  "cliVersion": "1.63.0",
+  "cliVersion": "1.63.1",
   "sha": "544359122f127cccedfe469232da915b04f7f4aa4795297281bd4bc9cd07d371"
 }

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.63.0",
+  "cliVersion": "1.63.1",
   "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-10-02T12:38:13+02:00",
-  "cliVersion": "1.63.0",
+  "cliVersion": "1.63.1",
   "sha": "ee8447d5ca9e5d77e0a338d1e762c30e1527ded4665c10ddf21f2c4c9ce3f2d5"
 }

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

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Concise, realistic copy for UI, landing/sales, SEO, email and docs - the user's outcome instead of the mechanism, no full enumerations or \"powered by\" lineage, none of the recognizable AI-writing tells, and never a typographic dash.",
   "updated": "2026-09-28T21:34:15+02:00",
-  "cliVersion": "1.63.0",
+  "cliVersion": "1.63.1",
   "sha": "e32623f37f1bf90fa611968ca8b216e3381771254b6af7c81a953c17a8889ddb"
 }

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-10-10T17:38:23+02:00",
-  "cliVersion": "1.63.0",
+  "cliVersion": "1.63.1",
   "sha": "86d49572f8e230377fcdafb0ac74bbc86998ffb68c3224b60793bf62a82bab16"
 }

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), real-time error timing (an emptied or not-yet-filled field is incomplete, not invalid: a `*` and an aria-disabled submit instead of \"not valid\" over an empty input), schema consistency, and safe client-facing error handling.",
   "updated": "2026-10-02T19:07:57+02:00",
-  "cliVersion": "1.63.0",
+  "cliVersion": "1.63.1",
   "sha": "7b39ded6b82cb7a8424aea7b8d59a293791205d57e7272ff63d9fa558772ecb1"
 }

package/bin/checksums.json

@@ -1,6 +1,6 @@
 {
-  "enigma-darwin-arm64": "fc98a18314a0da02606bca4474fc7e2b6d82e32706261bba0e093d8ccebf401b",
-  "enigma-linux-arm64": "6073353a4d614702fe889514b077da8b59e04baa0b3f41d1181553d5fc43718e",
-  "enigma-linux-x64": "8a6771f5c62c39501247c6b74f11a75f50ee9c6a7116c21d0b1f973166d51748",
-  "enigma-win32-x64.exe": "db9dba320cbf02422d25f57aad3df1c53013176268c5e85051d0497890392d54"
+  "enigma-darwin-arm64": "e4a3b8abf7dde9dbb49af22ff5d7096db1fe287df8619f454bf905fa31772bc0",
+  "enigma-linux-arm64": "cab2be861f711af148c80f829487475ee2d7306df843521acdc1674671b650b0",
+  "enigma-linux-x64": "77a77fbe169d3b959a3ef7c30ba173f359c19d52685bf6dc5c19b6b479688225",
+  "enigma-win32-x64.exe": "acd40a7f61708e83dccdba31b61e3b64c7b5040fad9eadab234b5c16812838dd"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "enigma-cli",
-  "version": "1.63.0",
+  "version": "1.63.1",
   "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": {