oh-my-customcodex 0.5.18 → 0.5.19

package/dist/cli/index.js

@@ -3091,7 +3091,7 @@ var init_package = __esm(() => {
     workspaces: [
       "packages/*"
     ],
-    version: "0.5.18",
+    version: "0.5.19",
     requiresCC: ">=2.1.121",
     claudeCode: {
       minimumVersion: "2.1.121",

package/dist/index.js

@@ -2316,7 +2316,7 @@ var package_default = {
   workspaces: [
     "packages/*"
   ],
-  version: "0.5.18",
+  version: "0.5.19",
   requiresCC: ">=2.1.121",
   claudeCode: {
     minimumVersion: "2.1.121",

package/package.json

@@ -3,7 +3,7 @@
   "workspaces": [
     "packages/*"
   ],
-  "version": "0.5.18",
+  "version": "0.5.19",
   "requiresCC": ">=2.1.121",
   "claudeCode": {
     "minimumVersion": "2.1.121",

package/templates/.claude/rules/MUST-completion-verification.md

@@ -85,8 +85,10 @@ Before invoking or registering generated workflow code, run a Tier-1 sanity pass
 
 1. Search for unresolved placeholders, malformed identifiers, and known dead-line patterns.
 2. Assemble the exact script body before execution; do not concatenate facts or guardrails after the call starts.
-3. Run the language parser or the narrowest no-side-effect syntax check available.
-4. If syntax validation is unavailable, read the generated body back and perform a focused self-review before launch.
+3. For compound shell verification or release gates, start the script with `set -euo pipefail`; `set -o pipefail` alone does not stop later sequential gates after an earlier command fails.
+4. For zsh/bash snippets, avoid reserved or special variable names such as `status`, `path`, and `argv`; use `run_status`, `cmd_path`, `args`, or similarly specific names.
+5. Run the language parser or the narrowest no-side-effect syntax check available.
+6. If syntax validation is unavailable, read the generated body back and perform a focused self-review before launch.
 
 This check is mandatory for workflow scripts that will run automation, mutate GitHub state, or gate a release.
 

package/templates/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.5.18",
+  "version": "0.5.19",
   "requiresCC": ">=2.1.121",
   "claudeCode": {
     "minimumVersion": "2.1.121",

package/templates/workflows/auto-dev.yaml

@@ -126,6 +126,11 @@ steps:
       - If a scoped issue is added or materially changed after verify-build starts, reset this phase and re-run the full verify-build gate for the new aggregate scope.
       - Do not proceed to release from a verify-build result collected before the latest scoped implementation change.
 
+      Shell execution discipline:
+      - Run compound verification commands under `set -euo pipefail` so lint, typecheck, tests, and build halt on the first failed gate.
+      - Do not rely on `set -o pipefail` alone for sequential verification chains.
+      - Avoid reserved shell variable names in polling or status snippets (`status`, `path`, `argv`); use `run_status`, `cmd_path`, or `args` instead.
+
       For Node/Bun projects:
       1. Run `bun install` and halt on lockfile drift.
       2. Run `bun run lint` when available.