enigma-cli 1.15.2 → 1.15.3

package/assets/memory/AGENTS.md

@@ -16,7 +16,7 @@
 - backend-policy, frontend-policy, database-expert, validation-policy: server, client, persistence, and input-validation work.
 - security-policy: secrets, auth, permissions, crypto, untrusted/tool output, and AI-agent/MCP/tool-use safety.
 - dependency-policy: adding/upgrading/auditing dependencies, lockfiles, and supply-chain risk.
-- testing-policy, test-organization-policy, code-review-policy, debugging-policy, git-policy: tests, test-suite layout (structured subfolders, never a flat tests/ dump), pre-delivery review, debugging, and commits/PRs.
+- testing-policy, code-review-policy, debugging-policy, git-policy: tests and test-suite layout (structured subfolders, never a flat tests/ dump), pre-delivery review, debugging, and commits/PRs.
 - task-completion-policy: long or multi-item tasks (1:1 ports, migrations, repo-wide changes) - work-unit inventory, persistent coverage ledger, and verified completion before any "done" claim.
 
 ### Always-On Rules (never skipped, even if no skill loads)

package/assets/memory/CLAUDE.md

@@ -16,7 +16,7 @@
 - backend-policy, frontend-policy, database-expert, validation-policy: server, client, persistence, and input-validation work.
 - security-policy: secrets, auth, permissions, crypto, untrusted/tool output, and AI-agent/MCP/tool-use safety.
 - dependency-policy: adding/upgrading/auditing dependencies, lockfiles, and supply-chain risk.
-- testing-policy, test-organization-policy, code-review-policy, debugging-policy, git-policy: tests, test-suite layout (structured subfolders, never a flat tests/ dump), pre-delivery review, debugging, and commits/PRs.
+- testing-policy, code-review-policy, debugging-policy, git-policy: tests and test-suite layout (structured subfolders, never a flat tests/ dump), pre-delivery review, debugging, and commits/PRs.
 - task-completion-policy: long or multi-item tasks (1:1 ports, migrations, repo-wide changes) - work-unit inventory, persistent coverage ledger, and verified completion before any "done" claim.
 
 ### Always-On Rules (never skipped, even if no skill loads)

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

@@ -3,6 +3,6 @@
   "version": "1.0.0",
   "provider": "FJRG2007/enigma",
   "description": "Minimal-code discipline - YAGNI ladder, deletion over addition, no unrequested abstractions, and the enigma: shortcut-marking convention; intensity via the minimal-code setting.",
-  "cliVersion": "1.15.2",
+  "cliVersion": "1.15.3",
   "sha": "297c5d9a0573a319a6f8476f5b1da8cb93e6f3297f13b76ac25d91ce10c7b523"
 }

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

@@ -3,6 +3,6 @@
   "version": "1.0.0",
   "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.",
-  "cliVersion": "1.15.2",
+  "cliVersion": "1.15.3",
   "sha": "f742a2be3f328b9ea1ff9a35a449177c2cbec35ad16e46f7054b7a873a2ab017"
 }

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

@@ -3,6 +3,6 @@
   "version": "1.1.0",
   "provider": "FJRG2007/enigma",
   "description": "Backend/API architecture: controller-service-repository layering, API and request optimization, server-side caching (Redis), and Zod boundary validation.",
-  "cliVersion": "1.15.2",
+  "cliVersion": "1.15.3",
   "sha": "a46c3cd00aa5f47adb1e7907f1d2bc6f5562f7a272890dee9b1121976ac04ae1"
 }

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

@@ -3,6 +3,6 @@
   "version": "1.1.1",
   "provider": "FJRG2007/enigma",
   "description": "Ciphera code style conventions (formatting, naming, imports, comments, code-level anti-patterns; TypeScript-first, language-agnostic).",
-  "cliVersion": "1.15.2",
+  "cliVersion": "1.15.3",
   "sha": "74f638aec13e8c93257fe1ad604c28b07e9a7c456796a4ceefcc99217d9e7039"
 }

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

