oh-my-customcode 1.0.9 → 1.0.11

package/dist/cli/index.js

@@ -241,7 +241,7 @@ var init_package = __esm(() => {
     workspaces: [
       "packages/*"
     ],
-    version: "1.0.9",
+    version: "1.0.11",
     description: "Batteries-included agent harness for Claude Code",
     type: "module",
     bin: {
@@ -289,13 +289,13 @@ var init_package = __esm(() => {
       yaml: "^2.8.2"
     },
     devDependencies: {
-      "@anthropic-ai/sdk": "^0.102.0",
+      "@anthropic-ai/sdk": "^0.105.0",
       "@biomejs/biome": "^2.3.12",
       "@types/bun": "^1.3.6",
       "@types/js-yaml": "^4.0.9",
       "@types/nodemailer": "^8.0.0",
       "js-yaml": "^4.1.0",
-      nodemailer: "^8.0.1",
+      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.9",
+  version: "1.0.11",
   description: "Batteries-included agent harness for Claude Code",
   type: "module",
   bin: {
@@ -2079,13 +2079,13 @@ var package_default = {
     yaml: "^2.8.2"
   },
   devDependencies: {
-    "@anthropic-ai/sdk": "^0.102.0",
+    "@anthropic-ai/sdk": "^0.105.0",
     "@biomejs/biome": "^2.3.12",
     "@types/bun": "^1.3.6",
     "@types/js-yaml": "^4.0.9",
     "@types/nodemailer": "^8.0.0",
     "js-yaml": "^4.1.0",
-    nodemailer: "^8.0.1",
+    nodemailer: "^9.0.1",
     typescript: "^6.0.2",
     vitepress: "^1.6.4"
   },

package/package.json

@@ -3,7 +3,7 @@
   "workspaces": [
     "packages/*"
   ],
-  "version": "1.0.9",
+  "version": "1.0.11",
   "description": "Batteries-included agent harness for Claude Code",
   "type": "module",
   "bin": {
@@ -51,13 +51,13 @@
     "yaml": "^2.8.2"
   },
   "devDependencies": {
-    "@anthropic-ai/sdk": "^0.102.0",
+    "@anthropic-ai/sdk": "^0.105.0",
     "@biomejs/biome": "^2.3.12",
     "@types/bun": "^1.3.6",
     "@types/js-yaml": "^4.0.9",
     "@types/nodemailer": "^8.0.0",
     "js-yaml": "^4.1.0",
-    "nodemailer": "^8.0.1",
+    "nodemailer": "^9.0.1",
     "typescript": "^6.0.2",
     "vitepress": "^1.6.4"
   },

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

@@ -44,6 +44,8 @@ This is a settings-level resilience mechanism, distinct from the per-agent `mode
 
 > **v2.1.166+**: `MAX_THINKING_TOKENS=0`, `--thinking disabled`, and the per-model thinking toggle disable thinking on models that think by default via the Claude API (3rd-party providers unchanged). Relevant when an agent's `effort` is low and thinking overhead is undesirable.
 
+> **v2.1.183+**: CC now warns (stderr, in `-p` print mode) when the requested model is deprecated or auto-updated to a newer model — and this warning now ALSO covers models set in agent frontmatter (`model:`). Relevant to the Model Aliases table above: a stale/deprecated `model:` value in agent frontmatter now surfaces a deprecation warning instead of silently resolving. Separately, v2.1.183 fixes `thinking.disabled.display: Extra inputs are not permitted` 400 errors on subagent spawns and session-title generation — extends the v2.1.166 toggle above; subagent spawns with thinking disabled no longer 400.
+
 ### Safe Mode & Bundled Skill Control (CC v2.1.169+)
 
 > **v2.1.169+**: `--safe-mode` (and `CLAUDE_CODE_SAFE_MODE`) starts Claude Code with ALL customizations disabled (CLAUDE.md, plugins, skills, hooks, MCP servers) — use it to isolate whether a project customization (agent/skill/hook) causes a regression. The `disableBundledSkills` setting (and `CLAUDE_CODE_DISABLE_BUNDLED_SKILLS` env) hides bundled skills, workflows, and built-in slash commands from the model — useful when bundled skills conflict with or duplicate project skills (R006 skill-surface management). Note: `disableBundledSkills` hides skills from the model but is a CC platform setting, distinct from the advisory `skills:` frontmatter field (which is documentation metadata, not a runtime allowlist).

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

@@ -48,6 +48,8 @@ These are distinct mechanisms. Agent Teams `SendMessage` requires `TeamCreate` a
 
 This hardens cross-session coordination (claude-peers-mcp `send_message`, see Scope table above) against privilege escalation — a relayed message from session A cannot grant session B permissions the user did not authorize on B. Aligns with R001 (credential/privileged-scope guardrails) and R010 (out-of-scope privileged chaining). Intra-session Agent Teams `SendMessage` between peers in the same session is unaffected.
 
+> **v2.1.183+**: Fixed tmux teammate panes failing to launch when the shell has slow rc-file initialization — a slow `.zshrc`/`.bashrc` no longer prevents Agent Teams teammate panes from launching in tmux. Also fixed WebSearch returning empty results in subagents: a subagent (including a Teams member) using WebSearch now returns results instead of silently empty.
+
 ## Self-Check (Before Agent Tool)
 
 Before using Agent tool for 2+ agent tasks, complete this check:

package/templates/.claude/rules/MUST-orchestrator-coordination.md

@@ -323,6 +323,8 @@ Before spawning any agent:
 
 > **v2.1.178+**: Fixed `claude agents` workers failing with `401 Invalid bearer token` when the daemon was started from a shell with a custom API gateway (`ANTHROPIC_BASE_URL` + `ANTHROPIC_AUTH_TOKEN`). Further hardens background-agent provider isolation (cf. v2.1.174 ANTHROPIC_* env isolation). Also fixed `/bg`-created background sessions showing "Working" forever after a turn finished. `mode: "bypassPermissions"` on every Agent tool call remains required regardless.
 
+> **v2.1.181+**: Fixed prompt caching not reading on a custom `ANTHROPIC_BASE_URL` (and on Foundry) due to a per-request attestation token changing every turn. Further strengthens background-agent provider isolation (cf. v2.1.174 ANTHROPIC_* env isolation, v2.1.178 401 bearer-token fix): a `/bg`-dispatched or custom-gateway session now benefits from prompt caching instead of paying a cache miss every turn. Separately, v2.1.179 fixed remote-session background tasks appearing stuck as "still running" between turns. `mode: "bypassPermissions"` on every Agent tool call remains required regardless.
+
 ## Agent Capability Pre-Check
 
 Before delegating a task to a subagent, MUST verify the target agent's tool capabilities against the task requirements. Failure to pre-check causes round-trip waste (delegation → failure → re-delegation).

package/templates/.claude/rules/MUST-permissions.md

@@ -47,6 +47,8 @@ Use a `"*"` deny rule in `settings.json` to enforce a deny-by-default posture, t
 
 > **v2.1.178+**: Permission rules now support `Tool(param:value)` syntax to match a tool's input parameters, with `*` wildcard — e.g. `Agent(model:opus)` denies Opus subagents, or a parameter glob to constrain a tool's arguments. This extends the v2.1.166 tool-name glob support down to per-parameter granularity. Relevant to the Agent Tool Permission Mode below: a deny rule can now block specific subagent models/parameters at the platform level, complementing `availableModels` (R006) and the universal `mode: "bypassPermissions"` requirement (R010). A `Agent(model:...)` parameter deny is evaluated by the CC platform independent of the advisory tier table.
 
+> **v2.1.183+**: Fixed MCP servers requiring authentication exposing auth-stub tools to the model in headless/SDK mode — unauthenticated MCP auth-stub tools are no longer surfaced to the model in `-p` / SDK runs (they would fail on call). Relevant to the Tier-6 MCP tier: a headless run no longer offers auth-stub MCP tools. Separately, v2.1.181 added the `sandbox.allowAppleEvents` opt-in setting, letting sandboxed commands send Apple Events on macOS (default off) — a deliberate sandbox-scope widening, complementing the Tier-based policy above.
+
 ## Agent Tool Permission Mode
 
 When spawning subagents via the Agent tool, always pass `mode: "bypassPermissions"` explicitly. The Agent tool's default mode is `acceptEdits`, which **overrides** the agent frontmatter `permissionMode` field.

package/templates/.claude/rules/MUST-safety.md

@@ -25,6 +25,8 @@ The following git commands have caused working tree loss in past sessions (#1146
 
 **Recovery hint**: If working tree loss occurs, check `git reflog` immediately — most operations are recoverable within 30 days.
 
+> **v2.1.183+**: Auto mode now BLOCKS destructive git commands at the platform level — `git reset --hard`, `git checkout -- .`, `git clean -fd`, and `git stash drop` are blocked when you did not ask to discard local work; `git commit --amend` is blocked when the commit was not made by the agent this session; and `terraform destroy` / `pulumi destroy` / `cdk destroy` are blocked unless you asked for the specific stack. This is the PLATFORM-level complement to this section's (advisory) per-invocation approval requirement and the Pre-Delegation Blast-Radius Enumeration below: the model still enumerates discard targets and requests approval (model-level), and CC now also hard-blocks the destructive command itself in auto mode (platform-level) — defense-in-depth. The advisory approval requirement remains because the platform block gates the COMMAND, not the blast-radius enumeration the user needs for an informed decision.
+
 ### Pre-Delegation Blast-Radius Enumeration
 
 > Origin: #1307 찐빠 #1 (High) — user chose "discard local changes and pull", and `git reset --hard origin/develop` was delegated immediately → user rejected (interrupt). The blast radius — that "discard local changes" included 18 files of *intended* uncommitted work (rule edits, new skills, new guides), not just a version downgrade — was never enumerated for the user.

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

@@ -37,25 +37,50 @@ FSD expands into:
 2. **`/loop` recurrence** — self-paced loop (model decides cadence), each iteration runs:
    1. `/pipeline auto-dev` — full release pipeline for the next eligible issue
    2. `/homework` — retrospective 찐빠 audit gate
+   3. **Open PR processing** — merge or defer all open PRs before checking convergence
 
 ### Loop Convergence
 
-The loop converges naturally when the auto-dev-eligible issue set reaches 0. Issue eligibility follows `/pipeline auto-dev` label selection exactly:
+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
+
+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
 
 Do NOT invent new label logic here — defer to the `pipeline` skill's auto-dev issue selection.
 
+### PR Processing Rules
+
+When open PRs are found during an iteration:
+
+| PR state | Action |
+|----------|--------|
+| CI passing, auto-mergeable | Merge via mgr-gitnerd (R010) |
+| CI failing with known pattern (e.g., dependabot frozen-lockfile cascade → `bun install` lockfile regeneration) | Fix CI, then merge |
+| CI failing with unknown cause | Diagnose; if fixable within iteration, fix and merge; otherwise defer |
+| Breaking change / design judgment required | Defer and surface to user |
+| Explicitly excluded by user this session | Skip (honor directive persistence, R015) |
+
+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.
+
 ### Iteration Flow (per iteration)
 
 ```
 [FSD Iteration N]
 ├── /pipeline auto-dev        → one release (PR create → merge → npm publish → milestone close)
 ├── /homework                 → extract 찐빠, confirm gate (or --dry-run if requested)
-└── Check: any eligible issues remain?
-    ├── YES → next iteration
-    └── NO  → [FSD Done] converged naturally
+├── Open PR processing        → for each open PR: merge (if CI-green + auto-mergeable)
+│                                                  fix-then-merge (known CI failure pattern)
+│                                                  defer+surface (design decision needed)
+└── Check convergence: eligible issues = 0 AND open PRs = 0 (merged or deferred)?
+    ├── YES → [FSD Done] converged naturally
+    └── NO  → next iteration
 ```
 
 ## Safety and Discipline
@@ -64,11 +89,12 @@ Each iteration operates under full project rules — no relaxation because FSD i
 
 | Rule | Applies |
 |------|---------|
-| R001 (safety) | Destructive ops still require explicit approval. Credential guardrails always active. |
+| R001 (safety) | Destructive ops still require explicit approval. Credential guardrails always active. PR merges that risk data loss require explicit approval. |
 | R009 (parallel) | Independent subtasks within each pipeline iteration run in parallel. |
-| R010 (orchestration) | All file modifications delegated to specialist subagents. mgr-gitnerd for git ops. |
+| R010 (orchestration) | All file modifications delegated to specialist subagents. mgr-gitnerd for git ops including PR merges. |
+| R015 (intent persistence) | If user explicitly defers a specific PR this session, honor that deferral — do not retry it. |
 | R017 (sync verification) | mgr-sauron passes required before any commit. |
-| R020 (completion verification) | Each release verified via `npm view`, `gh release view`, closed issues before `[Done]`. |
+| R020 (completion verification) | Each release verified via `npm view`, `gh release view`, closed issues before `[Done]`. PR merges verified via `gh pr view` ground-truth before declaring iteration complete. |
 
 `/homework` runs as a **retrospective gate** between iterations — findings go through `omcustom-feedback`'s Phase 4A confirmation gate. The loop does NOT skip homework on the grounds that it is "automated". If homework requires user confirmation (e.g., to file a feedback issue), the loop pauses and waits.
 
@@ -119,11 +145,13 @@ That session ran 2 iterations (v0.177.0 and v0.178.0) before converging with 0 e
 | `omcustom-loop` | Session auto-continuation via SubagentStop hook — keeps the loop alive during background agent work |
 | `pipeline` | `/pipeline auto-dev` — the core release pipeline per iteration |
 | `homework` | Retrospective 찐빠 audit gate per iteration |
-| R001 (safety) | Destructive ops require approval; credential guardrails |
+| `mgr-gitnerd` | PR merge operations — all open PR merges delegated here (R010) |
+| R001 (safety) | Destructive ops require approval; credential guardrails; risky PR merges require explicit approval |
 | R009 (parallel execution) | Parallel subtasks within each pipeline iteration |
-| R010 (orchestrator coordination) | All file writes delegated; mgr-gitnerd for git |
+| R010 (orchestrator coordination) | All file writes delegated; mgr-gitnerd for git including PR merges |
+| R015 (intent persistence) | User PR deferral decisions honored for the session |
 | R017 (sync verification) | mgr-sauron required before commit/push |
-| R020 (completion verification) | Actual outcome verified before declaring each release done |
+| R020 (completion verification) | Actual outcome verified before declaring each release or PR merge done |
 
 ## Design Notes
 
@@ -132,6 +160,7 @@ This skill is intentionally a **thin alias**. It does NOT duplicate:
 - Loop cadence / auto-continuation (owned by `omcustom-loop` + SubagentStop hook)
 - Release pipeline steps (owned by `pipeline auto-dev`)
 - Retrospective analysis (owned by `homework`)
+- PR merge execution (owned by `mgr-gitnerd`)
 - Completion verification (owned by R020 + `goal`)
 
 If any of those underlying skills evolve, FSD automatically benefits — its only responsibility is declaring the intent and forwarding to the right components.

package/templates/manifest.json

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