oh-my-customcode 1.1.47 → 1.1.49

package/templates/.claude/skills/agora/scripts/reviewers.sh

@@ -0,0 +1,312 @@
+#!/usr/bin/env bash
+# reviewers.sh — parallel 3-vendor adapter.
+# Spec: docs/superpowers/plans/2026-08-15-agora-anonymous-consensus-design.md §3 §11
+set -uo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+SCHEMA_PATH="$SCRIPT_DIR/response-schema.json"
+
+# Ruling 12 (controller): keep the bare binary names as defaults — `claude`
+# and `agy` are the user's shell ALIASES, not distinct binaries, and the
+# alias-appended flags below are added explicitly in invoke_vendor() because
+# aliases do not expand under non-interactive `bash script.sh` execution.
+# omx has no alias (spec §2 measured: /opt/homebrew/bin/omx), so its default
+# stays the absolute path.
+AGORA_CLAUDE_BIN="${AGORA_CLAUDE_BIN:-claude}"
+AGORA_OMX_BIN="${AGORA_OMX_BIN:-/opt/homebrew/bin/omx}"
+AGORA_AGY_BIN="${AGORA_AGY_BIN:-agy}"
+AGORA_TIMEOUT_SECS="${AGORA_TIMEOUT_SECS:-300}"
+
+# ---------------------------------------------------------------------------
+# _child_env_strip — the `env -u NAME` list that removes every AGORA_*
+# variable from a vendor CLI's environment.
+#
+# The anonymity of this process rests on the vendors and the judge never
+# reaching the sealed session material. Two guards already covered that:
+# agora.sh exports nothing of its own, and no session path is ever passed in
+# argv. Neither covers what the OPERATOR's shell exported before agora.sh
+# ever ran. Measured: with AGORA_OUTPUT_ROOT set in the invoking shell, that
+# value is inherited straight through agora.sh into every vendor CLI spawned
+# here, and the whole session tree — sealed round records included — sits one
+# glob below it. "We do not pass it" is no defence against a value that is
+# already in the environment.
+#
+# Prefix rule rather than a hardcoded name list, deliberately: a name list
+# leaks silently the day someone adds AGORA_SOMETHING_NEW, whereas the prefix
+# fails CLOSED — a new variable is stripped unless someone argues it back in.
+# Nothing outside the prefix is touched, so PATH, HOME, the vendors' own auth
+# tokens and proxy settings all survive; `env -i` would leave the CLIs unable
+# to authenticate at all.
+#
+# Read time and pass time are separate: the config reads above have already
+# happened, so this script goes on using AGORA_CLAUDE_BIN, AGORA_TIMEOUT_SECS
+# and friends as ordinary shell variables. Only the CHILD's copy is removed,
+# which is why test-injected configuration still works.
+#
+# Built from the exported names actually present (compgen -e), so a prefixed
+# variable this script has never heard of is covered too.
+# ---------------------------------------------------------------------------
+_child_env_strip=()
+while IFS= read -r _agora_env_name; do
+  [ -n "$_agora_env_name" ] || continue
+  _child_env_strip+=(-u "$_agora_env_name")
+done < <(compgen -e 2>/dev/null | grep '^AGORA_' || true)
+unset _agora_env_name
+
+# ---------------------------------------------------------------------------
+# run_with_timeout <seconds> <cmd>... — R005: macOS ships no GNU timeout.
+# Returns 124 on timeout, otherwise the command's own exit code.
+#
+# AGORA_FORCE_TIMEOUT_FALLBACK=1 is a TEST-ONLY switch (default off, never
+# set in production) that forces the wait-based fallback branch even when
+# gtimeout is installed locally, so both the gtimeout path and the fallback
+# path can be exercised deterministically regardless of what happens to be
+# on the machine running the tests (dev boxes have coreutils; GitHub-hosted
+# macos CI runners may not).
+#
+# F1 (review round 2, controller-measured): the fallback watchdog kills the
+# WHOLE PROCESS GROUP of the backgrounded command, not just its direct PID.
+# `kill -TERM "$pid"` alone only reaches the direct child — a vendor CLI
+# that forks a grandchild (common in Node-wrapped CLIs) orphans it, and the
+# orphan keeps running (and, against a real vendor, keeps making API calls)
+# after this function has already reported the vendor as timed out/missing.
+# Measured: `kill -TERM "$pid"` left 2/3 descendants of a forking stub
+# alive; `kill -TERM -- -"$pid"` (negative PID = process group) left 0.
+# `gtimeout`'s own default (non `--foreground`) mode already targets the
+# whole group, so only this fallback branch needed the fix.
+#
+# Getting a process group AT ALL requires job control (`set -m`) to be on —
+# without it, `"$@" &` inherits this shell's own process group, and a
+# negative-PID kill would hit this script's group, not just the timed-out
+# command's. macOS ships no `setsid`, so `set -m` is the only portable way
+# to get the backgrounded command its own group here. Scoped strictly to
+# this function: only turned on if not already on, and turned back off
+# before returning, so the rest of reviewers.sh (and any caller) is
+# unaffected by the job-control side effects (e.g. "Terminated" job
+# notifications on stray fds).
+# ---------------------------------------------------------------------------
+run_with_timeout() {
+  local secs="$1"; shift
+  if [ "${AGORA_FORCE_TIMEOUT_FALLBACK:-0}" != "1" ] && command -v gtimeout >/dev/null 2>&1; then
+    gtimeout "$secs" "$@"
+    return $?
+  fi
+
+  local restore_job_control=0
+  case $- in
+    *m*) ;;
+    *) set -m; restore_job_control=1 ;;
+  esac
+
+  "$@" &
+  local pid=$!
+  # Negative PID targets the whole process group (job-control-assigned pgid
+  # == the group leader's pid), so grandchildren the command forks are
+  # reaped too, not just the direct child.
+  ( sleep "$secs"; kill -TERM -- "-$pid" 2>/dev/null ) &
+  local watcher=$!
+
+  local rc=0
+  # 2>/dev/null: suppresses this shell's own job-control "Terminated"
+  # notification, which (only under `set -m`) prints as a side effect of
+  # `wait` reaping a signal-killed background job — noise, not a diagnostic
+  # this script itself emits.
+  wait "$pid" 2>/dev/null || rc=$?
+  # F1 (review round 3, measured): the watchdog must be torn down by PROCESS
+  # GROUP for exactly the reason the command itself is — `kill -TERM
+  # "$watcher"` reaches only the subshell, and its `sleep` child is orphaned
+  # and re-parented to init, where it lingers for the full AGORA_TIMEOUT_SECS
+  # (default 300). This is the SUCCESS path: when the command finishes first
+  # the watchdog's sleep is still running, so every completed vendor call
+  # leaked one. Measured before the fix: 1 orphaned `sleep` per call — up to
+  # 6 per round (3 reviewers + 3 judge attempts). On timeout nothing leaked,
+  # because the sleep had already elapsed by definition, which is why the
+  # existing timeout-path tests never saw it.
+  # Safe under `set -m` (guaranteed on in this branch by the block above):
+  # measured pgid(watcher) == pid(watcher) != pgid(this script), so the
+  # negative-PID kill cannot reach this script's own group. The pid also
+  # cannot have been recycled onto an unrelated group, because $watcher is
+  # still an unreaped child here — its zombie holds both the pid and the
+  # group until the `wait` below.
+  kill -TERM -- "-$watcher" 2>/dev/null || true
+  wait "$watcher" 2>/dev/null || true
+
+  [ "$restore_job_control" -eq 1 ] && set +m
+
+  # 143 = SIGTERM from the watchdog; normalize to the GNU timeout convention.
+  [ "$rc" -eq 143 ] && rc=124
+  return "$rc"
+}
+
+# ---------------------------------------------------------------------------
+# run_sanitized <seconds> <cmd>... — run_with_timeout with the AGORA_*
+# variables removed from the command's environment (see _child_env_strip).
+# Wrapping the command in `env` rather than unsetting the variables in this
+# shell is what keeps the read/pass split above intact. `env` execs the
+# command in place, so the pid and process group that run_with_timeout's
+# watchdog targets are the command's own, exactly as before.
+# ---------------------------------------------------------------------------
+run_sanitized() {
+  local secs="$1"; shift
+  run_with_timeout "$secs" env ${_child_env_strip[@]+"${_child_env_strip[@]}"} "$@"
+}
+
+# ---------------------------------------------------------------------------
+# invoke_vendor <slug> <prompt_file> — dispatches to the vendor-specific CLI
+# argument shape (spec §2 REQ-1) and applies run_sanitized uniformly, so
+# every vendor is launched under both the timeout and the env strip.
+# ---------------------------------------------------------------------------
+invoke_vendor() {
+  local slug="$1" prompt_file="$2"
+  local prompt; prompt=$(cat "$prompt_file")
+  case "$slug" in
+    claude)
+      # --enable-auto-mode: the user's shell `claude` alias appends this
+      # flag (Ruling 12 measured); aliases do not expand under
+      # non-interactive `bash script.sh` execution, so it must be passed
+      # explicitly here or the CLI runs without it.
+      run_sanitized "$AGORA_TIMEOUT_SECS" "$AGORA_CLAUDE_BIN" \
+        -p --model claude-opus-4-8 --enable-auto-mode "$prompt"
+      ;;
+    omx)
+      # omx is a plain binary, not a shell alias (spec §2 measured) — no
+      # extra flag is needed.
+      run_sanitized "$AGORA_TIMEOUT_SECS" "$AGORA_OMX_BIN" exec "$prompt"
+      ;;
+    agy)
+      # --dangerously-skip-permissions: the user's shell `agy` alias appends
+      # this flag (Ruling 12 measured); aliases do not expand under
+      # non-interactive `bash script.sh` execution, so it must be passed
+      # explicitly here or the CLI may block on a permission prompt.
+      run_sanitized "$AGORA_TIMEOUT_SECS" "$AGORA_AGY_BIN" \
+        -p --model gemini-3.1-pro-high --output-format json \
+        --json-schema "$SCHEMA_PATH" --dangerously-skip-permissions "$prompt"
+      ;;
+    *) return 65 ;;
+  esac
+}
+
+# ---------------------------------------------------------------------------
+# _emit_vendor_stderr_tail <slug> <err_file> — F2 (review round 2): print the
+# last 20 lines of a vendor's captured stderr as part of THIS script's own
+# diagnostic output, so a failure's actual cause (auth, rate-limit, model
+# deprecation, network) is debuggable instead of silently discarded. A
+# vendor's session/hook logs can be long (omx in particular), so only the
+# tail is surfaced, not the whole file.
+# ---------------------------------------------------------------------------
+_emit_vendor_stderr_tail() {
+  local slug="$1" err_file="$2"
+  if [ -s "$err_file" ]; then
+    printf '[agora] %s stderr (last 20 lines):\n' "$slug" >&2
+    tail -n 20 "$err_file" >&2
+  fi
+}
+
+# ---------------------------------------------------------------------------
+# call_vendor <slug> <prompt_file> <out_file> — one retry, then missing
+# (spec §11). Writes <out_file> ONLY on a verified-parseable success; a
+# missing vendor leaves no file at all (silent-failure avoidance: callers
+# distinguish "responded" from "missing" by file existence, never by an
+# empty/partial file).
+#
+# F2 (review round 2): each attempt's vendor stderr is captured to
+# <out_dir>/<slug>.attempt-<N>.stderr.log — inside SEALED/raw/round-N/, the
+# same trust boundary as the raw response itself (never under anon/). On
+# success the log is removed (no noise from chatty vendors); on failure it
+# is left on disk for audit AND its tail is folded into this script's own
+# diagnostic stderr via _emit_vendor_stderr_tail.
+# ---------------------------------------------------------------------------
+call_vendor() {
+  local slug="$1" prompt_file="$2" out_file="$3"
+  local attempt rc tmp err_file out_dir_path
+  tmp=$(mktemp)
+  out_dir_path="$(dirname "$out_file")"
+
+  for attempt in 1 2; do
+    rc=0
+    err_file="$out_dir_path/$slug.attempt-$attempt.stderr.log"
+    invoke_vendor "$slug" "$prompt_file" > "$tmp" 2> "$err_file" || rc=$?
+
+    if [ "$rc" -eq 124 ]; then
+      printf '[agora] %s timeout on attempt %s\n' "$slug" "$attempt" >&2
+      _emit_vendor_stderr_tail "$slug" "$err_file"
+    elif [ "$rc" -ne 0 ]; then
+      printf '[agora] %s exited %s on attempt %s\n' "$slug" "$rc" "$attempt" >&2
+      _emit_vendor_stderr_tail "$slug" "$err_file"
+    elif ! jq -e . "$tmp" >/dev/null 2>&1; then
+      printf '[agora] %s returned unparsable output on attempt %s\n' "$slug" "$attempt" >&2
+      _emit_vendor_stderr_tail "$slug" "$err_file"
+      rc=65
+    else
+      # Success is written to the final path ONLY after the response has
+      # been confirmed valid JSON — never before the check is settled.
+      rm -f "$err_file"
+      mv "$tmp" "$out_file"
+      return 0
+    fi
+
+    [ "$attempt" -eq 1 ] && printf '[agora] %s retry\n' "$slug" >&2
+  done
+
+  rm -f "$tmp"
+  printf '[agora] %s missing after retry\n' "$slug" >&2
+  return 1
+}
+
+# ---------------------------------------------------------------------------
+# run_reviewers --session-dir <dir> --round <N> --prompt-file <file>
+# Fans out call_vendor to all three vendors in parallel, then aborts the
+# round (exit 3) once two or more are missing (spec §11: a single opinion is
+# not a consensus process).
+# ---------------------------------------------------------------------------
+run_reviewers() {
+  local dir='' round='' prompt_file=''
+  while [ "$#" -gt 0 ]; do
+    case "$1" in
+      --session-dir) dir="$2";         shift 2 ;;
+      --round)       round="$2";       shift 2 ;;
+      --prompt-file) prompt_file="$2"; shift 2 ;;
+      *) printf 'reviewers.sh: unknown option %s\n' "$1" >&2; return 64 ;;
+    esac
+  done
+  [ -n "$dir" ] && [ -n "$round" ] && [ -n "$prompt_file" ] || {
+    printf 'reviewers.sh: --session-dir, --round and --prompt-file are required\n' >&2
+    return 64
+  }
+
+  local out_dir="$dir/SEALED/raw/round-$round"
+  mkdir -p "$out_dir"
+
+  local pids=() slugs=(claude omx agy) slug
+  for slug in "${slugs[@]}"; do
+    call_vendor "$slug" "$prompt_file" "$out_dir/$slug.json" &
+    pids+=("$!")
+  done
+
+  local i missing=0
+  for i in "${!pids[@]}"; do
+    wait "${pids[$i]}" || missing=$(( missing + 1 ))
+  done
+
+  if [ "$missing" -ge 2 ]; then
+    printf '[agora] 2 or more reviewers missing (%s) — aborting round %s\n' "$missing" "$round" >&2
+    return 3
+  fi
+  printf '[agora] round %s reviewers: %s responded\n' "$round" "$(( 3 - missing ))" >&2
+  return 0
+}
+
+main() {
+  case "${1:---help}" in
+    --run) shift; run_reviewers "$@" ;;
+    --help | -h)
+      cat <<'USAGE'
+Usage:
+  reviewers.sh --run --session-dir <dir> --round <N> --prompt-file <file>
+USAGE
+      ;;
+    *) printf 'reviewers.sh: unknown option %s\n' "$1" >&2; return 64 ;;
+  esac
+}
+
+main "$@"