@@ -3,6 +3,6 @@
   "version": "1.0.0",
   "provider": "FJRG2007/enigma",
   "description": "Pre-delivery self-review gate, prioritized review dimensions, and change-quality criteria.",
-  "cliVersion": "1.15.2",
+  "cliVersion": "1.15.3",
   "sha": "3d3bbe0602d5bbb4afe37648fe3c2fa39376b1bcbac5d8c441f01fad1e866ed0"
 }

package/assets/skills/core-engineering-policy/SKILL.md

@@ -33,8 +33,7 @@ description: Highest-authority engineering rules - priority hierarchy, modular a
   - Any dependency added/upgraded/removed/audited, or package manifest/lockfile change -> dependency-policy.
   - Any UI, client state, data fetching, or client caching -> frontend-policy.
   - Any API endpoint, service, controller, or server request flow -> backend-policy.
-  - Any new or changed code that needs verification -> testing-policy.
-  - Any test file created, moved, or renamed, or a test suite scaffolded/restructured -> test-organization-policy.
+  - Any new or changed code that needs verification, or any test file created/moved/renamed or a test suite scaffolded/restructured -> testing-policy.
   - Any source code written, refactored, or reviewed (formatting, naming, language idioms) -> ciphera-style-policy.
   - Any implementation code being written or refactored, or any "be lazy"/"simplify"/over-engineering request -> anti-overengineering-policy.
   - A one-shot complexity-only review/audit, "what can we delete", "find bloat", or an enigma: debt-marker ledger -> anti-overengineering-review.
@@ -82,8 +81,7 @@ This core policy owns orchestration, architecture, and the global rules. Each co
 - validation-policy: strict frontend + backend schema validation (Zod), schema consistency, client-facing error handling.
 - frontend-policy: frontend structure, reusable components, abstraction threshold, client-side caching, optimistic UI and rollback.
 - backend-policy: API/service architecture, controller-service-repository layering, API/request optimization, server-side caching (Redis).
-- testing-policy: test strategy, coverage gates, deterministic tests, test/regression-first discipline.
-- test-organization-policy: test-suite layout - structure by test type and domain, mirrored source paths, file naming, fixture/helper/factory placement.
+- testing-policy: test strategy, coverage gates, deterministic tests, test/regression-first discipline, and test-suite layout (structure by type and domain, mirrored source paths, file naming, fixture/helper/factory placement).
 - code-review-policy: self-review before delivery, review dimensions, change-quality gates.
 - debugging-policy: reproduce-isolate-fix methodology and root-cause discipline.
 - git-policy: commits, branches, and pull request standards.

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

@@ -1,8 +1,8 @@
 {
   "name": "core-engineering-policy",
-  "version": "1.8.0",
+  "version": "1.9.0",
   "provider": "FJRG2007/enigma",
   "description": "Core engineering execution policy and harness orchestration (highest-authority rules).",
-  "cliVersion": "1.15.2",
-  "sha": "54144f87e477c4b1c004abf2268d9294778e1e96e634bb837b4b1717aa1b7b16"
+  "cliVersion": "1.15.3",
+  "sha": "82d246faa4770248a36f143926fbf06bd3ffc082959014184548b57193770fab"
 }

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

@@ -3,6 +3,6 @@
   "version": "1.1.0",
   "provider": "FJRG2007/enigma",
   "description": "Senior database architecture policy: query optimization, anti-duplication/normalization, scalability, and RGPD/GDPR encryption.",
-  "cliVersion": "1.15.2",
+  "cliVersion": "1.15.3",
   "sha": "2883bcecb3202683ae6f81b073c3d6a9cec9c55029e011bdd06ba7ac3537297e"
 }

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

@@ -3,6 +3,6 @@
   "version": "1.0.0",
   "provider": "FJRG2007/enigma",
   "description": "Reproduce-isolate-fix debugging methodology with root-cause discipline and regression verification.",
-  "cliVersion": "1.15.2",
+  "cliVersion": "1.15.3",
   "sha": "14b0064c8b33a0dc85e51464b05005cf5801c756b1101789a6924b9548420f6b"
 }

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

