oh-my-customcode 1.0.11 → 1.0.13

package/dist/cli/index.js

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

package/package.json

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

package/templates/.claude/rules/MAY-optimization.md

@@ -14,6 +14,10 @@
 
 > **Platform tool variants (#1327 찐빠 #5)**: tool names differ by platform — e.g., macOS lacks GNU `timeout` (use `gtimeout` from coreutils). Confirm platform-specific tool availability before use.
 
+> **Sandbox/container tool gaps (#1401 찐빠 #4)**: `curl`, `wget`, `nc` 등 공통 CLI 도구는 샌드박스·컨테이너 환경에서 미설치일 수 있다. HTTP 요청에는 `WebFetch` 도구를 우선 사용하고, CLI 도구 사용 전 `command -v <tool>` 으로 가용성을 사전 확인한다.
+
+> **Shell output parsing — use Python, not read/grep (#1401 찐빠 #3)**: adb bounds rect, 좌표쌍, JSON 분할 등 구조화된 출력 파싱은 `read`+`grep -o` 파이프라인 대신 Python (`python3 -c "..."`) 을 사용한다. `read`+`grep -o` 조합은 공백 차이에 취약해 헛값을 산출한다. SSH 원격 `bash -c` 인자에 소괄호 포함 금지 — `ssh host "cmd; cmd2"` 형식 사용.
+
 ### Capability-Aware Tool Scheduling
 
 When dispatching parallel tool calls, consider per-tool capabilities to optimize scheduling:

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

@@ -110,3 +110,17 @@ Reference issue: #1096.
 | 1단어 응답 ("네"/"OK") | YES |
 
 Reference issues: #1188 item #2, #1198 item #2.
+
+### External-Project / Debugging Session Vigilance
+
+R007 헤더 누락은 외부 프로젝트 디버깅, SSH 진단, 배포 작업 등 기술적 몰입 세션에서 가장 자주 발생한다. 이 규칙은 프로젝트 종류와 무관하게 모든 상황에 적용된다.
+
+| 세션 유형 | R007 헤더 |
+|-----------|-----------|
+| oh-my-customcode 작업 | 필수 |
+| 외부 프로젝트 디버깅 | **동일하게 필수** |
+| SSH / 배포 / 인프라 작업 | **동일하게 필수** |
+
+기술적 몰입 중 헤더 누락이 반복될 경우 즉시 re-anchor: 다음 응답에 `┌─ Agent:` 풀 헤더를 붙이고 이후 계속 유지한다.
+
+Reference issue: #1401.

package/templates/.claude/rules/MUST-tool-identification.md

@@ -161,3 +161,15 @@ Reference issue: #1096.
 ```
 
 Reference issues: #1188 item #3, #1198 item #3.
+
+### External-Project / Debugging Session Vigilance
+
+R007 헤더와 마찬가지로, R008 prefix 누락도 외부 프로젝트 디버깅·배포 세션에서 가장 자주 발생한다. R007/R008은 세트로 함께 자가 점검한다.
+
+| 세션 유형 | R008 prefix |
+|-----------|-------------|
+| oh-my-customcode 작업 | 필수 |
+| 외부 프로젝트 디버깅 | **동일하게 필수** |
+| SSH / 배포 / 인프라 작업 | **동일하게 필수** |
+
+Reference issue: #1401.

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

@@ -315,15 +315,30 @@ steps:
          - Previous tag is ahead of source version (e.g., tag v0.136.1, package.json 0.136.0): use next available skip-version (0.136.2)
 
       2. Release notes via omcustom-release-notes skill
-      3. Delegate to mgr-gitnerd:
-         - git tag + push
-         - gh release create
-      4. Close milestone
-      5. Close verify-ready issues with "Fixed in v{version}"
+      3. Adapt release mechanism to project (determines how steps 3-5 execute):
+         - npm project with auto-tag.yml (this repo — release/v* PR pattern):
+           a. mgr-gitnerd creates release/v{NEW} branch from develop with the version-bump commit
+           b. mgr-gitnerd creates PR: gh pr create --base develop --head release/v{NEW} --title "chore(release): bump to v{NEW}"
+           c. mgr-gitnerd merges PR (admin merge required due to branch protection)
+           d. DO NOT manually git tag or gh release create.
+              auto-tag.yml fires on release/v* PR merge → creates tag → closes linked issues → closes milestone → deletes release branch.
+              release.yml fires on the tag → npm publish + GitHub Release creation.
+           Milestone close and issue close are handled downstream by auto-tag.yml — do NOT close them manually.
+         - Non-npm / no auto-tag.yml:
+           mgr-gitnerd: git tag v{NEW} && git push origin v{NEW}
+           mgr-gitnerd: gh release create v{NEW} (with release notes)
+           Then proceed with items 4-5 below.
+
+      4. Close milestone (non-auto-tag projects only — auto-tag.yml handles this for npm+PR projects):
+         gh api repos/{owner}/{repo}/milestones/{n} --method PATCH --field state=closed
+
+      5. Close verify-ready issues (non-auto-tag projects only — auto-tag.yml handles this for npm+PR projects):
+         gh issue close {n} --comment "Fixed in v{version}"
          Label needs-review issues as "Deferred from v{version}"
-      6. Adapt release mechanism to project:
-         - npm project: PR + merge + npm publish verification
-         - Non-npm: direct tag on main (trunk-based)
+
+      6. npm publish verification (npm projects only):
+         After auto-tag.yml + release.yml complete (verified in ci-check step):
+         npm view <pkg> version → must equal v{NEW}
     description: "Git tag + GitHub Release + close milestone/issues (with mandatory version sync verification)"
     depends_on: deep-verify
 
@@ -334,11 +349,19 @@ steps:
       1. Check if .github/workflows/ has CI workflows
          If NOT: skip with "No CI configured. Skipping." and continue.
       2. If CI exists:
-         - gh run list --limit 5
+         - gh run list --limit 10
          - Wait for runs triggered by the new tag/push
          - If failures: diagnose, fix, re-verify
-      3. For npm projects: verify npm publish succeeded (npm view <pkg> version)
-      4. Report final CI status.
+      3. For npm projects with auto-tag.yml: MANDATORY additional check:
+         gh run list --workflow auto-tag.yml --limit 1 --json conclusion,displayTitle
+         → conclusion MUST be "success" before declaring release complete.
+         If auto-tag.yml concluded "failure": diagnose root cause. Do NOT retry with manual git tag.
+         Common causes:
+           - Tag already exists (manual tag pushed before PR merge — fix: remove manual tag from release delegation)
+           - Branch naming mismatch (branch not matching release/v* pattern — fix: verify branch name)
+         Report: "[ci-check] auto-tag.yml: {conclusion}" as mandatory line in CI status report.
+      4. For npm projects: verify npm publish succeeded (npm view <pkg> version)
+      5. Report final CI status.
     description: "Post-release CI verification and fix loop"
     depends_on: release
 

package/templates/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.0.11",
+  "version": "1.0.13",
   "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

@@ -315,15 +315,30 @@ steps:
          - Previous tag is ahead of source version (e.g., tag v0.136.1, package.json 0.136.0): use next available skip-version (0.136.2)
 
       2. Release notes via omcustom-release-notes skill
-      3. Delegate to mgr-gitnerd:
-         - git tag + push
-         - gh release create
-      4. Close milestone
-      5. Close verify-ready issues with "Fixed in v{version}"
+      3. Adapt release mechanism to project (determines how steps 3-5 execute):
+         - npm project with auto-tag.yml (this repo — release/v* PR pattern):
+           a. mgr-gitnerd creates release/v{NEW} branch from develop with the version-bump commit
+           b. mgr-gitnerd creates PR: gh pr create --base develop --head release/v{NEW} --title "chore(release): bump to v{NEW}"
+           c. mgr-gitnerd merges PR (admin merge required due to branch protection)
+           d. DO NOT manually git tag or gh release create.
+              auto-tag.yml fires on release/v* PR merge → creates tag → closes linked issues → closes milestone → deletes release branch.
+              release.yml fires on the tag → npm publish + GitHub Release creation.
+           Milestone close and issue close are handled downstream by auto-tag.yml — do NOT close them manually.
+         - Non-npm / no auto-tag.yml:
+           mgr-gitnerd: git tag v{NEW} && git push origin v{NEW}
+           mgr-gitnerd: gh release create v{NEW} (with release notes)
+           Then proceed with items 4-5 below.
+
+      4. Close milestone (non-auto-tag projects only — auto-tag.yml handles this for npm+PR projects):
+         gh api repos/{owner}/{repo}/milestones/{n} --method PATCH --field state=closed
+
+      5. Close verify-ready issues (non-auto-tag projects only — auto-tag.yml handles this for npm+PR projects):
+         gh issue close {n} --comment "Fixed in v{version}"
          Label needs-review issues as "Deferred from v{version}"
-      6. Adapt release mechanism to project:
-         - npm project: PR + merge + npm publish verification
-         - Non-npm: direct tag on main (trunk-based)
+
+      6. npm publish verification (npm projects only):
+         After auto-tag.yml + release.yml complete (verified in ci-check step):
+         npm view <pkg> version → must equal v{NEW}
     description: "Git tag + GitHub Release + close milestone/issues (with mandatory version sync verification)"
     depends_on: deep-verify
 
@@ -334,11 +349,19 @@ steps:
       1. Check if .github/workflows/ has CI workflows
          If NOT: skip with "No CI configured. Skipping." and continue.
       2. If CI exists:
-         - gh run list --limit 5
+         - gh run list --limit 10
          - Wait for runs triggered by the new tag/push
          - If failures: diagnose, fix, re-verify
-      3. For npm projects: verify npm publish succeeded (npm view <pkg> version)
-      4. Report final CI status.
+      3. For npm projects with auto-tag.yml: MANDATORY additional check:
+         gh run list --workflow auto-tag.yml --limit 1 --json conclusion,displayTitle
+         → conclusion MUST be "success" before declaring release complete.
+         If auto-tag.yml concluded "failure": diagnose root cause. Do NOT retry with manual git tag.
+         Common causes:
+           - Tag already exists (manual tag pushed before PR merge — fix: remove manual tag from release delegation)
+           - Branch naming mismatch (branch not matching release/v* pattern — fix: verify branch name)
+         Report: "[ci-check] auto-tag.yml: {conclusion}" as mandatory line in CI status report.
+      4. For npm projects: verify npm publish succeeded (npm view <pkg> version)
+      5. Report final CI status.
     description: "Post-release CI verification and fix loop"
     depends_on: release