package/templates/.claude/skills/agora/scripts/verdict-schema.json

@@ -0,0 +1,34 @@
+{
+  "type": "object",
+  "required": ["round", "judge", "consensus", "verdict", "resolved", "unresolved", "agenda", "draft", "new_findings", "notes"],
+  "properties": {
+    "round": { "type": "number" },
+    "judge": { "type": "string" },
+    "consensus": { "type": "string", "enum": ["UNANIMOUS", "MAJORITY", "SPLIT", "NONE"] },
+    "verdict": { "type": "string", "enum": ["BUILD", "BUILD_WITH_CHANGES", "REDESIGN", "ABANDON"] },
+    "resolved": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "required": ["id", "resolution"],
+        "properties": { "id": { "type": "string" }, "resolution": { "type": "string" } }
+      }
+    },
+    "unresolved": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "required": ["id", "severity", "positions"],
+        "properties": {
+          "id": { "type": "string" },
+          "severity": { "type": "string", "enum": ["CRITICAL", "HIGH", "MEDIUM", "LOW"] },
+          "positions": { "type": "string" }
+        }
+      }
+    },
+    "agenda": { "type": "array", "items": { "type": "string" } },
+    "draft": { "type": "string" },
+    "new_findings": { "type": "number" },
+    "notes": { "type": "string" }
+  }
+}