@@ -3,6 +3,6 @@
   "version": "1.0.0",
   "provider": "FJRG2007/enigma",
   "description": "Dependency and supply-chain security: lockfiles and reproducible installs, version pinning, vulnerability auditing, vetting/minimizing packages, vendoring, and SBOM/provenance.",
-  "cliVersion": "1.15.2",
+  "cliVersion": "1.15.3",
   "sha": "6375d835c2aef2c9bd31ce116444dc3d796f510f9970a213aa3ac4696d7e21b9"
 }

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

@@ -3,6 +3,6 @@
   "version": "1.0.0",
   "provider": "FJRG2007/enigma",
   "description": "Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one.",
-  "cliVersion": "1.15.2",
+  "cliVersion": "1.15.3",
   "sha": "431645565aec8a4ab4cd17247139f78c377a9bcfcfc4ee1d6f252199c332d86f"
 }

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

@@ -3,6 +3,6 @@
   "version": "1.3.0",
   "provider": "FJRG2007/enigma",
   "description": "Frontend architecture: reusable components, abstraction thresholds, state management, no-op save detection, large-list rendering (infinite scroll/pagination, virtualization, skeletons, progressive loading), and optimistic UI with rollback.",
-  "cliVersion": "1.15.2",
+  "cliVersion": "1.15.3",
   "sha": "26962db5a8b607e95098a6d88977aee59a10bd14e03afe97245f2b013fd21a9a"
 }

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

@@ -3,6 +3,6 @@
   "version": "1.3.0",
   "provider": "FJRG2007/enigma",
   "description": "Git & contribution policy (senior engineering standards).",
-  "cliVersion": "1.15.2",
+  "cliVersion": "1.15.3",
   "sha": "73a978ef11f4def067f9252fc3e2e6aa737a08b6d58ad8a2a45cbcd4b02813f6"
 }

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

@@ -3,6 +3,6 @@
   "version": "1.0.0",
   "provider": "FJRG2007/enigma",
   "description": "Application and AI-agent security: secrets, authn/authz (least privilege), OWASP Top 10, transport/crypto baseline, secure logging, and agent/MCP/tool-use safety.",
-  "cliVersion": "1.15.2",
+  "cliVersion": "1.15.3",
   "sha": "9971e9d9127397d0152e89d24aad3191e2935e55a8483db7fd15f5d4d7a60e7a"
 }

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

@@ -3,6 +3,6 @@
   "version": "1.0.0",
   "provider": "FJRG2007/enigma",
   "description": "Create new skills, modify and improve existing skills, and measure skill performance with evals and benchmarks.",
-  "cliVersion": "1.15.2",
+  "cliVersion": "1.15.3",
   "sha": "699586cce82ec0a5458288b598ee7e5ebdddb3dfcf19db354d8bc5e85e47c1c7"
 }

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

@@ -3,6 +3,6 @@
   "version": "1.1.0",
   "provider": "FJRG2007/enigma",
   "description": "Exhaustive completion discipline for long/multi-item tasks - inventory, coverage ledger, verified done.",
-  "cliVersion": "1.15.2",
+  "cliVersion": "1.15.3",
   "sha": "6e3facba307eb2b55cefbab2e4b2a346a2b82f93c3ef47e11ebeb78c3c9453a8"
 }

package/assets/skills/testing-policy/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: testing-policy
-description: Test strategy (test pyramid), coverage gates, deterministic tests, mocking discipline, and regression-first bug fixing. Use when writing or changing code that needs tests, when asked to add or fix tests, or after fixing a bug to add a regression test.
+description: Test strategy (test pyramid), coverage gates, deterministic tests, mocking discipline, regression-first bug fixing, and test-suite organization (directory structure by test type and domain, mirrored source paths, file naming, fixture/helper/factory placement). Use when writing or changing code that needs tests, when asked to add or fix tests, after fixing a bug to add a regression test, or when creating, moving, renaming, or structuring test files - never dump tests flat into a single tests/ folder.
 ---
 
 # Testing Policy (Senior Engineering Standards)
