oh-my-customcode 1.0.12 → 1.0.14

package/dist/cli/index.js

@@ -241,7 +241,7 @@ var init_package = __esm(() => {
     workspaces: [
       "packages/*"
     ],
-    version: "1.0.12",
+    version: "1.0.14",
     description: "Batteries-included agent harness for Claude Code",
     type: "module",
     bin: {
@@ -294,7 +294,7 @@ var init_package = __esm(() => {
       "@types/bun": "^1.3.6",
       "@types/js-yaml": "^4.0.9",
       "@types/nodemailer": "^8.0.0",
-      "js-yaml": "^4.1.0",
+      "js-yaml": "^5.0.0",
       nodemailer: "^9.0.1",
       typescript: "^6.0.2",
       vitepress: "^1.6.4"

package/dist/index.js

@@ -2031,7 +2031,7 @@ var package_default = {
   workspaces: [
     "packages/*"
   ],
-  version: "1.0.12",
+  version: "1.0.14",
   description: "Batteries-included agent harness for Claude Code",
   type: "module",
   bin: {
@@ -2084,7 +2084,7 @@ var package_default = {
     "@types/bun": "^1.3.6",
     "@types/js-yaml": "^4.0.9",
     "@types/nodemailer": "^8.0.0",
-    "js-yaml": "^4.1.0",
+    "js-yaml": "^5.0.0",
     nodemailer: "^9.0.1",
     typescript: "^6.0.2",
     vitepress: "^1.6.4"

package/package.json

@@ -3,7 +3,7 @@
   "workspaces": [
     "packages/*"
   ],
-  "version": "1.0.12",
+  "version": "1.0.14",
   "description": "Batteries-included agent harness for Claude Code",
   "type": "module",
   "bin": {
@@ -56,7 +56,7 @@
     "@types/bun": "^1.3.6",
     "@types/js-yaml": "^4.0.9",
     "@types/nodemailer": "^8.0.0",
-    "js-yaml": "^4.1.0",
+    "js-yaml": "^5.0.0",
     "nodemailer": "^9.0.1",
     "typescript": "^6.0.2",
     "vitepress": "^1.6.4"

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

@@ -108,8 +108,17 @@ Reference issue: #1096.
 | 사용자 질문 재확인 | YES |
 | 도구 호출 없는 텍스트 응답 | YES |
 | 1단어 응답 ("네"/"OK") | YES |
+| **빈 응답 (0단어 turn 종료)** | **금지** — 헤더 누락 이전에 응답 자체가 없음 |
 
-Reference issues: #1188 item #2, #1198 item #2.
+#### 빈 응답 금지 (Empty-Response Prohibition)
+
+도구 결과를 수신한 후 응답 텍스트 없이 turn 을 종료하는 것(빈 응답, "(no content)")은 R007 위반의 극단 케이스다. 1단어 응답에도 헤더가 필수이므로 0단어 응답은 당연히 금지된다. 도구 호출 결과를 받은 직후에는 항상 최소 1줄의 진행 상태(R003 status format)와 R007 헤더를 출력한 뒤 다음 단계로 진행하거나 turn 을 마친다. 작업이 끝났으면 완료 요약을, 계속할 작업이 있으면 다음 단계 announce 를 출력한다 — 어느 경우에도 빈 turn 종료는 허용되지 않는다.
+
+| Anti-pattern | Required |
+|--------------|----------|
+| 도구 결과 수신 후 응답 텍스트 없이 turn 종료 ("(no content)") | 최소 1줄 진행 상태 + R007 헤더 출력 후 종료/계속 |
+
+Reference issues: #1188 item #2, #1198 item #2, #1409.
 
 ### External-Project / Debugging Session Vigilance
 

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.12",
+  "version": "1.0.14",
   "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