package/templates/.claude/skills/hada-scout/SKILL.md

@@ -50,7 +50,7 @@ The haiku agent receives the following system prompt:
 
 ```
 You are a relevance filter for the oh-my-customcode project — an AI agent harness/orchestration
-system built on Claude Code CLI with 49 agents, 114 skills.
+system built on Claude Code CLI with 50 agents, 115 skills.
 
 Project domains (HIGH relevance):
 - AI agent orchestration, multi-agent systems, agent design patterns

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

@@ -95,7 +95,7 @@ Infra Engineer:
   infra-docker-expert       Docker containerization
   infra-aws-expert          AWS architecture
 
-Total: 49 agents
+Total: 50 agents
 ```
 
 ### Rules List

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

@@ -5,6 +5,14 @@ version: "2.1.0"
 # Design rule: each pipeline run produces ONE bounded release unit (3-7 issues), not all open issues.
 # This pipeline is a project-agnostic template. Project-specific overrides belong in
 # the project's own workflows/auto-dev.yaml (e.g., AgentNav, second-brain).
+#
+# Design rule (R020 「위임 경계를 Phase 개수로 설계」 배선, Origin: #1595 #4):
+# 아래 `skill:` 스텝 중 다중 Phase 스킬(deep-plan = research→plan→verify, deep-verify = 다각 검증)은
+# 스킬을 그대로 spawn하지 않는다. Phase 경계가 곧 종료 유혹 지점이므로, 발주 전에 스킬의 Phase를
+# 읽고 **단일 목표 1개짜리 위임**으로 분할해 순차 발주한다. 실측(v1.1.48): `skill: deep-plan`을
+# 그대로 호출한 결과 tool_uses=0 / 6.9초 / 산출물 0으로 종료했고, 단일 목표 Plan 에이전트로
+# 재설계하니 1/1 완주했다. `skill:` 값은 **분할의 근거가 되는 스킬 정의**를 가리키는 것이지
+# "이 스킬을 1회 호출하라"는 뜻이 아니다.
 
 steps:
   - name: pre-triage