@@ -8,8 +8,9 @@ description: Test strategy (test pyramid), coverage gates, deterministic tests,
 ## Activation Scope
 
 - Apply whenever code is written, changed, or fixed, and whenever the user asks for tests.
-- Owns test strategy, coverage expectations, determinism, and test-first discipline.
-- Test file placement, suite layout, naming of test files, and fixture/helper organization live in test-organization-policy; apply it alongside this skill when creating or moving test files.
+- Apply whenever a test file is created, moved, or renamed, and whenever a test suite is scaffolded or restructured.
+- Owns test strategy, coverage expectations, determinism, mocking discipline, and test-first discipline.
+- Owns test-suite layout: directory structure, subfolders, file naming, and placement of fixtures, helpers, factories, and mocks.
 
 ---
 
@@ -70,8 +71,84 @@ description: Test strategy (test pyramid), coverage gates, deterministic tests,
 
 ---
 
+## Suite Organization: Core Principle
+
+- A test suite is navigable code: anyone must find the tests for a module in seconds from the module's path alone, and find the module from its test's path.
+- Never dump test files flat into a single tests/ folder. Flat suites hide coverage gaps, cause name collisions, and stop scaling past a handful of files.
+- Organize from the first test file. Structure is cheapest at file creation and most expensive after the folder is a mess.
+
+---
+
+## Framework Convention First
+
+- Every ecosystem has an established convention; it beats any custom layout:
+  - JS/TS (Vitest, Jest, Bun): colocated `*.test.ts` next to the source file, a `__tests__/` folder per directory, or a mirrored `tests/` tree - follow whichever the repo already uses.
+  - Python (pytest): a `tests/` package mirroring the source package; shared fixtures in `conftest.py` at the narrowest directory that covers their users.
+  - Go: `_test.go` colocated in the same package (mandated by the toolchain); black-box tests use the `_test` package suffix.
+  - Rust: unit tests in `#[cfg(test)] mod tests` inside the module; integration tests as separate files under the crate-root `tests/`.
+  - Java/Kotlin: `src/test/<lang>/` mirroring the `src/main/<lang>/` package path exactly.
+- In an existing repo, detect the established layout and extend it; never introduce a second competing layout. Migrations to a better layout are proposed explicitly, not done by stealth.
+
+---
+
+## Structure by Test Type, Then by Domain
+
+- When more than one test type exists, separate types at the top level - they differ in speed, dependencies, and CI stage:
+
+  ```text
+  tests/
+    unit/          fast, isolated, no I/O
+    integration/   module boundaries, DB, contracts
+    e2e/           critical user flows only
+    fixtures/      shared static data
+    helpers/       shared builders, factories, fakes
+  ```
+
+- Inside each type, mirror the source tree: tests for `src/<domain>/<module>` live at `tests/<type>/<domain>/<module>.<suffix>`.
+- Group e2e tests by user flow (e.g. `e2e/checkout/`), not by source module - flows cross modules.
+- Default to one test file per module under test; split a large file by scenario, never by arbitrary size cuts.
+- Keep the test runner's discovery config (`testMatch`, `testpaths`, includes) in sync with the layout; a test the runner cannot find is dead code.
+
+---
+
+## Naming Conventions
+
+- Test file name = module under test + the framework's suffix: `parser.test.ts`, `test_parser.py`, `parser_test.go`.
+- When splitting by scenario, encode the scenario in the name: `parser.errors.test.ts`, `auth.session-expiry.test.ts`.
+- Suite and case names describe behavior, not implementation - name tests by the behavior they verify, consistent with the Test Quality Rules above.
+- Forbidden names: `test1`, `misc`, `temp`, `new`, `utils-tests`, or any name that does not identify what is verified.
+
+---
+
+## Shared Test Code Placement
+
+- Fixtures (static data), factories/builders (object construction), helpers (setup/assertion logic), and fakes each get their own folder; do not mix them in one grab-bag file.
+- Place shared test code at the narrowest scope that covers its users; promote it upward only when a second consumer appears (same reuse rule as production code).
+- Test helpers are production code: deduplicate, name well, and review them like any other module.
+- Never import from another test file; extract the shared piece into a helper module instead.
+- Large fixtures live as data files under `fixtures/`, named after the scenario they encode, not inlined into test bodies.
+
+---
+
+## Scaling & Maintenance
+
+- When adding a test to an existing flat or misplaced suite: place the new test correctly and surface the layout debt; do not extend the mess to match it.
+- Layout migrations are pure moves: never change test logic in the same commit as a file move (atomic-commit rule in git-policy).
+- After any move, run the affected suite to prove discovery still works, and delete emptied folders.
+- If two layouts coexist after a partial migration, finish the migration or document the boundary; a half-migrated suite is worse than either layout.
+
+---
+
+## Decision Rule: Colocated vs Centralized
+
+- Colocated tests (next to source) fit unit tests in ecosystems that idiomatically support it (JS/TS, Go, Rust) - shortest navigation distance, moves with the code.
+- A centralized `tests/` tree fits integration/e2e tests, packages that must exclude tests from the published artifact, and ecosystems whose tooling expects it (Python, Java).
+- Mixing is fine when each side follows its rule (e.g. colocated unit + centralized integration); mixing within the same test type is not.
+
+---
+
 ## Reporting
 
 - State plainly what was tested and the actual result.
 - If tests fail, report the failure with output; do not claim success.
