oh-my-customcode 0.168.0 → 0.170.0

package/README.md

@@ -213,7 +213,7 @@ All commands are invoked inside the Claude Code conversation.
 | Priority | Count | Purpose |
 |----------|-------|---------|
 | **MUST** | 14 | Safety, permissions, agent design, identification, orchestration, verification, completion, enforcement |
-| **SHOULD** | 6 | Interaction, error handling, memory, HUD, ecomode, ontology routing |
+| **SHOULD** | 8 | Interaction, error handling, memory, HUD, ecomode, ontology routing, wiki sync, verification ladder |
 | **MAY** | 1 | Optimization |
 
 Key rules: R010 (orchestrator never writes files), R009 (parallel execution mandatory), R017 (sauron verification before push), R020 (completion verification before declaring done), R021 (advisory-first enforcement model).
@@ -271,7 +271,7 @@ your-project/
 ├── .claude/
 │   ├── agents/                 # 49 agent definitions
 │   ├── skills/                 # 116 skill modules
-│   ├── rules/                  # 22 governance rules (R000-R021)
+│   ├── rules/                  # 23 governance rules (R000-R023)
 │   ├── hooks/                  # 15 lifecycle hook scripts
 │   ├── schemas/                # Tool input validation schemas
 │   ├── specs/                  # Extracted canonical specs

package/dist/cli/index.js