@@ -270,7 +278,7 @@ steps:
 
   - name: deep-plan
     skill: deep-plan
-    description: "Research-validated implementation plan (research → plan → verify) — skipped if docs-only, integrated-analysis allowed if lite"
+    description: "Research-validated implementation plan (research → plan → verify) — skipped if docs-only, integrated-analysis allowed if lite. MULTI-PHASE: 스킬을 그대로 spawn하지 말고 R020 「위임 경계를 Phase 개수로 설계」에 따라 단일 목표 위임으로 분할해 순차 발주한다 (#1595 #4)."
     depends_on: plan
 
   - name: implement
@@ -357,7 +365,7 @@ steps:
 
   - name: deep-verify
     skill: deep-verify
-    description: "Multi-angle release quality verification — self-review checklist if docs-only; mgr-sauron R017 + core self-check if lite"
+    description: "Multi-angle release quality verification — self-review checklist if docs-only; mgr-sauron R017 + core self-check if lite. MULTI-PHASE: 스킬을 그대로 spawn하지 말고 R020 「위임 경계를 Phase 개수로 설계」에 따라 단일 목표 위임으로 분할해 순차 발주한다 (#1595 #4)."
     depends_on: verify-build
 
   - name: release
@@ -398,8 +406,18 @@ steps:
            #   Edit ONLY the .version field — do NOT overwrite templates/manifest.json wholesale (e.g. a source-hash path→hash map).
            #   Recover a corrupted manifest: git show HEAD:templates/manifest.json | jq '.version="<NEW>"' > templates/manifest.json (#1423/#1154).
            d. templates/manifest.json: jq '.version = "<NEW>"' templates/manifest.json > templates/manifest.json.tmp && mv templates/manifest.json.tmp templates/manifest.json   [on release/v{NEW}]
