genesis-compiler 1.3.0 → 1.3.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "genesis-compiler",
-  "version": "1.3.0",
+  "version": "1.3.2",
   "type": "module",
   "description": "An agent-independent prompt, multi-language code-index, cleanup, and verification companion with project agent guidance.",
   "repository": {

package/plugins/genesis/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "genesis",
-  "version": "1.3.0",
+  "version": "1.3.2",
   "description": "Makes Codex aware of optional Genesis adoption for existing projects.",
   "author": {
     "name": "Mobily Enterprises"

package/skills/genesis-deslop/SKILL.md

@@ -8,12 +8,29 @@ description: Deslop committed work through an explicit behavior-preserving clean
 Review and simplify committed work without changing product behavior. Deslop is
 explicit: never run it merely because implementation finished.
 
-When this repository is Genesis itself or has `genesis-compiler` installed
-locally, invoke every Genesis CLI operation through the project-pinned package:
-`npm exec --no -- genesis <arguments>`. This runs without fetching another
-package. Otherwise use `genesis <arguments>` only when that executable is
-already available on `PATH`. Never install or update Genesis merely to satisfy
-a workflow instruction.
+Resolve the invocation before running the first Genesis operation. Do not use a
+Genesis operation or `genesis --version` as an availability probe.
+
+1. Read the repository-root `package.json`. Treat Genesis as project-pinned only
+   when that manifest's `name` is `genesis-compiler`, or its `dependencies`,
+   `devDependencies`, or `optionalDependencies` contain the exact
+   `genesis-compiler` key.
+2. For a project-pinned repository, invoke every Genesis CLI operation with
+   `npm exec --no -- genesis <arguments>`. This runs without fetching another
+   package. If the declared package is not installed, report that the project's
+   dependencies are not prepared; do not fall back to another Genesis version.
+3. Otherwise, do not try `npm exec`. Run `command -v genesis` (or the current
+   shell's equivalent `PATH` lookup). When it resolves an executable, invoke
+   `genesis <arguments>` directly.
+4. When neither source is available, stop and report that Genesis is
+   unavailable. Never install or update Genesis merely to satisfy a workflow
+   instruction.
+
+Successful invocation resolution is routine. Do not narrate whether Genesis is
+project-pinned or on `PATH`, and never describe direct `PATH` use as a fallback.
+Mention how the invocation was selected only when resolution fails or the user
+explicitly asks. This does not suppress an otherwise-required work update about
+using Genesis; keep that update about the project work, not executable selection.
 
 ## Load the effective project instructions once
 

package/skills/genesis-project/SKILL.md

@@ -25,12 +25,29 @@ one exact investigation.
 
 ## Run Genesis commands
 
-When this repository is Genesis itself or has `genesis-compiler` installed
-locally, invoke every Genesis CLI operation through the project-pinned package:
-`npm exec --no -- genesis <arguments>`. This runs without fetching another
-package. Otherwise use `genesis <arguments>` only when that executable is
-already available on `PATH`. Never install or update Genesis merely to satisfy
-a workflow instruction.
+Resolve the invocation before running the first Genesis operation. Do not use a
+Genesis operation or `genesis --version` as an availability probe.
+
+1. Read the repository-root `package.json`. Treat Genesis as project-pinned only
+   when that manifest's `name` is `genesis-compiler`, or its `dependencies`,
+   `devDependencies`, or `optionalDependencies` contain the exact
+   `genesis-compiler` key.
+2. For a project-pinned repository, invoke every Genesis CLI operation with
+   `npm exec --no -- genesis <arguments>`. This runs without fetching another
+   package. If the declared package is not installed, report that the project's
+   dependencies are not prepared; do not fall back to another Genesis version.
+3. Otherwise, do not try `npm exec`. Run `command -v genesis` (or the current
+   shell's equivalent `PATH` lookup). When it resolves an executable, invoke
+   `genesis <arguments>` directly.
+4. When neither source is available, stop and report that Genesis is
+   unavailable. Never install or update Genesis merely to satisfy a workflow
+   instruction.
+
+Successful invocation resolution is routine. Do not narrate whether Genesis is
+project-pinned or on `PATH`, and never describe direct `PATH` use as a fallback.
+Mention how the invocation was selected only when resolution fails or the user
+explicitly asks. This does not suppress an otherwise-required work update about
+using Genesis; keep that update about the project work, not executable selection.
 
 ## Resolve explicit technology choices