@@ -241,7 +241,7 @@ var init_package = __esm(() => {
     workspaces: [
       "packages/*"
     ],
-    version: "0.168.0",
+    version: "0.170.0",
     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: "0.168.0",
+  version: "0.170.0",
   description: "Batteries-included agent harness for Claude Code",
   type: "module",
   bin: {

package/package.json

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

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

@@ -90,7 +90,7 @@
             "command": "bash .claude/hooks/scripts/rtk-intercept.sh"
           }
         ],
-        "description": "RTK auto-intercept — transparently rewrites CLI commands through RTK proxy when available (R015 advisory)"
+        "description": "RTK auto-intercept — transparently rewrites CLI commands through RTK proxy when available (R013 advisory)"
       },
       {
         "matcher": "tool == \"Bash\" && tool_input.command matches \"git (reset|clean|checkout|restore|switch|rebase|merge)\"",

package/templates/.claude/rules/MUST-agent-design.md

@@ -356,6 +356,8 @@ description: Brief desc    # One-line summary
 
 Key optional fields: `scope`, `context`, `version`, `effort`, `model`, `agent`, `hooks`, `paths`, `shell`, `allowed-tools`, `keep-coding-instructions`. Skill `effort` takes precedence over agent `effort` when both specified. See full optional fields via Read tool.
 
+> **v2.1.163+**: In skill `command` bodies, use `\$` to emit a literal `$` before a number (e.g., `\$1`) — previously ambiguous with shell variable expansion. Relevant when authoring skills with `shell:` or inline command steps that include dollar signs not intended as variables.
+
 <!-- DETAIL: Skill Optional Fields (full yaml block)
 ```yaml
 scope: core                # core | harness | package (default: core)

package/templates/.claude/rules/MUST-enforcement-policy.md

@@ -17,6 +17,8 @@ oh-my-customcode uses an **advisory-first enforcement model**. Most rules are en
 | Advisory (proactive) | UserPromptSubmit hook | R007, R008 (`r007-r008-drift-advisor.sh`, #1229) | Reads last assistant turn; emits stderr advisory before next response if header/prefix absent. Complements retroactive Stop-hook (`session-reflection.sh`, #1190). |
 | Prompt-based | CLAUDE.md + rules/ + PostCompact | All MUST rules | Behavioral guidance in context |
 
+> **v2.1.163+**: Stop and SubagentStop hooks can return `hookSpecificOutput.additionalContext` (JSON) to feed structured feedback back into Claude's context without triggering a hook error label. This enables advisory-style enforcement via Stop/SubagentStop hooks (e.g., `session-reflection.sh`, omcustom-loop SubagentStop) to pass richer context — replacing plain stderr text — without disrupting the turn continuation behavior that advisory-first enforcement relies on.
+
 ## Why Advisory-First
 
 1. **Agent flexibility**: Hard blocks can trap agents in unrecoverable states

package/templates/.claude/skills/pipeline/labels.md

@@ -41,6 +41,13 @@ An issue is eligible for `docs-only` compression mode if its labels include at l
 If ALL scoped issues are compression-eligible AND scope size ≤ 3, the pipeline MAY use
 `compression_mode=docs-only` (skip professor-triage / release-plan / deep-plan / deep-verify skill spawns).
 
+An issue is eligible for `lite` (Tier 2) compression mode if its labels include at least one of:
+`documentation`, `automated`, `claude-code-release`, `feedback`, `professor`, `enhancement`, `improvement`
+
+If ALL scoped issues carry at least one lite-eligible label AND scope size ≤ 7 AND no issue carries
+`breaking-change` or `decision-needed`, the pipeline MAY use `compression_mode=lite`
+(integrated analysis replaces heavy skill spawns for triage/plan/deep-plan/deep-verify; implement and verify-build execute normally).
+
 ## Lifecycle Labels (set by `implement` step)
 
 | Transition | Action |

package/templates/.claude/skills/pipeline/workflows/auto-dev.yaml

@@ -137,7 +137,7 @@ steps:
       Evaluate ONLY if docs-only NOT met. Conditions (ALL must hold):
       1. scope size ≤ 7
       2. ALL scoped issues are low-risk: for EVERY issue,
-         labels ∩ {documentation, automated, claude-code-release, feedback, professor, enhancement} ≠ ∅
+         labels ∩ {documentation, automated, claude-code-release, feedback, professor, enhancement, improvement} ≠ ∅
       3. NO scoped issue carries a breaking-change or decision-needed label
       4. No code logic change is expected — work is docs/rule/skill/config/script-centric
          (verify against each issue body; if any issue implies application code logic change, FAIL the lite check)
@@ -201,6 +201,7 @@ steps:
       - Issues whose prerequisites failed in-run MUST be skipped (log reason)
       - No direct orchestrator writes (R010)
       - All Agent tool calls MUST pass mode: "bypassPermissions" to prevent permission prompts during unattended execution
+      - Mid-run scope additions (a new issue added via user interrupt AFTER implement began) MUST re-enter the verify-build gate before release — do NOT let a late-added scope item ride to release on a prior verify-build pass. Critical for code changes; benign for docs-only (#1301).
 
 
       ## Sensitive Path Handling (CC v2.1.121+)

package/templates/manifest.json

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

package/templates/workflows/auto-dev.yaml

@@ -137,7 +137,7 @@ steps:
       Evaluate ONLY if docs-only NOT met. Conditions (ALL must hold):
       1. scope size ≤ 7
       2. ALL scoped issues are low-risk: for EVERY issue,
-         labels ∩ {documentation, automated, claude-code-release, feedback, professor, enhancement} ≠ ∅
+         labels ∩ {documentation, automated, claude-code-release, feedback, professor, enhancement, improvement} ≠ ∅
       3. NO scoped issue carries a breaking-change or decision-needed label
       4. No code logic change is expected — work is docs/rule/skill/config/script-centric
          (verify against each issue body; if any issue implies application code logic change, FAIL the lite check)
@@ -201,6 +201,7 @@ steps:
       - Issues whose prerequisites failed in-run MUST be skipped (log reason)
       - No direct orchestrator writes (R010)
       - All Agent tool calls MUST pass mode: "bypassPermissions" to prevent permission prompts during unattended execution
+      - Mid-run scope additions (a new issue added via user interrupt AFTER implement began) MUST re-enter the verify-build gate before release — do NOT let a late-added scope item ride to release on a prior verify-build pass. Critical for code changes; benign for docs-only (#1301).
 
 
       ## Sensitive Path Handling (CC v2.1.121+)