-           e. bun run build — run standalone (NO pipe), read exit code directly ($? after a pipe is the last command's, R005/#1492).
-              This regenerates .omcustom.lock.json (generatorVersion/templateVersion) to <NEW> via scripts/sync-source-lockfile.ts.   [on release/v{NEW}]
+           e. ⚠ PREREQUISITE: steps c (package.json) AND d (templates/manifest.json) MUST BOTH be completed
+              before running this step. bun run build — run standalone (NO pipe), read exit code directly
+              ($? after a pipe is the last command's, R005/#1492).
+              Actual mechanism (corrected, #1593): `bun run build` invokes `scripts/sync-source-lockfile.ts`
+              (a 10-line wrapper with no version literals of its own), which calls
+              `generateAndWriteLockfileForDir` (`src/core/lockfile.ts`). That function reads versions via
+              `loadVersions()` (`src/core/sync.ts`) — `generatorVersion` FROM package.json, `templateVersion`
+              FROM templates/manifest.json — and writes both into .omcustom.lock.json. If step d has not yet
+              landed when this runs, the lockfile silently records the PREVIOUS templateVersion — no warning,
+              no error. Observed contamination: v1.1.47 shipped generatorVersion=1.1.47 / templateVersion=1.1.46
+              because the bump commit created package.json + lockfile together and manifest.json was bumped in
+              a later commit. Do NOT run this step until BOTH c and d are staged.   [on release/v{NEW}]
            f. git status --short — enumerate ALL tracked drift (`^ M`) the build produced; stage EVERY one (esp. .omcustom.lock.json) before commit.
               (#1531 — .omcustom.lock.json missed staging across 4 consecutive releases after v1.1.29; root cause was no build step between version bump and commit.)   [on release/v{NEW}]
            g. mgr-gitnerd commit: "chore(release): bump to v<NEW>" — MUST include the drift from step f.
@@ -411,12 +429,27 @@ steps:
            i. mandatory verification (with existence guard for partial-update safety), run on release/v{NEW}:
               [ -f scripts/verify-version-sync.sh ] && bash scripts/verify-version-sync.sh || echo "::warning::verify-version-sync.sh not found, version sync verification skipped"
               (verify-version-sync.sh 가 exit 1 시 release 단계 halt)
+           j. lockfile 3-way assertion (#1593 제안3, closes the gap step i's 2-way check misses) — run standalone
+              (NO pipe), read exit code directly, on release/v{NEW}:
+              jq -e --arg v "<NEW>" '.generatorVersion==$v and .templateVersion==$v' .omcustom.lock.json
+              실패 시 release 단계 halt — cause is almost always step e run before step d landed; fix by
+              re-running step d then step e, re-staging, and re-running this assertion.
 
          Version decision (semver) — PATCH-PREFERRED policy (post-1.0.0):
          - No existing tags → v0.1.0
          - Previous tag exists → DEFAULT to patch. When in doubt, patch — do NOT reflexively bump minor for rule/doc/skill edits.
            - patch (DEFAULT): rule/doc/skill/config/wiki/workflow changes, bugfixes, hardening, CC-compat notes — the vast majority of this project's changes
-           - minor: ONLY a genuinely NEW user-facing capability (a new skill/agent/command adding user-visible surface), not a refinement of an existing one
+           - minor: ONLY a new user-facing capability that changes HOW the harness is used — a new
+             workflow axis, a new command surface users must learn, or a contract other components
+             depend on. NOT "a file was added under .claude/skills/ or .claude/agents/".
+             ⚠ Counter-example (Origin: v1.1.49 세션, 사용자 지적): adding one skill + one agent
+             (agora: skills 114→115, agents 49→50) was initially scoped as v1.2.0 minor by reading
+             the old wording literally. That was WRONG — this repo adds skills routinely, and
+             skills reached 115 while the version stayed v1.1.48, so skill/agent addition is
+             ESTABLISHED as patch (target was corrected to v1.1.49). Count growth is this repo's
+             baseline rate of change, NOT a minor signal. If a version bump would follow
+             mechanically from "a new file exists", it is patch. Ask instead: does a user's
+             workflow change because of this?
            - major: breaking changes to user-facing contracts (CLI flags, public skill/command names, public API), or a deliberate milestone declaration (e.g., v1.0.0)
          - 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)
 
@@ -428,7 +461,15 @@ steps:
            b. mgr-gitnerd creates PR: gh pr create --base develop --head release/v{NEW} --title "chore(release): bump to v{NEW}" --body "<MUST include 'Closes #N' for EVERY issue this release resolves>"
               ⚠ auto-tag.yml closes issues by grep'ing Closes/Fixes/Resolves keywords in the PR BODY — NOT by milestone membership NOR by commit message trailers. If the keywords are missing, no issues close and the workflow still reports success (#1531). Commit-message close keywords are explicitly forbidden during `implement` and step 1.g above (#1542) — the PR body is the ONLY place a close keyword should appear.
               Before creating the PR (whether via inline --body or --body-file), confirm the body text actually contains a Closes line per issue.
-           c. mgr-gitnerd merges PR (admin merge required due to branch protection)
+           c. mgr-gitnerd merges PR: gh pr merge {n} --merge --delete-branch (plain merge — NOT --admin).
+              Ground-truth (measured 2026-08-15, `gh api repos/{owner}/{repo}/branches/develop/protection`):
+              required status checks are exactly 6 — Test, Lint, Template Sync, Version Sync,
+              Dependency Security Audit, Rust Tests (strict=true); enforce_admins=false; NO
+              required_pull_request_reviews (no reviewer-approval requirement exists). v1.1.47 merged with a
+              plain `gh pr merge 1585 --merge --delete-branch` — no --admin needed. A plain merge succeeds
+              once all 6 checks report green. If the merge is rejected, do NOT reflexively add --admin —
+              re-run the protection query above to re-measure current requirements and report the actual
+              blocker (R010 bypass-flag pre-check: name what is bypassed and why before ever using --admin).
            d. DO NOT manually git tag or gh release create.
               auto-tag.yml fires on release/v* PR merge → creates tag → closes issues linked via PR-body Closes/Fixes/Resolves keywords → closes milestone → deletes release branch.
               release.yml fires on the tag → npm publish + GitHub Release creation.

package/templates/.claude/skills/sauron-watch/SKILL.md

@@ -198,7 +198,7 @@ Starting full R017 verification...
 ═══════════════════════════════════════════════════════════
 
 [Round 1/5] mgr-supplier:audit
-  ✓ 49 agents checked, 0 issues
+  ✓ 50 agents checked, 0 issues
 
 [Round 2/5] mgr-updater:docs
   ✓ Documentation sync: OK

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

@@ -33,10 +33,10 @@ Agents:
   Database:         4
   Infra Engineer:   2
   Other:           10 (security, architect, QA, system)
-  Total:           49 agents
+  Total:           50 agents
 
 Skills:
-  Total:          114 skills
+  Total:          115 skills
 
 Guides:            56 loaded
 Commands:          60+ available
@@ -131,7 +131,7 @@ status --health
 Health Checks:
 
 Agents:
-  ✓ 49/49 agents valid
+  ✓ 50/50 agents valid
   ✓ All agent files exist in .claude/agents/
 
 Dependencies:

package/templates/.claude/skills/token-efficiency-audit/SKILL.md

@@ -125,7 +125,7 @@ Applies CI/Worker-Only Levers. These disable core oh-my-customcode functionality
 
 These settings disable core oh-my-customcode functionality:
   • CLAUDE_CODE_DISABLE_CLAUDE_MDS=1  → ALL rules and routing offline (R010 disabled)
-  • CLAUDE_AGENT_SDK_DISABLE_BUILTIN_AGENTS=1 → All 49 agents unavailable
+  • CLAUDE_AGENT_SDK_DISABLE_BUILTIN_AGENTS=1 → All 50 agents unavailable
   • ENABLE_CLAUDEAI_MCP_SERVERS=false → MCP-dependent skills unavailable
   • CLAUDE_CODE_DISABLE_AUTO_MEMORY=1 → No persistent memory across sessions
 

package/templates/.github/workflows/wiki-sync.yml

@@ -127,6 +127,6 @@ jobs:
           TOTAL_GUIDES=$(find guides -mindepth 1 -maxdepth 1 -type d 2>/dev/null | wc -l | tr -d ' ')
           TOTAL_WIKI=$(find wiki -name "*.md" ! -name "index.md" ! -name "log.md" 2>/dev/null | wc -l | tr -d ' ')
 
-          echo "Source entities: agents=$TOTAL_AGENTS skills=$TOTAL_SKILLS rules=$TOTAL_RULES guides=$TOTAL_GUIDES"
+          echo "Source entities: agents=$TOTAL_AGENTS skills=$TOTAL_SKILLS rules=$TOTAL_RULES guide_topics=$TOTAL_GUIDES"
           echo "Wiki pages: $TOTAL_WIKI"
           echo "All wiki pages present — sync OK"

package/templates/CLAUDE.md

@@ -117,8 +117,8 @@ oh-my-customcode로 구동됩니다.
 project/
 +-- CLAUDE.md                    # 진입점
 +-- .claude/
-|   +-- agents/                  # 서브에이전트 정의 (49 파일)
-|   +-- skills/                  # 스킬 (114 디렉토리)
+|   +-- agents/                  # 서브에이전트 정의 (50 파일)
+|   +-- skills/                  # 스킬 (115 디렉토리)
 |   +-- rules/                   # 전역 규칙 (R000-R023)
 |   +-- hooks/                   # 훅 스크립트 (보안, 검증, HUD)
 |   +-- contexts/                # 컨텍스트 파일 (ecomode)
@@ -180,7 +180,7 @@ oh-my-customcode는 소프트웨어 컴파일과 동일한 구조를 따릅니
 | System | 4 | sys-memory-keeper, sys-naggy, tracker-checkpoint, wiki-curator |
 -->
 
-총 **49개** 에이전트 (타입별 상세는 `/omcustom:lists` 또는 wiki/agents/ 참조)
+총 **50개** 에이전트 (타입별 상세는 `/omcustom:lists` 또는 wiki/agents/ 참조)
 
 ## Agent Teams (MUST when enabled)
 

package/templates/CLAUDE.md.en

@@ -129,8 +129,8 @@ NO EXCEPTIONS. NO EXCUSES.
 project/
 +-- CLAUDE.md                    # Entry point
 +-- .claude/
-|   +-- agents/                  # Subagent definitions (49 files)
-|   +-- skills/                  # Skills (114 directories)
+|   +-- agents/                  # Subagent definitions (50 files)
+|   +-- skills/                  # Skills (115 directories)
 |   +-- rules/                   # Global rules (R000-R023)
 |   +-- hooks/                   # Hook scripts (security, validation, HUD)
 |   +-- contexts/                # Context files (ecomode)
@@ -174,7 +174,7 @@ This is the core oh-my-customcode philosophy: **"No expert? CREATE one, connect
 | QA Team | 3 | qa-planner, qa-writer, qa-engineer |
 | Manager | 6 | mgr-creator, mgr-updater, mgr-supplier, mgr-gitnerd, mgr-sauron, mgr-claude-code-bible |
 | System | 4 | sys-memory-keeper, sys-naggy, tracker-checkpoint, wiki-curator |
-| **Total** | **49** | |
+| **Total** | **50** | |
 
 ## Agent Teams (MUST when enabled)
 

package/templates/CLAUDE.md.ko

@@ -129,8 +129,8 @@ oh-my-customcode로 구동됩니다.
 project/
 +-- CLAUDE.md                    # 진입점
 +-- .claude/
-|   +-- agents/                  # 서브에이전트 정의 (49 파일)
-|   +-- skills/                  # 스킬 (114 디렉토리)
+|   +-- agents/                  # 서브에이전트 정의 (50 파일)
+|   +-- skills/                  # 스킬 (115 디렉토리)
 |   +-- rules/                   # 전역 규칙 (R000-R023)
 |   +-- hooks/                   # 훅 스크립트 (보안, 검증, HUD)
 |   +-- contexts/                # 컨텍스트 파일 (ecomode)
@@ -174,7 +174,7 @@ project/
 | QA Team | 3 | qa-planner, qa-writer, qa-engineer |
 | Manager | 6 | mgr-creator, mgr-updater, mgr-supplier, mgr-gitnerd, mgr-sauron, mgr-claude-code-bible |
 | System | 4 | sys-memory-keeper, sys-naggy, tracker-checkpoint, wiki-curator |
-| **총계** | **49** | |
+| **총계** | **50** | |
 
 ## Agent Teams (MUST when enabled)
 

package/templates/README.md

@@ -47,8 +47,8 @@ templates/
 ├── CLAUDE.md                        # 에이전트 시스템 진입점
 ├── manifest.json                    # 배포 컴포넌트 카운트 및 메타데이터
 ├── .claude/
-│   ├── agents/                      # 에이전트 정의 파일 (*.md, 49개)
-│   ├── skills/                      # 스킬 모듈 (각 디렉토리에 SKILL.md, 114개)
+│   ├── agents/                      # 에이전트 정의 파일 (*.md, 50개)
+│   ├── skills/                      # 스킬 모듈 (각 디렉토리에 SKILL.md, 115개)
 │   ├── rules/                       # 전역 규칙 (R000–R023, 23개)
 │   ├── hooks/
 │   │   ├── hooks.json               # 훅 이벤트 설정 (PreToolUse/PostToolUse 등)
@@ -65,7 +65,7 @@ templates/
 아래 카운트는 `templates/manifest.json`과 동기화됩니다.
 CI의 `verify-template-sync.sh`가 소스와 templates/ 간 일치를 검증합니다.
 
-### Agents (49)
+### Agents (50)
 
 `.claude/agents/*.md` — 에이전트 정의 파일.
 
@@ -80,13 +80,13 @@ CI의 `verify-template-sync.sh`가 소스와 templates/ 간 일치를 검증합
 | DE Engineer | 6 |
 | SW Engineer / Database | 4 |
 | Security | 1 |
-| SW Architect | 2 |
+| SW Architect | 3 |
 | Infra Engineer | 2 |
 | QA Team | 3 |
 | Manager | 6 |
 | System | 4 |
 
-### Skills (114)
+### Skills (115)
 
 `.claude/skills/*/SKILL.md` — 재사용 가능한 스킬 모듈.
 

package/templates/guides/agent-eval/README.md

@@ -23,7 +23,7 @@ LangChain의 Deep Agents 평가 방법론은 "More evals ≠ better agents" 철
 
 ### oh-my-customcode 맥락
 
-oh-my-customcode의 에이전트 시스템은 49개 전문 에이전트와 114개 스킬로 구성된다. 이 방법론은 신규 에이전트 검증(mgr-creator), 릴리즈 품질 검증(deep-verify), 반복 개선 루프(evaluator-optimizer)에 정량 차원을 추가하는 수단으로 내재화된다.
+oh-my-customcode의 에이전트 시스템은 50개 전문 에이전트와 115개 스킬로 구성된다. 이 방법론은 신규 에이전트 검증(mgr-creator), 릴리즈 품질 검증(deep-verify), 반복 개선 루프(evaluator-optimizer)에 정량 차원을 추가하는 수단으로 내재화된다.
 
 ---