-- If testing was skipped or partial, say so explicitly and why.
+- If testing was skipped or partial, say so explicitly and why.

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

@@ -1,8 +1,8 @@
 {
   "name": "testing-policy",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "provider": "FJRG2007/enigma",
-  "description": "Test strategy, coverage gates, deterministic tests, mocking discipline, and regression-first bug fixing.",
-  "cliVersion": "1.15.2",
-  "sha": "dd5c0bb67aba7f31b2f520e626a9df512b5ad2d2e7baf5567fe64d9e28a437db"
+  "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).",
+  "cliVersion": "1.15.3",
+  "sha": "3bdf591057b760f674fb2b1425f63acb426cda2c4f042e1a74c5a5d3807df664"
 }

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

@@ -3,6 +3,6 @@
   "version": "1.0.0",
   "provider": "FJRG2007/enigma",
   "description": "Strict frontend + backend schema validation, schema consistency, and safe client-facing error handling.",
-  "cliVersion": "1.15.2",
+  "cliVersion": "1.15.3",
   "sha": "a33622a2f810ee4cea39824cb1a7ca34b355a917d4224025df50d77dd74f0b3a"
 }

package/package.json

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

package/assets/skills/test-organization-policy/SKILL.md

@@ -1,88 +0,0 @@
----
-name: test-organization-policy
-description: Expert test-suite organization - directory structure by test type and domain, mirrored source paths, file naming conventions, and fixture/helper/factory placement. Use when creating, moving, or renaming test files, scaffolding or restructuring a test suite, or deciding where a new test lives - never dump tests flat into a single tests/ folder.
----
-
-# Test Organization Policy (Senior Engineering Standards)
-
-## Activation Scope
-
-- Apply whenever a test file is created, moved, or renamed, and whenever a test suite is scaffolded or restructured.
-- Owns test-suite layout: directory structure, subfolders, file naming, and placement of fixtures, helpers, factories, and mocks.
-- Test strategy, coverage, determinism, and mocking discipline live in testing-policy; compose with it, never restate it.
-
----
-
-## Core Principle
-
-- A test suite is navigable code: anyone must find the tests for a module in seconds from the module's path alone, and find the module from its test's path.
-- Never dump test files flat into a single tests/ folder. Flat suites hide coverage gaps, cause name collisions, and stop scaling past a handful of files.
-- Organize from the first test file. Structure is cheapest at file creation and most expensive after the folder is a mess.
-
----
-
-## Framework Convention First
-
-- Every ecosystem has an established convention; it beats any custom layout:
-  - JS/TS (Vitest, Jest, Bun): colocated `*.test.ts` next to the source file, a `__tests__/` folder per directory, or a mirrored `tests/` tree - follow whichever the repo already uses.
-  - Python (pytest): a `tests/` package mirroring the source package; shared fixtures in `conftest.py` at the narrowest directory that covers their users.
-  - Go: `_test.go` colocated in the same package (mandated by the toolchain); black-box tests use the `_test` package suffix.
-  - Rust: unit tests in `#[cfg(test)] mod tests` inside the module; integration tests as separate files under the crate-root `tests/`.
-  - Java/Kotlin: `src/test/<lang>/` mirroring the `src/main/<lang>/` package path exactly.
-- In an existing repo, detect the established layout and extend it; never introduce a second competing layout. Migrations to a better layout are proposed explicitly, not done by stealth.
-
----
-
-## Structure by Test Type, Then by Domain
-
-- When more than one test type exists, separate types at the top level - they differ in speed, dependencies, and CI stage:
-
-  ```text
-  tests/
-    unit/          fast, isolated, no I/O
-    integration/   module boundaries, DB, contracts
-    e2e/           critical user flows only
-    fixtures/      shared static data
-    helpers/       shared builders, factories, fakes
-  ```
-
-- Inside each type, mirror the source tree: tests for `src/<domain>/<module>` live at `tests/<type>/<domain>/<module>.<suffix>`.
-- Group e2e tests by user flow (e.g. `e2e/checkout/`), not by source module - flows cross modules.
-- Default to one test file per module under test; split a large file by scenario, never by arbitrary size cuts.
-- Keep the test runner's discovery config (`testMatch`, `testpaths`, includes) in sync with the layout; a test the runner cannot find is dead code.
-
----
-
-## Naming Conventions
-
-- Test file name = module under test + the framework's suffix: `parser.test.ts`, `test_parser.py`, `parser_test.go`.
-- When splitting by scenario, encode the scenario in the name: `parser.errors.test.ts`, `auth.session-expiry.test.ts`.
-- Suite and case names describe behavior, not implementation (naming-by-behavior rules live in testing-policy).
-- Forbidden names: `test1`, `misc`, `temp`, `new`, `utils-tests`, or any name that does not identify what is verified.
-
----
-
-## Shared Test Code Placement
-
-- Fixtures (static data), factories/builders (object construction), helpers (setup/assertion logic), and fakes each get their own folder; do not mix them in one grab-bag file.
-- Place shared test code at the narrowest scope that covers its users; promote it upward only when a second consumer appears (same reuse rule as production code).
-- Test helpers are production code: deduplicate, name well, and review them like any other module.
-- Never import from another test file; extract the shared piece into a helper module instead.
-- Large fixtures live as data files under `fixtures/`, named after the scenario they encode, not inlined into test bodies.
-
----
-
-## Scaling & Maintenance
-
-- When adding a test to an existing flat or misplaced suite: place the new test correctly and surface the layout debt; do not extend the mess to match it.
-- Layout migrations are pure moves: never change test logic in the same commit as a file move (atomic-commit rule in git-policy).
-- After any move, run the affected suite to prove discovery still works, and delete emptied folders.
-- If two layouts coexist after a partial migration, finish the migration or document the boundary; a half-migrated suite is worse than either layout.
-
----
-
-## Decision Rule: Colocated vs Centralized
-
-- Colocated tests (next to source) fit unit tests in ecosystems that idiomatically support it (JS/TS, Go, Rust) - shortest navigation distance, moves with the code.
-- A centralized `tests/` tree fits integration/e2e tests, packages that must exclude tests from the published artifact, and ecosystems whose tooling expects it (Python, Java).
-- Mixing is fine when each side follows its rule (e.g. colocated unit + centralized integration); mixing within the same test type is not.

package/assets/skills/test-organization-policy/skill.json

@@ -1,8 +0,0 @@
-{
-  "name": "test-organization-policy",
-  "version": "1.0.0",
-  "provider": "FJRG2007/enigma",
-  "description": "Expert test-suite organization: structure by test type and domain, mirrored source paths, naming conventions, and fixture/helper placement.",
-  "cliVersion": "1.15.2",
-  "sha": "09184beb8e423efd26fce0221cd374d41b6ba0bb3d223d7edce250d9d978767e"
-}