oh-my-customcode 1.1.16 → 1.1.17

package/dist/cli/index.js

@@ -241,7 +241,7 @@ var init_package = __esm(() => {
     workspaces: [
       "packages/*"
     ],
-    version: "1.1.16",
+    version: "1.1.17",
     description: "Batteries-included agent harness for Claude Code",
     type: "module",
     bin: {

package/dist/index.js

@@ -2031,7 +2031,7 @@ var package_default = {
   workspaces: [
     "packages/*"
   ],
-  version: "1.1.16",
+  version: "1.1.17",
   description: "Batteries-included agent harness for Claude Code",
   type: "module",
   bin: {

package/package.json

@@ -3,7 +3,7 @@
   "workspaces": [
     "packages/*"
   ],
-  "version": "1.1.16",
+  "version": "1.1.17",
   "description": "Batteries-included agent harness for Claude Code",
   "type": "module",
   "bin": {

package/templates/.claude/hooks/hooks.json

@@ -222,7 +222,7 @@
         "matcher": "*",
         "hooks": [
           {
-            "type": "prompt",
+            "type": "command",
             "command": "bash .claude/hooks/scripts/session-autofix-prompt.sh"
           }
         ],

package/templates/.claude/hooks/scripts/stage-blocker.sh

@@ -1,15 +1,15 @@
 #!/bin/bash
 # Stage-blocking hook: blocks Write/Edit in non-implement stages
 # Mutual Exclusion: This hook is mutually exclusive with autonomous mode (R010).
-# When /tmp/.claude-dev-stage exists, autonomous mode cannot be activated.
+# When /tmp/.claude-dev-stage-$PPID exists, autonomous mode cannot be activated.
 # When /tmp/.claude-autonomous-$PPID exists, /structured-dev-cycle should not be started.
 # See: MUST-orchestrator-coordination.md "Autonomous Execution Mode" section.
-if [ -f /tmp/.claude-dev-stage ]; then
-  stage=$(cat /tmp/.claude-dev-stage | tr -d '[:space:]')
+if [ -f /tmp/.claude-dev-stage-$PPID ]; then
+  stage=$(cat /tmp/.claude-dev-stage-$PPID | tr -d '[:space:]')
   if [ -z "$stage" ]; then exit 0; fi
   case "$stage" in
     plan|verify-plan|verify-impl|compound|done)
-      echo "⛔ BLOCKED: Write/Edit disabled in '$stage' stage. Only allowed during 'implement' stage. Use 'echo implement > /tmp/.claude-dev-stage' to transition."
+      echo "⛔ BLOCKED: Write/Edit disabled in '$stage' stage. Only allowed during 'implement' stage. Use 'echo implement > /tmp/.claude-dev-stage-$PPID' to transition."
       exit 2
       ;;
   esac

package/templates/.claude/hooks/scripts/task-state-precompact.sh

@@ -20,7 +20,7 @@ collect_state() {
   [ -f "/tmp/.claude-autonomous-$PPID" ] && autonomous="true"
 
   # Dev stage (structured-dev-cycle)
-  [ -f "/tmp/.claude-dev-stage" ] && dev_stage=$(cat "/tmp/.claude-dev-stage" 2>/dev/null)
+  [ -f "/tmp/.claude-dev-stage-$PPID" ] && dev_stage=$(cat "/tmp/.claude-dev-stage-$PPID" 2>/dev/null)
 
   # Tool call counter
   [ -f "/tmp/claude-tool-count-$PPID" ] && tool_count=$(cat "/tmp/claude-tool-count-$PPID" 2>/dev/null)

package/templates/.claude/rules/MUST-orchestrator-coordination.md

@@ -179,7 +179,7 @@ When the user explicitly signals full-delegation intent, the orchestrator operat
 ### Activation Protocol
 
 1. User gives explicit autonomous signal (not inferred from task complexity)
-2. Verify stage-blocker is NOT active (`/tmp/.claude-dev-stage` must not exist)
+2. Verify stage-blocker is NOT active (`/tmp/.claude-dev-stage-$PPID` must not exist)
 3. Create marker: `echo 1 > /tmp/.claude-autonomous-$PPID`
 4. Announce: `[Autonomous Mode] Activated for current task scope`
 
@@ -211,7 +211,7 @@ When the user explicitly signals full-delegation intent, the orchestrator operat
 ### Mutual Exclusion
 
 - Autonomous mode and `/structured-dev-cycle` (stage-blocker) are **mutually exclusive**
-- If `/tmp/.claude-dev-stage` exists → autonomous mode CANNOT be activated
+- If `/tmp/.claude-dev-stage-$PPID` exists → autonomous mode CANNOT be activated
 - If autonomous mode is active → `/structured-dev-cycle` should not be started
 
 ### Self-Check
@@ -225,7 +225,7 @@ When the user explicitly signals full-delegation intent, the orchestrator operat
 ║     NO  → Do NOT activate                                        ║
 ║                                                                   ║
 ║  2. Is stage-blocker inactive?                                   ║
-║     (/tmp/.claude-dev-stage does NOT exist)                      ║
+║     (/tmp/.claude-dev-stage-$PPID does NOT exist)                      ║
 ║     YES → Continue                                               ║
 ║     NO  → Cannot activate (mutually exclusive)                   ║
 ║                                                                   ║

package/templates/.claude/skills/profile/SKILL.md

@@ -70,43 +70,11 @@ Profile: web-app
   Disable: codex, ralph-wiggum, agent-sdk-dev, ...
 ```
 
-6. Apply changes via /tmp script:
+6. Apply changes via direct Edit on `~/.claude/settings.json` (`mode: "bypassPermissions"`, CC v2.1.121+):
+   - Read `~/.claude/settings.json`, merge the computed diff into `enabledPlugins` (set enabled plugins to `true`, disabled plugins to `false`), then Write the updated JSON back.
 
-```bash
-cat > /tmp/profile-apply-$$.sh << 'APPLY'
-#!/usr/bin/env python3
-import json, sys
-
-settings_path = "/Users/<user>/.claude/settings.json"  # resolve from $HOME
-with open(settings_path) as f:
-    settings = json.load(f)
-
-profile_path = ".claude/profiles/<name>.json"
-with open(profile_path) as f:
-    profile = json.load(f)
-
-for plugin in profile["plugins"]["enabled"]:
-    settings.setdefault("enabledPlugins", {})[plugin] = True
-for plugin in profile["plugins"]["disabled"]:
-    settings.setdefault("enabledPlugins", {})[plugin] = False
-
-with open(settings_path, "w") as f:
-    json.dump(settings, f, indent=2)
-    f.write("\n")
-
-print("Settings updated.")
-APPLY
-python3 /tmp/profile-apply-$$.sh
-```
-
-7. Write active marker via /tmp script:
-
-```bash
-cat > /tmp/profile-marker-$$.sh << 'MARKER'
-echo "<name>" > .claude/profiles/.active
-MARKER
-bash /tmp/profile-marker-$$.sh
-```
+7. Write active marker via direct Write on `.claude/profiles/.active` (`mode: "bypassPermissions"`):
+   - Write the profile `<name>` as plain text content to `.claude/profiles/.active`.
 
 8. Confirm:
 
@@ -118,7 +86,7 @@ IMPORTANT: Restart this Claude Code session for plugin changes to take effect.
 
 ## Workflow: `/profile reset`
 
-1. Remove `.claude/profiles/.active` marker via /tmp script
+1. Remove `.claude/profiles/.active` marker via direct `Bash: /bin/rm .claude/profiles/.active` (`mode: "bypassPermissions"`)
 2. Print: `[Done] Profile marker removed. Full plugin set will be active after restart.`
 3. Note: does NOT revert `~/.claude/settings.json` — user should re-run `/profile load <other>` or manually restore
 
@@ -127,7 +95,7 @@ IMPORTANT: Restart this Claude Code session for plugin changes to take effect.
 - Profile changes to `~/.claude/settings.json` take effect only after session restart
 - Profiles define a subset: plugins not listed in `enabled` or `disabled` keep their current state
 - Profile JSON `enabled`/`disabled` lists use full plugin keys: `<name>@<marketplace>` format
-- All `.claude/` writes use the /tmp bypass pattern (see Implementation rules above)
+- All `.claude/` writes use direct Write/Edit/Bash (CC v2.1.121+, no `/tmp` wrapping — see Implementation rules above)
 
 ## Manifest Profile Integration
 

package/templates/.claude/skills/structured-dev-cycle/SKILL.md

@@ -46,13 +46,13 @@ Stage state is tracked via a marker file for hook enforcement:
 
 ```bash
 # Set stage (used by orchestrator or skill)
-echo "plan" > /tmp/.claude-dev-stage
+echo "plan" > /tmp/.claude-dev-stage-$PPID
 
 # Valid stage values (all block Write/Edit except 'implement'):
 # plan, verify-plan, implement, verify-impl, compound, done
 
 # Clear stage (disable blocking)
-rm -f /tmp/.claude-dev-stage
+rm -f /tmp/.claude-dev-stage-$PPID
 ```
 
 A PreToolUse hook in `.claude/hooks/hooks.json` checks this marker and blocks Write/Edit tools during non-implementation stages.
@@ -140,7 +140,7 @@ Stage 1 (Plan) maps to Claude Code's `EnterPlanMode`. When the structured cycle
 Stage 2 (Verify Plan) and Stage 4 (Verify Implementation) can invoke the `multi-model-verification` skill for comprehensive review.
 
 ### With PreToolUse Hooks
-The stage marker file (`/tmp/.claude-dev-stage`) is read by a PreToolUse hook that enforces tool restrictions. This provides a safety net beyond instruction-based compliance.
+The stage marker file (`/tmp/.claude-dev-stage-$PPID`) is read by a PreToolUse hook that enforces tool restrictions. This provides a safety net beyond instruction-based compliance.
 
 ### With Agent Teams
 For complex tasks, Agent Teams is **preferred** when available (R018):
@@ -165,19 +165,19 @@ When Agent Teams is enabled AND task involves 3+ agents or review→fix cycles,
 
 ```bash
 # Orchestrator manages transitions:
-echo "plan" > /tmp/.claude-dev-stage           # Enter planning
-echo "verify-plan" > /tmp/.claude-dev-stage     # Enter plan verification
-echo "implement" > /tmp/.claude-dev-stage       # Enter implementation
-echo "verify-impl" > /tmp/.claude-dev-stage     # Enter impl verification
-echo "compound" > /tmp/.claude-dev-stage        # Enter compound testing
-echo "done" > /tmp/.claude-dev-stage            # Mark done
-rm -f /tmp/.claude-dev-stage                    # Clear (disable blocking)
+echo "plan" > /tmp/.claude-dev-stage-$PPID           # Enter planning
+echo "verify-plan" > /tmp/.claude-dev-stage-$PPID    # Enter plan verification
+echo "implement" > /tmp/.claude-dev-stage-$PPID      # Enter implementation
+echo "verify-impl" > /tmp/.claude-dev-stage-$PPID    # Enter impl verification
+echo "compound" > /tmp/.claude-dev-stage-$PPID       # Enter compound testing
+echo "done" > /tmp/.claude-dev-stage-$PPID           # Mark done
+rm -f /tmp/.claude-dev-stage-$PPID                   # Clear (disable blocking)
 ```
 
 ## Limitations
 
-- **Single session**: The fixed path `/tmp/.claude-dev-stage` does not support concurrent Claude Code sessions. Running multiple sessions simultaneously may cause stage state conflicts.
-- **World-writable path**: The `/tmp/` directory is accessible to all users. For multi-user environments, consider using a user-scoped path like `/tmp/.claude-dev-stage-$(id -u)`.
+- **Session scoping**: The marker path is scoped by parent PID (`/tmp/.claude-dev-stage-$PPID`), so concurrent Claude Code sessions use distinct markers and do not conflict. The reader hooks (`stage-blocker.sh`, `task-state-precompact.sh`) and the writer commands above all resolve `$PPID` to the same Claude Code process, keeping the gate consistent.
+- **World-writable path**: The `/tmp/` directory is accessible to all users. The `-$PPID` suffix isolates per-session state but does not restrict filesystem permissions; avoid storing sensitive data in the marker file.
 
 ## Permission Mode
 

package/templates/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.16",
+  "version": "1.1.17",
   "lastUpdated": "2026-07-14T00:00:00.000Z",
   "omcustomMinClaudeCode": "2.1.121",
   "omcustomMinClaudeCodeReason": "Sensitive-path direct Write/Edit on .claude/** under bypassPermissions (R010 deprecation, #1101)",