oh-my-customcode 1.1.82 → 1.1.83

package/dist/cli/index.js

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

package/dist/index.js

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

package/package.json

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

package/templates/.claude/rules/MUST-parallel-execution.md

@@ -365,6 +365,8 @@ Single agent spawns do NOT use the `[N]` prefix.
   ✗ agent-2: failed (reason)
 ```
 
+완료 알림에 보고 본문이 없으면 한 턴 기다리고, 그래도 없으면 산출물을 실측(ground truth)한 뒤 SendMessage로 재요청합니다 — 모든 위임 결과 수집 단계에 적용됩니다.
+
 ## Parallel Feature Integration Gate
 
 병렬 각자의 "build green"은 통합 정합성 미보장 — 병합 후 통합 빌드+런타임 스모크 게이트 필수.

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

@@ -48,12 +48,14 @@ The loop converges naturally when **both** conditions are met:
 1. The auto-dev-eligible issue set reaches 0
 2. All open PRs have been either merged or explicitly deferred
 
+If a release step is held pending a user-executed constrained command (per `pipeline auto-dev`'s release-step user-execution constraint check), convergence MUST NOT be declared — present the pending command(s) to the user and wait, even if the eligible issue set and open-PR count would otherwise read as zero (#1733 찐빠 #2).
+
 수렴을 선언하기 전에(수렴 조건이 아니라 **선언 직전 게이트**로) 이 세션의 homework 아티팩트 수를 실측해 반복 수와 대조합니다. 불일치는 다음 반복을 돌리는 신호가 아니라 **누락분을 기록하라는 신호**이므로, 회상 기반(`[recall]` 표시)으로라도 기록한 뒤 수렴을 선언합니다. v1.1.65 반복은 아티팩트를 기록하지 않은 채 다음 반복으로 넘어갔고 Iteration 4 종료 후에야 누락이 발견되어 회상 기반으로 보완되었습니다(#1688 Iteration 2 #1).
 
 FSD processes **open PRs as part of each iteration**, not only issues. This includes dependabot PRs and any automatically created PRs. Issue eligibility follows `/pipeline auto-dev` label selection exactly:
 
 - **Included**: `verify-ready` (preferred), unlabeled auto-dev candidates
-- **Excluded**: `verify-done`, `needs-review`, `decision-needed` labels
+- **Excluded**: `triage-complete`, `needs-review`, `decision-needed` labels
 
 Do NOT invent new label logic here — defer to the `pipeline` skill's auto-dev issue selection.
 
@@ -69,6 +71,8 @@ When open PRs are found during an iteration:
 | Breaking change / design judgment required | Defer and surface to user |
 | Explicitly excluded by user this session | Skip (honor directive persistence, R015) |
 
+Before executing any merge in this table, apply the same user-execution constraint check used by the release step (CLAUDE.md / session memory / the entry card, if the environment provides one, e.g. a recall entry card) — if the merge is covered by a user-execution constraint, do NOT execute it; present the exact command to the user and wait (#1733 찐빠 #2).
+
 All PR merge operations are delegated to **mgr-gitnerd** (R010). After merging, verify ground-truth via `gh pr view` or `git log` before declaring done (R020).
 
 Do NOT merge PRs that require user approval for architectural decisions. Surface them with a short summary and wait.

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

@@ -8,7 +8,7 @@ Used by `scope-selection` to include/exclude issues and by `implement` for lifec
 | Label | Meaning | scope-selection 처리 |
 |-------|---------|----------------------|
 | `verify-ready` | Triage 완료, 즉시 verify 가능 (자동화 후보) | INCLUDE (preferred) |
-| `verify-done` | Triage 완료했으나 deferred 또는 이미 처리됨 (이번 사이클 미포함) | EXCLUDE |
+| `triage-complete` | Triage 완료, auto-dev 스코프에 선택되지 않음 (standalone triage 또는 deferred) — release-plan이 수집; auto-dev 내부 triage에서 manifest 선택 이슈는 `verify-ready` 부여 (#1734) | EXCLUDE |
 | `in-progress` | 작업 진행 중 (다른 세션에서 claim됨) | EXCLUDE |
 | `needs-review` | 사람 검토 필요 (자동 파이프라인 진입 불가) | EXCLUDE |
 | `decision-needed` | 결정 필요 (보안, 정책 critical) | EXCLUDE |
@@ -22,7 +22,7 @@ Used by `scope-selection` to include/exclude issues and by `implement` for lifec
 ```
 EXCLUDE if:
   - blocked_by_decision == true
-  - labels ∩ {decision-needed, needs-review, verify-done, manual-action, in-progress} ≠ ∅
+  - labels ∩ {decision-needed, needs-review, triage-complete, manual-action, in-progress} ≠ ∅
 
 INCLUDE (preferred tier):
   - labels ∩ {verify-ready, claude-code-release, documentation} ≠ ∅
@@ -55,5 +55,5 @@ If ALL scoped issues carry at least one lite-eligible label AND scope size ≤ 7
 | Work started | Add `in-progress`, assign @me |
 | Work succeeded | Remove `in-progress`, add `verify-ready` |
 | Work failed | Remove `in-progress`, add `needs-review` |
-| Released | Remove `verify-ready`, close with "Fixed in v{version}" |
-| Deferred | Add `verify-done`, label "Deferred from v{version}" |
+| Released | Remove `verify-ready`, close with "Fixed in v{version}" (auto-dev's `ci-check` step applies the `verify-ready` removal to the CURRENT release's scoped issues only; past closed issues' stale `verify-ready` are out of scope by user decision, #1734) |
+| Deferred | Add `triage-complete`, label "Deferred from v{version}" |

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

@@ -158,7 +158,7 @@ steps:
       Reference label semantics: .claude/skills/pipeline/labels.md
 
       Apply filter rules:
-      - EXCLUDE: blocked_by_decision == true OR labels ∩ {decision-needed, needs-review, verify-done, manual-action, in-progress} ≠ ∅
+      - EXCLUDE: blocked_by_decision == true OR labels ∩ {decision-needed, needs-review, triage-complete, manual-action, in-progress} ≠ ∅
       - INCLUDE (preferred): labels ∩ {verify-ready, claude-code-release, documentation} ≠ ∅
       - INCLUDE (standard): P1/P2/P3 issues not in excluded set
       - Tie-break: P1 > P2 > P3 > unclassified
@@ -237,6 +237,9 @@ steps:
         - triage step: skip professor-triage skill; perform direct manifest summary instead
         - plan step: skip release-plan skill; single-response plan instead
         - deep-plan step: skip deep-plan skill; single-response implementation notes instead
+          (except when scope contains a security/availability issue — see the Cross-tier
+          「Lightweight Skill-Mode Substitution」 restriction below, which forbids this
+          substitution for such issues)
         - deep-verify step: skip deep-verify skill; perform self-review checklist instead
           — 단, 변경 집합에 `.claude/rules/**`(또는 agents/skills frontmatter 등 구조 표면)가
           포함되면 self-review로 대체하지 않고 mgr-sauron R017 검증을 **단일 목표 위임으로 필수
@@ -262,6 +265,9 @@ steps:
         - triage step: MAY replace professor-triage skill spawn with orchestrator integrated analysis
         - plan step: MAY replace release-plan skill spawn with orchestrator integrated analysis
         - deep-plan step: MAY replace deep-plan skill spawn with orchestrator integrated analysis
+          (except when scope contains a security/availability issue — see the Cross-tier
+          「Lightweight Skill-Mode Substitution」 restriction below, which forbids this
+          substitution for such issues)
         - deep-verify step: perform via mgr-sauron R017 structural verification + core self-check (split standard: see the deep-verify step description — R017 spawn + change-type adversarial review, one single-goal delegation each)
           (instead of full deep-verify skill spawn). If the change set has NO structural surface
           (no agent/skill/guide/rule frontmatter changed — e.g. a workflow-yaml-only or docs-only change),
@@ -307,14 +313,14 @@ steps:
       | pre-triage | `gh label create in-progress / verify-ready / needs-review --force` (idempotent label bootstrap) |
       | scope-selection | Milestone 3-branch state machine (Step 0): closed → HALT / open → reuse / absent → `gh api repos/{owner}/{repo}/milestones --method POST`. Then: assign every scoped issue to that milestone. |
       | compression-mode-eval | none (pure evaluation + justification logs) |
-      | triage | none (analysis only) — compressible |
+      | triage | `verify-ready` added to manifest issues selected by professor-triage when it runs inside this step (NOT `triage-complete`) — analysis output is compressible, this label side effect is not; when triage is skipped (docs-only) or substituted (lite integrated-analysis, lightweight mode), no separate label action is required here — the implement step's per-issue success path (row below: "On success: remove in-progress, add verify-ready") already adds `verify-ready` to each processed issue before this release completes |
       | plan | none (analysis only) — compressible |
       | deep-plan | none (analysis only) — compressible |
       | implement | `gh issue edit <N> --add-label in-progress --assignee @me`; `gh issue comment <N>` (start notice); on success remove in-progress + add verify-ready; on failure remove in-progress + add needs-review + comment error summary |
       | verify-build | none (gate only) |
       | deep-verify | none (analysis only) — compressible |
       | release | PR body MUST carry `Closes #N` for every resolved issue (auto-tag.yml greps the PR body); non-auto-tag projects additionally: `gh api .../milestones/{n} --method PATCH --field state=closed`, `gh issue close {n}`, label needs-review issues "Deferred from v{version}" |
-      | ci-check | none (verification only) |
+      | ci-check | `gh issue edit <N> --remove-label in-progress` for stale labels; `gh issue edit <N> --remove-label verify-ready` for THIS release's CLOSED scoped issues only (past closed issues excluded, #1734) |
       | post-release-followup | new issue registration for release follow-ups (genuine defects auto-registered, no-ask per R016) |
 
       Only the rows marked "none (analysis only)" are compressible. Any step with a
@@ -366,6 +372,20 @@ steps:
          `mode: lightweight`) so downstream steps and reviewers can tell it apart from a full
          skill spawn (결과물에 모드를 표시, #1721 제안 4).
 
+      Additional restriction — security/availability scope (#1733 찐빠 #9): if ANY scoped issue
+      carries the `security` label, OR its title/body explicitly states a security/availability
+      concern (e.g. rate limiting, resource exhaustion, injection, denial-of-service — this repo
+      has no separate `availability` label; measured via `gh label list`, so an availability
+      concern must be asserted in the issue text, not inferred from a label), this lightweight
+      substitution is FORBIDDEN for deep-plan on that issue — AND compression-mode-eval Tier 2
+      lite's deep-plan integrated-analysis substitution is also FORBIDDEN for it; deep-plan MUST
+      run as a full skill spawn. Because deep-plan is a single release-scoped step (not run
+      per-issue), when ANY scoped issue qualifies, this restriction applies to the whole
+      release's deep-plan step. The entry-point audit for such an issue MUST include an
+      "executions per request (amplification)" check — how many downstream operations a single
+      request can trigger (e.g. GraphQL alias batching, N+1 fan-out) — not only a per-call
+      timeout/rate-limit check. (GraphQL document fuzz testing is OUT of scope here.)
+
       This substitution is NEVER available for implement, verify-build, release, ci-check, or
       deep-verify.
       It replaces analysis output ONLY — every step's state-change side effect still runs in
@@ -382,7 +402,7 @@ steps:
 
   - name: triage
     skill: professor-triage
-    description: "Cross-analysis triage with priority assessment (scoped to release manifest) — skipped if docs-only, integrated-analysis allowed if lite; independent of tier, MAY run in lightweight mode when compression-mode-eval's 'Cross-tier — Lightweight Skill-Mode Substitution' conditions are met"
+    description: "Cross-analysis triage with priority assessment (scoped to release manifest) — invoke professor-triage WITH the release manifest issue numbers from scope-selection's output as input; in this auto-dev context, manifest issues receive `verify-ready` (not `triage-complete`) per the side-effect inventory above — skipped if docs-only, integrated-analysis allowed if lite; independent of tier, MAY run in lightweight mode when compression-mode-eval's 'Cross-tier — Lightweight Skill-Mode Substitution' conditions are met"
     depends_on: compression-mode-eval
 
   - name: plan
@@ -448,6 +468,16 @@ steps:
         (#1701 #1). The orchestrator's own wiring judgement (which file/anchor already covers a
         new clause) counts as final wording too — the prompt supplies candidate files/anchors
         only, and the subagent decides coverage by quoting the covering sentence (R010 [#1704 #1]).
+        Non-issue sources (더루키 회상, 메모리, 다른 프로젝트 관측) MUST be placed in a separate
+        block labeled with its source (e.g. `[출처: 더루키 회상 — <project>]`) and MUST NOT be
+        mixed into issue-quote sentences — completion criteria MUST state this separation
+        explicitly, applying to every orchestrator-authored delegation, all tiers (R010 「출처
+        인용과 인접 문구 점검」 확장, #1735 찐빠 #1).
+      - A release that bundles ≥2 `feedback`-type issue proposals MUST produce a per-proposal
+        application-boundary table (exceptions, deadlines, tiers/steps) during plan/deep-plan or
+        its lightweight tier substitute, applying to lite and standard tiers, and
+        implement-stage delegation prompts MUST carry the relevant boundary row for each edit
+        (회고 제안 묶음 릴리즈의 통합 분석에 적용 경계 표 필수, #1735 찐빠 #4).
       - Before dispatching any delegation prompt in an iteration that created or reinforced a rule
         clause, the orchestrator MUST compare that clause's Anti-pattern table rows 1:1 against the
         delegation prompt's sentences and rewrite any match (cause: the R016 「신설 조항의 동일
@@ -488,6 +518,14 @@ steps:
         around it (e.g. via a shell glob or path rewrite) — it MUST stop and report the block
         verbatim (R010 「품질 게이트 우회 금지 — 훅 차단은 보고 대상」, extended here from git
         hooks to guards/classifiers/permissions generally) (#1728 찐빠 #1).
+      - No state-changing command (`gh issue create/edit/close`, `gh pr create/edit/close/merge`,
+        `git push`, label changes) — including the orchestrator's own direct commands, not only
+        delegated ones — MAY use a `||` fallback that prints success-looking output; the observed
+        failure mode was a failed `gh issue create` followed by a `||` fallback that printed a
+        DIFFERENT issue's URL, which the orchestrator briefly read as a successful create
+        (#1735 찐빠 #2). Exceptions: a `||` fallback whose output is explicitly marked as
+        failure (e.g. `|| echo "::warning::…"`, a literal `MISS` token) and idempotent bootstrap
+        commands (no `||` success masking) such as `gh label create --force 2>/dev/null`.
       - After any delegation that creates temporary files under constraint (h) above, the
         orchestrator MUST confirm with `git status --short` that no stray file was left in the
         repo (#1721 찐빠 #7).
@@ -496,7 +534,13 @@ steps:
         arithmetic below, not a replacement for it); compute turn arithmetic (files × 3 +
         edit_items × 2 ≤ 16 — a #1709-proposed guide kept below the 20-turn limit, not a
         truncation guarantee, per R020 「maxTurns 절단 실증」 6항) and state that arithmetic in
-        the delegation prompt before dispatch (#1709 #1).
+        the delegation prompt before dispatch (#1709 #1). Any edit delegation requiring
+        verification of N quotations or identifiers (not only claude-code-release CC-note
+        delegations) MUST perform that verification with batched command(s) (a single loop or
+        combined `grep -F` pass over all N items), never per-item invocations, and the turn
+        arithmetic above MUST add a batched-verification term — ⌈N/batch⌉ — still an
+        upper-bound guide that may still truncate, not a truncation guarantee (검증 비용을
+        턴 산술에 반영, R020 「maxTurns 절단 실증」 6항 확장, #1737 찐빠 #1).
       - Parity delegation prompts (e.g. a ko mirror tracking an en source) MUST require THREE
         directions — additions, edits, AND deletions — to match the source, never additions
         only; completion criteria MUST include a `grep -F` confirming zero rows/sentences are
@@ -523,6 +567,16 @@ steps:
         before restating either — do not relay an unverified agent-reported count or identifier
         (R023 「리서치 위임의 결론 수치는 표에서 재계산해 병기」 #1707 #4 확장, #1709 #5, #1722
         찐빠 #3).
+      - Delegations that create files, binaries, worktrees, or branches (artifact-creating
+        delegations only — text-only edits are excluded) MUST include measured output in their
+        completion report — `file <bin>` for binaries, `ls -la <path>` for created paths, `git
+        worktree list` for worktrees, `git branch --list` for branches, as applicable — and the
+        orchestrator MUST confirm architecture/path from that measured output before using the
+        artifact, not from the agent's self-report alone (R020 Subagent Self-Report
+        Verification, #1733 찐빠 #1). (#1733 찐빠 #1's third proposal — never use haiku for
+        worktree/cross-compile delegations — is not added separately here: R006
+        (`.claude/rules/MUST-agent-design.md`) already scopes `haiku` to "Fast, cheap tasks
+        (search, simple edits)", which excludes multi-step build/worktree work.)
       - Delegations that build or replace an evaluation/test harness or a production code path
         (fixtures, ablation lanes, scoring/oracle logic) MUST require bidirectional proof, not
         a single-direction pass: (a) positive AND negative fixtures — a fixture set that can
@@ -536,6 +590,14 @@ steps:
         measurement; (c) no working around a discovered product or measurement defect to force
         a pass — halt and report instead (R023 「Conditional-Output Verification」 양성/음성 짝
         원칙 확장, #1721 찐빠 #1, #1727 찐빠 #2, #1728 찐빠 #2).
+      - Delegations that inject faults / modify-then-restore files — not limited to harness
+        builds — MUST back up the original file under `bak/<repo-relative-path>` (the full
+        repo-relative path, not filename-only) nested under the session scratchpad or `$TMPDIR`
+        (not inside the repo, to stay consistent with constraint (h) above), and a checksum
+        comparison after restore is MANDATORY. A `git diff`-based patch approach is also allowed.
+        `git stash` is otherwise allowed EXCEPT when parallel delegations share the working tree
+        (R009 「File-Disjoint ≠ Independent (Local Git State)」), where it MUST NOT be used
+        (#1733 코멘트 찐빠 #8).
       - For `claude-code-release` issues, CC release knowledge goes to
         `guides/claude-code/15-version-compatibility.md` (+ templates mirror) per rule; a rule
         file gets at most ONE line of behavioral norm only when agent behavior must change.
@@ -638,6 +700,19 @@ steps:
     prompt: |
       Create a GitHub Release.
 
+      0a. User-execution constraint check (mandatory, before step 0, #1733 찐빠 #2): read
+          CLAUDE.md, session memory, and the entry card (if the environment provides one, e.g. a
+          recall entry card) for any user-execution constraint (e.g. "merge/tag/publish must be
+          run by the user, not the agent"). For each command this release step is about to run:
+          if it is COVERED by a constraint (merge, tag, publish), do NOT execute it — present the
+          exact command(s) to the user and STOP this step; if it is NOT covered (e.g. branch
+          creation, version bump, PR creation — coverage is judged by the scope of the constraint
+          text actually found in CLAUDE.md/session memory, not by this example list), proceed
+          normally. No matching constraint found → unchanged behavior, proceed to step 0. User decision
+          (recorded): in an unattended run (`/fsd` etc. — see pre-triage Phase 0.6
+          `unattended_mode`), STOP at the first covered command, present it to the user, and HOLD
+          the convergence declaration until the user runs it and confirms.
+
       0. Pre-check (mandatory, delegate to mgr-gitnerd per R010): Detect and remove stale local `release` branch if present.
          The local `release` branch (file ref) conflicts with `release/v*` directory ref namespace.
          mgr-gitnerd executes (force-delete acceptable in automation context; warns if branch has unpushed commits):
@@ -800,7 +875,11 @@ steps:
          in-progress`) and report the fix; if the issue is still OPEN, do NOT close it here —
          closing stays with auto-tag.yml unless it failed to close that issue, in which case
          report the open issue for manual close per release step 3.d above (#1722 하네스 제안
-         4).
+         4). Additionally, for each scoped issue that IS closed by THIS release, remove a
+         lingering `verify-ready` label if present (`gh issue edit <N> --remove-label
+         verify-ready`) — scoped to THIS release's closed issues only; bulk-removing
+         `verify-ready` from previously closed issues is explicitly excluded (user decision,
+         #1734).
       6. Report final CI status.
     description: "Post-release CI verification and fix loop"
     depends_on: release

package/templates/.claude/skills/post-release-followup/SKILL.md

@@ -19,7 +19,7 @@ After PR creation in the auto-dev release workflow, collect unaddressed findings
 Gather unfinished work from multiple sources:
 
 **Source A — Remaining open issues**:
-- Run: `gh issue list --label verify-done --state open --json number,title,labels`
+- Run: `gh issue list --label triage-complete --state open --json number,title,labels`
 - These are triaged issues NOT included in the current release
 
 **Source B — Deep-verify findings**:

package/templates/.claude/skills/professor-triage/SKILL.md

@@ -20,12 +20,14 @@ Analyzes GitHub issues directly against the current codebase. For each issue, se
 ## Usage
 
 ```
-/professor-triage                          # Default: --state open (excludes verify-done)
+/professor-triage                          # Default: --state open (excludes triage-complete)
 /professor-triage 587 589 590 591 592      # Direct issue numbers
 /professor-triage --label codex-release    # Custom label filter
 /professor-triage --since 2026-03-20       # Date filter
 ```
 
+When `pipeline auto-dev`'s triage step invokes this skill with a release manifest (issue numbers from scope-selection) instead of a user typing issue numbers directly, the Phase 5 label differs — see the "Auto-dev manifest detection" bullet under Phase 5 Action Policy below.
+
 ## Workflow Contract
 
 5-phase pipeline:
@@ -86,12 +88,13 @@ See R006 "Sensitive Path Handling" (CC v2.1.121+ direct-write convention).
 - Issue already resolved by commit → `gh issue close --reason "completed"` + resolving commit comment
 - Cross-analysis "Not Applicable" → `gh issue close --reason "not planned"`
 - Duplicate series → close older + `duplicate` label
-- All analysis complete → add `verify-done` label
+- All analysis complete → add `triage-complete` label (meaning: triaged but not selected in this auto-dev cycle — deferred/excluded, collected by release-plan; when this skill runs standalone rather than inside auto-dev's triage step, this is the label applied — manifest-selected issues inside auto-dev get `verify-ready` instead, #1734)
+- **Auto-dev manifest detection**: when the caller supplies a release manifest (the list of issue numbers selected by `pipeline auto-dev`'s scope-selection step) as this skill's issue-number argument, treat it as auto-dev context — label those manifest issues `verify-ready`, NOT `triage-complete`. With no manifest supplied (standalone `/professor-triage`, `--label`, `--state`, or `--since` invocation), apply the default `triage-complete` label per the bullet above.
 - Priority assigned → add `P1`/`P2`/`P3` label
 
 **Confirmation required** (high-risk): issue reopen, new issue creation, epic linking, issue body modification.
 
-**Ensure `verify-done` label exists**: `gh label create "verify-done" --color "0E8A16"` if missing.
+**Ensure `triage-complete` label exists**: `gh label create "triage-complete" --color "0E8A16"` if missing.
 
 ## Permission Mode
 

package/templates/.claude/skills/release-plan/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: release-plan
-description: Generate release-unit development plans from professor-triage completed (verify-done) issues, grouping by priority and size
+description: Generate release-unit development plans from professor-triage completed (triage-complete) issues, grouping by priority and size
 scope: harness
 user-invocable: true
 effort: medium
@@ -10,12 +10,12 @@ effort: medium
 
 ## Purpose
 
-Collects open GitHub issues labeled `verify-done` (triage-completed by `/professor-triage`), groups them into release units by priority and estimated size, and generates a structured release plan document. Plan only — no implementation, no commits.
+Collects open GitHub issues labeled `triage-complete` (triage-completed by `/professor-triage`), groups them into release units by priority and estimated size, and generates a structured release plan document. Plan only — no implementation, no commits.
 
 ## Usage
 
 ```
-/release-plan                    # Default: all verify-done open issues
+/release-plan                    # Default: all triage-complete open issues
 /release-plan --next minor       # Force minor version bump
 /release-plan --next patch       # Force patch version bump
 /release-plan --dry-run          # Print plan to stdout only, no file write
@@ -26,14 +26,14 @@ Collects open GitHub issues labeled `verify-done` (triage-completed by `/profess
 ### Phase 1: Collect Issues
 
 ```bash
-# Get all open issues labeled verify-done
-gh issue list --state open --label verify-done \
+# Get all open issues labeled triage-complete
+gh issue list --state open --label triage-complete \
   --json number,title,labels,body,createdAt
 ```
 
-If `verify-done` label returns 0 results, check label existence:
+If `triage-complete` label returns 0 results, check label existence:
 ```bash
-gh label list | grep verify-done
+gh label list | grep triage-complete
 ```
 Report if label is missing and stop.
 
@@ -81,10 +81,10 @@ Use title keywords as additional hints:
 - Epic references → group constraint
 
 **Epic handling**:
-- Epic issues (title starts with "epic:" or has `epic` label) with `verify-done` label:
+- Epic issues (title starts with "epic:" or has `epic` label) with `triage-complete` label:
   - Do NOT include the epic itself in release bins
   - DO scan epic body for child issue references (#NNN)
-  - Include any open child issues that have `verify-done` label
+  - Include any open child issues that have `triage-complete` label
   - If all child issues are closed, recommend closing the epic
 
 ### Phase 4: Group into Release Units
@@ -151,8 +151,8 @@ For each release group, produce:
 ### Completeness Check
 
 Before generating the plan document, verify:
-- Every verify-done issue is assigned to a release bin (none dropped)
-- Epic child issues with verify-done are included
+- Every triage-complete issue is assigned to a release bin (none dropped)
+- Epic child issues with triage-complete are included
 - Issue count in plan == issue count from Phase 1 collection (minus epics themselves)
 - No issue is deferred without explicit user approval
 
@@ -186,7 +186,7 @@ File header format:
 ```markdown
 # 릴리즈 계획 — YYYY-MM-DD 생성
 
-> 출처: YYYY-MM-DD 기준 `verify-done` 라벨 오픈 이슈
+> 출처: YYYY-MM-DD 기준 `triage-complete` 라벨 오픈 이슈
 > 제외된 이슈 (이미 오픈 PR에 포함): #NNN, #NNN
 
 {릴리즈 그룹}

package/templates/guides/professor-triage/README.md

@@ -17,7 +17,7 @@ The SKILL.md is intentionally thin — it carries only the workflow contract and
 ## Usage
 
 ```
-/professor-triage                          # Default: --state open (excludes verify-done)
+/professor-triage                          # Default: --state open (excludes triage-complete)
 /professor-triage 587 589 590 591 592      # Direct issue numbers
 /professor-triage --label codex-release    # Custom label filter
 /professor-triage --since 2026-03-20       # Date filter

package/templates/guides/professor-triage/phases.md

@@ -7,7 +7,7 @@ Companion to `guides/professor-triage/README.md`. Detailed workflow for each pha
 1. Parse arguments to determine target issues:
    - If issue numbers provided: use those directly
    - If `--label` provided: `gh issue list --label <label> --state <state> --json number`
-   - Default: `gh issue list --state open --json number` + exclude issues with `verify-done` label
+   - Default: `gh issue list --state open --json number` + exclude issues with `triage-complete` label
    - If `--since` provided: add `--search "created:>YYYY-MM-DD"` filter
 
 2. For each issue, fetch full details:
@@ -17,7 +17,7 @@ gh issue view NNN --json number,title,body,comments,labels,createdAt
 
 3. For batches >20 issues, prefer `gh api graphql` for batch fetching to respect GitHub API rate limits (5000/hour authenticated).
 
-4. If filter returns 0 results: if `--label` was used, check label existence via `gh label list`. Report if label missing. If default filter, report "No open issues without verify-done label found."
+4. If filter returns 0 results: if `--label` was used, check label existence via `gh label list`. Report if label missing. If default filter, report "No open issues without triage-complete label found."
 
 ## Phase 2: Codebase Analysis
 
@@ -293,7 +293,8 @@ Delegate ALL GitHub operations to mgr-gitnerd.
 | Phase 2 found issue already resolved (with commit evidence) | `gh issue close --reason "completed"` + comment with resolving commit |
 | Cross-analysis concludes "Not Applicable" / "no action needed" | `gh issue close --reason "not planned"` |
 | Cross-analysis detects same-series duplicates | Keep latest, close others + `duplicate` label |
-| All analysis complete | Add `verify-done` label |
+| All analysis complete (standalone triage, not selected this cycle) | Add `triage-complete` label |
+| All analysis complete (invoked within auto-dev's triage step, manifest-selected) | Add `verify-ready` label instead |
 | Priority assigned | Add `P1`/`P2`/`P3` label |
 
 ### Confirmation Required (high-risk)
@@ -307,7 +308,7 @@ Present to user and wait for approval before executing:
 | Epic/milestone linking | Propose link | Project structure change |
 | Issue body modification | Present edit draft | Respect original author intent |
 
-**Ensure `verify-done` label exists**: If not, create with `gh label create "verify-done" --color "0E8A16"`.
+**Ensure `triage-complete` label exists**: If not, create with `gh label create "triage-complete" --color "0E8A16"`.
 
 ## Phase Notes Summary
 

package/templates/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.82",
+  "version": "1.1.83",
   "lastUpdated": "2026-09-03",
   "omcustomMinClaudeCode": "2.1.121",
   "omcustomMinClaudeCodeReason": "Sensitive-path direct Write/Edit on .claude/** under bypassPermissions (R010 deprecation, #1101)",

package/templates/workflows/auto-dev.yaml

@@ -158,7 +158,7 @@ steps:
       Reference label semantics: .claude/skills/pipeline/labels.md
 
       Apply filter rules:
-      - EXCLUDE: blocked_by_decision == true OR labels ∩ {decision-needed, needs-review, verify-done, manual-action, in-progress} ≠ ∅
+      - EXCLUDE: blocked_by_decision == true OR labels ∩ {decision-needed, needs-review, triage-complete, manual-action, in-progress} ≠ ∅
       - INCLUDE (preferred): labels ∩ {verify-ready, claude-code-release, documentation} ≠ ∅
       - INCLUDE (standard): P1/P2/P3 issues not in excluded set
       - Tie-break: P1 > P2 > P3 > unclassified
@@ -237,6 +237,9 @@ steps:
         - triage step: skip professor-triage skill; perform direct manifest summary instead
         - plan step: skip release-plan skill; single-response plan instead
         - deep-plan step: skip deep-plan skill; single-response implementation notes instead
+          (except when scope contains a security/availability issue — see the Cross-tier
+          「Lightweight Skill-Mode Substitution」 restriction below, which forbids this
+          substitution for such issues)
         - deep-verify step: skip deep-verify skill; perform self-review checklist instead
           — 단, 변경 집합에 `.claude/rules/**`(또는 agents/skills frontmatter 등 구조 표면)가
           포함되면 self-review로 대체하지 않고 mgr-sauron R017 검증을 **단일 목표 위임으로 필수
@@ -262,6 +265,9 @@ steps:
         - triage step: MAY replace professor-triage skill spawn with orchestrator integrated analysis
         - plan step: MAY replace release-plan skill spawn with orchestrator integrated analysis
         - deep-plan step: MAY replace deep-plan skill spawn with orchestrator integrated analysis
+          (except when scope contains a security/availability issue — see the Cross-tier
+          「Lightweight Skill-Mode Substitution」 restriction below, which forbids this
+          substitution for such issues)
         - deep-verify step: perform via mgr-sauron R017 structural verification + core self-check (split standard: see the deep-verify step description — R017 spawn + change-type adversarial review, one single-goal delegation each)
           (instead of full deep-verify skill spawn). If the change set has NO structural surface
           (no agent/skill/guide/rule frontmatter changed — e.g. a workflow-yaml-only or docs-only change),
@@ -307,14 +313,14 @@ steps:
       | pre-triage | `gh label create in-progress / verify-ready / needs-review --force` (idempotent label bootstrap) |
       | scope-selection | Milestone 3-branch state machine (Step 0): closed → HALT / open → reuse / absent → `gh api repos/{owner}/{repo}/milestones --method POST`. Then: assign every scoped issue to that milestone. |
       | compression-mode-eval | none (pure evaluation + justification logs) |
-      | triage | none (analysis only) — compressible |
+      | triage | `verify-ready` added to manifest issues selected by professor-triage when it runs inside this step (NOT `triage-complete`) — analysis output is compressible, this label side effect is not; when triage is skipped (docs-only) or substituted (lite integrated-analysis, lightweight mode), no separate label action is required here — the implement step's per-issue success path (row below: "On success: remove in-progress, add verify-ready") already adds `verify-ready` to each processed issue before this release completes |
       | plan | none (analysis only) — compressible |
       | deep-plan | none (analysis only) — compressible |
       | implement | `gh issue edit <N> --add-label in-progress --assignee @me`; `gh issue comment <N>` (start notice); on success remove in-progress + add verify-ready; on failure remove in-progress + add needs-review + comment error summary |
       | verify-build | none (gate only) |
       | deep-verify | none (analysis only) — compressible |
       | release | PR body MUST carry `Closes #N` for every resolved issue (auto-tag.yml greps the PR body); non-auto-tag projects additionally: `gh api .../milestones/{n} --method PATCH --field state=closed`, `gh issue close {n}`, label needs-review issues "Deferred from v{version}" |
-      | ci-check | none (verification only) |
+      | ci-check | `gh issue edit <N> --remove-label in-progress` for stale labels; `gh issue edit <N> --remove-label verify-ready` for THIS release's CLOSED scoped issues only (past closed issues excluded, #1734) |
       | post-release-followup | new issue registration for release follow-ups (genuine defects auto-registered, no-ask per R016) |
 
       Only the rows marked "none (analysis only)" are compressible. Any step with a
@@ -366,6 +372,20 @@ steps:
          `mode: lightweight`) so downstream steps and reviewers can tell it apart from a full
          skill spawn (결과물에 모드를 표시, #1721 제안 4).
 
+      Additional restriction — security/availability scope (#1733 찐빠 #9): if ANY scoped issue
+      carries the `security` label, OR its title/body explicitly states a security/availability
+      concern (e.g. rate limiting, resource exhaustion, injection, denial-of-service — this repo
+      has no separate `availability` label; measured via `gh label list`, so an availability
+      concern must be asserted in the issue text, not inferred from a label), this lightweight
+      substitution is FORBIDDEN for deep-plan on that issue — AND compression-mode-eval Tier 2
+      lite's deep-plan integrated-analysis substitution is also FORBIDDEN for it; deep-plan MUST
+      run as a full skill spawn. Because deep-plan is a single release-scoped step (not run
+      per-issue), when ANY scoped issue qualifies, this restriction applies to the whole
+      release's deep-plan step. The entry-point audit for such an issue MUST include an
+      "executions per request (amplification)" check — how many downstream operations a single
+      request can trigger (e.g. GraphQL alias batching, N+1 fan-out) — not only a per-call
+      timeout/rate-limit check. (GraphQL document fuzz testing is OUT of scope here.)
+
       This substitution is NEVER available for implement, verify-build, release, ci-check, or
       deep-verify.
       It replaces analysis output ONLY — every step's state-change side effect still runs in
@@ -382,7 +402,7 @@ steps:
 
   - name: triage
     skill: professor-triage
-    description: "Cross-analysis triage with priority assessment (scoped to release manifest) — skipped if docs-only, integrated-analysis allowed if lite; independent of tier, MAY run in lightweight mode when compression-mode-eval's 'Cross-tier — Lightweight Skill-Mode Substitution' conditions are met"
+    description: "Cross-analysis triage with priority assessment (scoped to release manifest) — invoke professor-triage WITH the release manifest issue numbers from scope-selection's output as input; in this auto-dev context, manifest issues receive `verify-ready` (not `triage-complete`) per the side-effect inventory above — skipped if docs-only, integrated-analysis allowed if lite; independent of tier, MAY run in lightweight mode when compression-mode-eval's 'Cross-tier — Lightweight Skill-Mode Substitution' conditions are met"
     depends_on: compression-mode-eval
 
   - name: plan
@@ -448,6 +468,16 @@ steps:
         (#1701 #1). The orchestrator's own wiring judgement (which file/anchor already covers a
         new clause) counts as final wording too — the prompt supplies candidate files/anchors
         only, and the subagent decides coverage by quoting the covering sentence (R010 [#1704 #1]).
+        Non-issue sources (더루키 회상, 메모리, 다른 프로젝트 관측) MUST be placed in a separate
+        block labeled with its source (e.g. `[출처: 더루키 회상 — <project>]`) and MUST NOT be
+        mixed into issue-quote sentences — completion criteria MUST state this separation
+        explicitly, applying to every orchestrator-authored delegation, all tiers (R010 「출처
+        인용과 인접 문구 점검」 확장, #1735 찐빠 #1).
+      - A release that bundles ≥2 `feedback`-type issue proposals MUST produce a per-proposal
+        application-boundary table (exceptions, deadlines, tiers/steps) during plan/deep-plan or
+        its lightweight tier substitute, applying to lite and standard tiers, and
+        implement-stage delegation prompts MUST carry the relevant boundary row for each edit
+        (회고 제안 묶음 릴리즈의 통합 분석에 적용 경계 표 필수, #1735 찐빠 #4).
       - Before dispatching any delegation prompt in an iteration that created or reinforced a rule
         clause, the orchestrator MUST compare that clause's Anti-pattern table rows 1:1 against the
         delegation prompt's sentences and rewrite any match (cause: the R016 「신설 조항의 동일
@@ -488,6 +518,14 @@ steps:
         around it (e.g. via a shell glob or path rewrite) — it MUST stop and report the block
         verbatim (R010 「품질 게이트 우회 금지 — 훅 차단은 보고 대상」, extended here from git
         hooks to guards/classifiers/permissions generally) (#1728 찐빠 #1).
+      - No state-changing command (`gh issue create/edit/close`, `gh pr create/edit/close/merge`,
+        `git push`, label changes) — including the orchestrator's own direct commands, not only
+        delegated ones — MAY use a `||` fallback that prints success-looking output; the observed
+        failure mode was a failed `gh issue create` followed by a `||` fallback that printed a
+        DIFFERENT issue's URL, which the orchestrator briefly read as a successful create
+        (#1735 찐빠 #2). Exceptions: a `||` fallback whose output is explicitly marked as
+        failure (e.g. `|| echo "::warning::…"`, a literal `MISS` token) and idempotent bootstrap
+        commands (no `||` success masking) such as `gh label create --force 2>/dev/null`.
       - After any delegation that creates temporary files under constraint (h) above, the
         orchestrator MUST confirm with `git status --short` that no stray file was left in the
         repo (#1721 찐빠 #7).
@@ -496,7 +534,13 @@ steps:
         arithmetic below, not a replacement for it); compute turn arithmetic (files × 3 +
         edit_items × 2 ≤ 16 — a #1709-proposed guide kept below the 20-turn limit, not a
         truncation guarantee, per R020 「maxTurns 절단 실증」 6항) and state that arithmetic in
-        the delegation prompt before dispatch (#1709 #1).
+        the delegation prompt before dispatch (#1709 #1). Any edit delegation requiring
+        verification of N quotations or identifiers (not only claude-code-release CC-note
+        delegations) MUST perform that verification with batched command(s) (a single loop or
+        combined `grep -F` pass over all N items), never per-item invocations, and the turn
+        arithmetic above MUST add a batched-verification term — ⌈N/batch⌉ — still an
+        upper-bound guide that may still truncate, not a truncation guarantee (검증 비용을
+        턴 산술에 반영, R020 「maxTurns 절단 실증」 6항 확장, #1737 찐빠 #1).
       - Parity delegation prompts (e.g. a ko mirror tracking an en source) MUST require THREE
         directions — additions, edits, AND deletions — to match the source, never additions
         only; completion criteria MUST include a `grep -F` confirming zero rows/sentences are
@@ -523,6 +567,16 @@ steps:
         before restating either — do not relay an unverified agent-reported count or identifier
         (R023 「리서치 위임의 결론 수치는 표에서 재계산해 병기」 #1707 #4 확장, #1709 #5, #1722
         찐빠 #3).
+      - Delegations that create files, binaries, worktrees, or branches (artifact-creating
+        delegations only — text-only edits are excluded) MUST include measured output in their
+        completion report — `file <bin>` for binaries, `ls -la <path>` for created paths, `git
+        worktree list` for worktrees, `git branch --list` for branches, as applicable — and the
+        orchestrator MUST confirm architecture/path from that measured output before using the
+        artifact, not from the agent's self-report alone (R020 Subagent Self-Report
+        Verification, #1733 찐빠 #1). (#1733 찐빠 #1's third proposal — never use haiku for
+        worktree/cross-compile delegations — is not added separately here: R006
+        (`.claude/rules/MUST-agent-design.md`) already scopes `haiku` to "Fast, cheap tasks
+        (search, simple edits)", which excludes multi-step build/worktree work.)
       - Delegations that build or replace an evaluation/test harness or a production code path
         (fixtures, ablation lanes, scoring/oracle logic) MUST require bidirectional proof, not
         a single-direction pass: (a) positive AND negative fixtures — a fixture set that can
@@ -536,6 +590,14 @@ steps:
         measurement; (c) no working around a discovered product or measurement defect to force
         a pass — halt and report instead (R023 「Conditional-Output Verification」 양성/음성 짝
         원칙 확장, #1721 찐빠 #1, #1727 찐빠 #2, #1728 찐빠 #2).
+      - Delegations that inject faults / modify-then-restore files — not limited to harness
+        builds — MUST back up the original file under `bak/<repo-relative-path>` (the full
+        repo-relative path, not filename-only) nested under the session scratchpad or `$TMPDIR`
+        (not inside the repo, to stay consistent with constraint (h) above), and a checksum
+        comparison after restore is MANDATORY. A `git diff`-based patch approach is also allowed.
+        `git stash` is otherwise allowed EXCEPT when parallel delegations share the working tree
+        (R009 「File-Disjoint ≠ Independent (Local Git State)」), where it MUST NOT be used
+        (#1733 코멘트 찐빠 #8).
       - For `claude-code-release` issues, CC release knowledge goes to
         `guides/claude-code/15-version-compatibility.md` (+ templates mirror) per rule; a rule
         file gets at most ONE line of behavioral norm only when agent behavior must change.
@@ -638,6 +700,19 @@ steps:
     prompt: |
       Create a GitHub Release.
 
+      0a. User-execution constraint check (mandatory, before step 0, #1733 찐빠 #2): read
+          CLAUDE.md, session memory, and the entry card (if the environment provides one, e.g. a
+          recall entry card) for any user-execution constraint (e.g. "merge/tag/publish must be
+          run by the user, not the agent"). For each command this release step is about to run:
+          if it is COVERED by a constraint (merge, tag, publish), do NOT execute it — present the
+          exact command(s) to the user and STOP this step; if it is NOT covered (e.g. branch
+          creation, version bump, PR creation — coverage is judged by the scope of the constraint
+          text actually found in CLAUDE.md/session memory, not by this example list), proceed
+          normally. No matching constraint found → unchanged behavior, proceed to step 0. User decision
+          (recorded): in an unattended run (`/fsd` etc. — see pre-triage Phase 0.6
+          `unattended_mode`), STOP at the first covered command, present it to the user, and HOLD
+          the convergence declaration until the user runs it and confirms.
+
       0. Pre-check (mandatory, delegate to mgr-gitnerd per R010): Detect and remove stale local `release` branch if present.
          The local `release` branch (file ref) conflicts with `release/v*` directory ref namespace.
          mgr-gitnerd executes (force-delete acceptable in automation context; warns if branch has unpushed commits):
@@ -800,7 +875,11 @@ steps:
          in-progress`) and report the fix; if the issue is still OPEN, do NOT close it here —
          closing stays with auto-tag.yml unless it failed to close that issue, in which case
          report the open issue for manual close per release step 3.d above (#1722 하네스 제안
-         4).
+         4). Additionally, for each scoped issue that IS closed by THIS release, remove a
+         lingering `verify-ready` label if present (`gh issue edit <N> --remove-label
+         verify-ready`) — scoped to THIS release's closed issues only; bulk-removing
+         `verify-ready` from previously closed issues is explicitly excluded (user decision,
+         #1734).
       6. Report final CI status.
     description: "Post-release CI verification and fix loop"
     depends_on: release