oh-my-customcode 1.1.87 → 1.1.89

package/dist/cli/index.js

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

package/package.json

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

package/templates/.claude/agents/agora-runner.md

@@ -1,7 +1,7 @@
 ---
 name: agora-runner
 description: Executes exactly one agora session step (start, one round, or finish) via the skill scripts and returns only a verdict summary. Never returns reviewer text, vendor attribution or sealed paths.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 tools: [Bash, Read, Write, Glob]
 skills: [agora]
 ---

package/templates/.claude/agents/arch-documenter.md

@@ -1,7 +1,7 @@
 ---
 name: arch-documenter
 description: Use for generating architecture documentation, API specifications (OpenAPI), Architecture Decision Records (ADRs), technical diagrams (Mermaid/PlantUML), and README maintenance
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: universal
 memory: local
 effort: medium

package/templates/.claude/agents/arch-speckit-agent.md

@@ -1,7 +1,7 @@
 ---
 name: arch-speckit-agent
 description: Use for spec-driven development, transforming requirements into executable specifications, defining project constitution, creating technical plans, and generating TDD task lists
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: universal
 memory: local
 effort: high

package/templates/.claude/agents/be-django-expert.md

@@ -1,7 +1,7 @@
 ---
 name: be-django-expert
 description: Expert Django developer for production-ready Python web applications. Use for Django projects, models/views/templates, Django REST Framework, authentication, admin customization, and deployment optimization.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: backend
 memory: local
 effort: high

package/templates/.claude/agents/be-express-expert.md

@@ -1,7 +1,7 @@
 ---
 name: be-express-expert
 description: Expert Express.js developer for production-ready Node.js APIs following security best practices and 12-factor app principles. Use for Express.js APIs, REST API architectures, middleware chains, authentication/authorization, security hardening, and Node.js performance optimization.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: backend
 memory: local
 effort: high

package/templates/.claude/agents/be-fastapi-expert.md

@@ -1,7 +1,7 @@
 ---
 name: be-fastapi-expert
 description: Expert FastAPI developer for building high-performance async Python APIs. Use for FastAPI projects, Python async/await patterns, Pydantic models, API architecture design, and performance optimization.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: backend
 memory: local
 effort: high

package/templates/.claude/agents/be-go-backend-expert.md

@@ -1,7 +1,7 @@
 ---
 name: be-go-backend-expert
 description: Expert Go backend developer for production-ready services following Uber style guide and standard layout. Use for Go backend services, HTTP/gRPC servers, microservices in Go, concurrent systems, and Go performance optimization.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: backend
 memory: local
 effort: high

package/templates/.claude/agents/be-nestjs-expert.md

@@ -1,7 +1,7 @@
 ---
 name: be-nestjs-expert
 description: Expert NestJS developer for opinionated, scalable Node.js applications with TypeScript. Use for NestJS projects, decorator-based patterns (@Injectable, @Module, @Controller), enterprise API architectures, authentication/authorization guards, DTO validation, and modular architecture.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: backend
 memory: local
 effort: high

package/templates/.claude/agents/be-springboot-expert.md

@@ -1,7 +1,7 @@
 ---
 name: be-springboot-expert
 description: Expert Spring Boot 4.0 developer for enterprise-grade Java 25 LTS applications. Use for Spring Boot projects, Java/Kotlin enterprise apps, RESTful APIs, microservices architecture, Spring Data, security patterns, virtual threads, and GraalVM native images.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: backend
 memory: local
 effort: high

package/templates/.claude/agents/db-alembic-expert.md

@@ -1,7 +1,7 @@
 ---
 name: db-alembic-expert
 description: Alembic migration specialist for generating, reviewing, fixing, and advising on SQLAlchemy database migrations
-model: claude-opus-5
+model: claude-opus-5-5
 domain: backend
 memory: local
 effort: high

package/templates/.claude/agents/db-postgres-expert.md

@@ -1,7 +1,7 @@
 ---
 name: db-postgres-expert
 description: Expert PostgreSQL DBA for pure PostgreSQL environments. Use for database design, query optimization, indexing strategies, partitioning, replication, PG-specific SQL syntax, and performance tuning without Supabase dependency.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: backend
 memory: user
 effort: high

package/templates/.claude/agents/db-redis-expert.md

@@ -1,7 +1,7 @@
 ---
 name: db-redis-expert
 description: Expert Redis developer for caching strategies, data structure design, Pub/Sub messaging, Streams, Lua scripting, and cluster management. Use for Redis configuration, performance optimization, and in-memory data architecture.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: backend
 memory: user
 effort: medium

package/templates/.claude/agents/db-supabase-expert.md

@@ -1,7 +1,7 @@
 ---
 name: db-supabase-expert
 description: Supabase and PostgreSQL expert. Use when working with Supabase projects, writing SQL queries, designing database schemas, configuring Row-Level Security (RLS), optimizing Postgres performance, or managing connection pooling. Handles .sql files and Supabase configuration.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: backend
 memory: user
 effort: high

package/templates/.claude/agents/de-airflow-expert.md

@@ -1,7 +1,7 @@
 ---
 name: de-airflow-expert
 description: Expert Apache Airflow developer for DAG authoring, testing, and debugging. Use for DAG files (*.py in dags/), airflow.cfg, Airflow-related keywords, scheduling patterns, and pipeline orchestration.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: data-engineering
 memory: local
 effort: high

package/templates/.claude/agents/de-dbt-expert.md

@@ -1,7 +1,7 @@
 ---
 name: de-dbt-expert
 description: Expert dbt developer for SQL modeling, testing, and documentation. Use for dbt model files (*.sql in models/), schema.yml, dbt_project.yml, dbt-related keywords, and analytics engineering workflows.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: data-engineering
 memory: local
 effort: medium

package/templates/.claude/agents/de-kafka-expert.md

@@ -1,7 +1,7 @@
 ---
 name: de-kafka-expert
 description: Expert Apache Kafka developer for event streaming, topic design, and producer-consumer patterns. Use for Kafka configs, streaming applications, event-driven architectures, and message broker design.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: data-engineering
 memory: local
 effort: high

package/templates/.claude/agents/de-pipeline-expert.md

@@ -1,7 +1,7 @@
 ---
 name: de-pipeline-expert
 description: Expert data pipeline architect for ETL/ELT design, orchestration patterns, data quality, and cross-tool integration. Use for pipeline architecture decisions, data quality frameworks, lineage tracking, and multi-tool coordination.
-model: claude-opus-5
+model: claude-opus-5-5
 domain: data-engineering
 memory: local
 effort: high

package/templates/.claude/agents/de-snowflake-expert.md

@@ -1,7 +1,7 @@
 ---
 name: de-snowflake-expert
 description: Expert Snowflake developer for cloud data warehouse design, query optimization, and data loading. Use for Snowflake SQL, warehouse configuration, clustering keys, data sharing, and Iceberg table integration.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: data-engineering
 memory: local
 effort: medium

package/templates/.claude/agents/de-spark-expert.md

@@ -1,7 +1,7 @@
 ---
 name: de-spark-expert
 description: Expert Apache Spark developer for PySpark and Scala distributed data processing. Use for Spark jobs (*.py, *.scala), spark-submit configs, Spark-related keywords, and large-scale data transformation.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: data-engineering
 memory: local
 effort: high

package/templates/.claude/agents/fe-design-expert.md

@@ -1,7 +1,7 @@
 ---
 name: fe-design-expert
 description: Use for design system review, typography audit, color palette evaluation, motion design, and AI-generated design quality assessment
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: frontend
 memory: local
 effort: medium

package/templates/.claude/agents/fe-flutter-agent.md

@@ -1,7 +1,7 @@
 ---
 name: fe-flutter-agent
 description: Use for Flutter/Dart cross-platform app development, widget composition, state management (Riverpod/BLoC), and performance optimization
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: frontend
 memory: local
 effort: medium

package/templates/.claude/agents/fe-svelte-agent.md

@@ -1,7 +1,7 @@
 ---
 name: fe-svelte-agent
 description: Use for Svelte compiler-based reactivity, reactive statements ($:), Svelte stores, and SvelteKit full-stack development with SSR
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: frontend
 memory: local
 effort: medium

package/templates/.claude/agents/fe-vercel-agent.md

@@ -1,7 +1,7 @@
 ---
 name: fe-vercel-agent
 description: Use for React/Next.js optimization, web design review (accessibility, UX), Vercel deployment automation, and bundle size optimization
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: frontend
 memory: local
 effort: medium

package/templates/.claude/agents/fe-vuejs-agent.md

@@ -1,7 +1,7 @@
 ---
 name: fe-vuejs-agent
 description: Use for Vue 3 Composition API development, single-file components, Pinia state management, and Vue Router navigation
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: frontend
 memory: local
 effort: medium

package/templates/.claude/agents/infra-aws-expert.md

@@ -1,7 +1,7 @@
 ---
 name: infra-aws-expert
 description: Use for AWS architecture design with Well-Architected Framework, infrastructure as code (CloudFormation/CDK/Terraform), VPC networking, IAM security, and cost optimization
-model: claude-opus-5
+model: claude-opus-5-5
 domain: devops
 memory: user
 effort: high

package/templates/.claude/agents/infra-docker-expert.md

@@ -1,7 +1,7 @@
 ---
 name: infra-docker-expert
 description: Use for creating optimized Dockerfiles, multi-stage builds, container security hardening, Docker Compose configurations, and image size optimization
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: devops
 memory: user
 effort: medium

package/templates/.claude/agents/lang-golang-expert.md

@@ -1,7 +1,7 @@
 ---
 name: lang-golang-expert
 description: Expert Go developer for writing idiomatic, performant Go code. Use for Go files (*.go, go.mod, go.sum), Go-related keywords, implementing concurrent systems, reviewing Go code, and optimizing Go applications.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: backend
 memory: local
 effort: high

package/templates/.claude/agents/lang-java-expert.md

@@ -1,7 +1,7 @@
 ---
 name: lang-java-expert
 description: Expert Java 25 LTS developer for modern Java with Virtual Threads, Pattern Matching, Record Patterns, and Sequenced Collections. Use for Java files (*.java, pom.xml, build.gradle), Java-related keywords, high-concurrency systems, data-centric APIs with Records, and migrating from older Java versions.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: backend
 memory: local
 effort: medium

package/templates/.claude/agents/lang-kotlin-expert.md

@@ -1,7 +1,7 @@
 ---
 name: lang-kotlin-expert
 description: Expert Kotlin developer for writing idiomatic, concise, null-safe Kotlin code. Use for Kotlin files (*.kt, *.kts), Kotlin-related keywords, Android development, Kotlin multiplatform projects, and migrating Java to Kotlin.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: backend
 memory: local
 effort: high

package/templates/.claude/agents/lang-python-expert.md

@@ -1,7 +1,7 @@
 ---
 name: lang-python-expert
 description: Expert Python developer for writing Pythonic, clean code following PEP 8. Use for Python files (*.py, requirements.txt, pyproject.toml), Python-related keywords, designing Python APIs, reviewing Python code, and optimizing Python applications.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: backend
 memory: local
 effort: high

package/templates/.claude/agents/lang-rust-expert.md

@@ -1,7 +1,7 @@
 ---
 name: lang-rust-expert
 description: Expert Rust developer for writing safe, performant, idiomatic Rust code. Use for Rust files (*.rs, Cargo.toml), Rust-related keywords, designing safe APIs, debugging ownership/lifetime issues, and implementing high-performance systems.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: backend
 memory: local
 effort: high

package/templates/.claude/agents/lang-typescript-expert.md

@@ -1,7 +1,7 @@
 ---
 name: lang-typescript-expert
 description: Expert TypeScript developer for writing type-safe, maintainable, scalable TypeScript code. Use for TypeScript files (*.ts, *.tsx, tsconfig.json), TypeScript-related keywords, designing APIs with type contracts, migrating JavaScript to TypeScript, and Node.js backend services.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: backend
 memory: local
 effort: high

package/templates/.claude/agents/mgr-claude-code-bible.md

@@ -1,7 +1,7 @@
 ---
 name: mgr-claude-code-bible
 description: Fetches latest Claude Code official documentation from code.claude.com and verifies agents/skills compliance against the official spec. Use when you need to check official Claude Code documentation or verify frontmatter fields.
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: universal
 memory: local
 effort: medium

package/templates/.claude/agents/mgr-creator.md

@@ -1,7 +1,7 @@
 ---
 name: mgr-creator
 description: Use when you need to create new agents following design guidelines. Automatically researches authoritative references before agent creation to ensure high-quality knowledge base
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: universal
 memory: local
 effort: high
@@ -50,7 +50,7 @@ When invoked as routing fallback (not explicit `/create-agent`):
 3. Auto-connect: scan `guides/` for relevant reference docs
 4. Create minimal viable agent with:
    - Detected skills and relevant guides
-   - `claude-sonnet-5` model (default; Tier 2 full model ID — CC does not resolve invented version-suffixed aliases, use the full ID per R006)
+   - `claude-sonnet-5-5` model (default; Tier 2 full model ID — CC does not resolve invented version-suffixed aliases, use the full ID per R006)
    - `project` memory scope
 5. Agent is persisted (not ephemeral) for future reuse
 

package/templates/.claude/agents/mgr-gitnerd.md

@@ -1,7 +1,7 @@
 ---
 name: mgr-gitnerd
 description: Use when you need to handle Git operations and GitHub workflow management, including commits, branches, PRs, and history management following best practices
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: universal
 memory: local
 effort: medium

package/templates/.claude/agents/mgr-sauron.md

@@ -1,7 +1,7 @@
 ---
 name: mgr-sauron
 description: Use when you need automated verification of R017 compliance, executing mandatory multi-round verification (5 manager rounds + 3 deep review rounds, with rounds 3-4 conditionally skipped when rounds 1-2 return 0 issues) before commits
-model: claude-opus-5
+model: claude-opus-5-5
 domain: universal
 memory: local
 effort: medium

package/templates/.claude/agents/mgr-updater.md

@@ -1,7 +1,7 @@
 ---
 name: mgr-updater
 description: Use when you need to update external agents, skills, and guides from their upstream sources, checking versions and applying updates
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: universal
 memory: local
 effort: medium

package/templates/.claude/agents/qa-engineer.md

@@ -1,7 +1,7 @@
 ---
 name: qa-engineer
 description: Use when you need to execute tests based on detailed plans and documentation, perform manual and automated testing, report defects, and validate fixes
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: universal
 memory: local
 effort: medium

package/templates/.claude/agents/qa-planner.md

@@ -1,7 +1,7 @@
 ---
 name: qa-planner
 description: Use when you need to create detailed QA plans from requirements and specifications, including test strategy design, risk-based prioritization, test scenario identification, and acceptance criteria definition
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: universal
 memory: local
 effort: high

package/templates/.claude/agents/qa-writer.md

@@ -1,7 +1,7 @@
 ---
 name: qa-writer
 description: Use when you need to create comprehensive QA documentation from detailed plans, including test cases, test reports, and quality documentation
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: universal
 memory: local
 effort: medium

package/templates/.claude/agents/sec-codeql-expert.md

@@ -1,7 +1,7 @@
 ---
 name: sec-codeql-expert
 description: Expert security code analyst using CodeQL for vulnerability detection, call graph analysis, and SARIF output. Use for security audits, CVE triage, code pattern analysis, and vulnerability validation.
-model: claude-opus-5
+model: claude-opus-5-5
 effort: high
 domain: devops
 memory: local

package/templates/.claude/agents/slack-cli-expert.md

@@ -1,7 +1,7 @@
 ---
 name: slack-cli-expert
 description: Expert Slack CLI developer for Slack app management, deployment, triggers, and workspace automation
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: universal
 effort: medium
 tools:

package/templates/.claude/agents/sys-memory-keeper.md

@@ -1,7 +1,7 @@
 ---
 name: sys-memory-keeper
 description: Use when you need to manage session memory persistence via native auto-memory, save context before compaction, restore context on session start, collect session summaries, or perform session-end memory operations
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: universal
 memory: local
 effort: medium

package/templates/.claude/agents/tool-bun-expert.md

@@ -1,7 +1,7 @@
 ---
 name: tool-bun-expert
 description: Use for Bun runtime development, bunfig.toml configuration, Bun test runner, fast bundling, and Node.js to Bun migrations
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: universal
 memory: local
 effort: medium

package/templates/.claude/agents/tool-npm-expert.md

@@ -1,7 +1,7 @@
 ---
 name: tool-npm-expert
 description: Use for npm package publishing workflows, semantic versioning (major/minor/patch), package.json optimization, and dependency audits
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: universal
 memory: local
 effort: medium

package/templates/.claude/agents/tool-optimizer.md

@@ -1,7 +1,7 @@
 ---
 name: tool-optimizer
 description: Use for bundle size analysis, tree-shaking verification, performance profiling, dead code detection, and build optimization recommendations
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 domain: universal
 memory: local
 effort: medium

package/templates/.claude/agents/wiki-curator.md

@@ -1,7 +1,7 @@
 ---
 name: wiki-curator
 description: Dedicated wiki page CRUD agent — creates, updates, and maintains wiki/ markdown pages for the codebase knowledge base
-model: claude-sonnet-5
+model: claude-sonnet-5-5
 tools:
   - Read
   - Write

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

@@ -40,14 +40,15 @@ Tier를 섞으면(예: frontmatter에 Tier-3 전용 값을 쓰거나 그 반대)
 | `opusplan` | Opus + plan mode; architecture planning with approval gates |
 | `inherit` | Inherit the parent session's model |
 
-**CC resolves these, not this project.** This project cannot "pin" an alias to a specific version — measured: a frontmatter `model: sonnet` agent executed as `claude-sonnet-5` (CC v2.1.197+ default), not a project-fixed `claude-sonnet-4-6`. Treat any "currently resolves to X" statement as a snapshot that changes when CC's own default changes.
+**CC resolves these, not this project.** This project cannot "pin" an alias to a specific version — measured: a frontmatter `model: sonnet` agent executed as `claude-sonnet-5` (the v2.1.197-era default), not a project-fixed `claude-sonnet-4-6`. Treat any "currently resolves to X" statement as a snapshot that changes when CC's own default changes.
 
 #### Tier 2 — Full model IDs (frontmatter `model:` ONLY — recommended for stability)
 
 | Full ID | Use Case |
 |---------|----------|
 | `claude-haiku-4-5` | Fast, cheap tasks |
-| `claude-sonnet-5` | Native 1M context; current CC default Sonnet (v2.1.197+) |
+| `claude-sonnet-5` | Native 1M context; previous-generation Sonnet (v2.1.197+; on the Anthropic API, `claude-sonnet-5-5` is now the default Sonnet model, v2.1.284+) |
+| `claude-sonnet-5-5` | Now the default Sonnet model on the Anthropic API (v2.1.284+); 1M context, $2/$10 per Mtok, $0.20/Mtok cache reads |
 | `claude-opus-4-6` | Opus, previous generation |
 | `claude-opus-4-8` | Opus, previous generation; supports xhigh effort |
 | `claude-opus-5` | Opus, previous generation (GA); native 1M context, fast mode at $10/$50 per Mtok |
@@ -55,7 +56,7 @@ Tier를 섞으면(예: frontmatter에 Tier-3 전용 값을 쓰거나 그 반대)
 | `claude-fable-5` | Mythos-class; tier above Opus (access via CC v2.1.170+) |
 | `claude-fable-5-1` | Mythos-class; Fable 5.1 — v2.1.257부터 기본 Fable 모델, 1M context |
 
-Full IDs are valid ONLY in agent frontmatter — the Agent tool's `model:` spawn parameter does NOT accept them (see Tier 3). Writing the full ID directly (not a project-invented shorthand) pins the agent regardless of future CC default changes. This is the recommended way to opt into Sonnet 5 / Opus 5 / Fable 5 explicitly rather than riding CC's Tier-1 default resolution.
+Full IDs are valid ONLY in agent frontmatter — the Agent tool's `model:` spawn parameter does NOT accept them (see Tier 3). Writing the full ID directly (not a project-invented shorthand) pins the agent regardless of future CC default changes. This is the recommended way to opt into Sonnet 5.5 / Opus 5.5 / Fable 5 explicitly rather than riding CC's Tier-1 default resolution.
 
 Extended context suffix: `[1m]` (e.g., `claude-opus-4-6[1m]`) — enables 1M token context window.
 
@@ -80,7 +81,7 @@ Skill/rule text instructing "spawn with `model: opus`" refers to this tier — a
 
 > **v2.1.233+**: print 모드(`-p`) 진단이 추가되어, Claude Code가 **인식하지 못하는 model ID**로 요청이 나가면 stderr에 `[claude-code:unrecognized_model]` 라인이 기록됩니다(`modelOverrides`로 매핑하면 억제). 구버전에서는 오타·폐기된 full ID가 **무음으로 fallback 해석**되어 "frontmatter에 적힌 모델 = 실제 실행 모델"이라는 전제가 검증 불가능했습니다 — 위 v2.1.223 강등 경고와 같은 계열의 **관측성 보강**이며, 이 저장소는 다수 에이전트가 Tier-2 full ID를 쓰므로 `-p` 실행 시 이 라인 유무가 model ID 유효성의 결정론적 증거입니다(R020 "attempt ≠ outcome"). 무인 루프(`/fsd`)의 stderr를 버리면 이 신호도 함께 사라집니다.
 
-> **v2.1.223+**: `CLAUDE_CODE_DISABLE_1M_CONTEXT`가 **native 1M 창을 가진 모든 Claude 모델**을 auto-compaction으로 200K에 유지하도록 확대되었습니다(이전에는 고정 모델 목록). 미인식 model ID도 가정 컨텍스트 창 내로 유지되며 `CLAUDE_CODE_DISABLE_UNKNOWN_MODEL_WINDOW_ENFORCEMENT=1`로 복원할 수 있습니다. 위 Tier-2 표의 `claude-sonnet-5`/`claude-opus-5`(native 1M)와 `[1m]` 접미사는 이 env가 설정된 환경에서 **실효 200K로 동작**하므로, 1M 전제의 대용량 컨텍스트 위임 전에 env 설정 여부를 확인합니다(cross-ref R013 context budget).
+> **v2.1.223+**: `CLAUDE_CODE_DISABLE_1M_CONTEXT`가 **native 1M 창을 가진 모든 Claude 모델**을 auto-compaction으로 200K에 유지하도록 확대되었습니다(이전에는 고정 모델 목록). 미인식 model ID도 가정 컨텍스트 창 내로 유지되며 `CLAUDE_CODE_DISABLE_UNKNOWN_MODEL_WINDOW_ENFORCEMENT=1`로 복원할 수 있습니다. 위 Tier-2 표의 `claude-sonnet-5`/`claude-opus-5`/`claude-sonnet-5-5`/`claude-opus-5-5`(native 1M)와 `[1m]` 접미사는 이 env가 설정된 환경에서 **실효 200K로 동작**하므로, 1M 전제의 대용량 컨텍스트 위임 전에 env 설정 여부를 확인합니다(cross-ref R013 context budget).
 
 > **v2.1.251+**: `CLAUDE_CODE_SUBAGENT_MODEL`이 이제 "모든 것을 override"가 아니라 **기본 subagent 모델만 설정**합니다 — 에이전트 정의의 `model:`(Tier 1/2)과 spawn 시점 명시적 `model`(Tier 3)이 이 env보다 **우선**합니다. 이 저장소는 다수 에이전트가 Tier-2 full ID로 model을 pin하므로, v2.1.251부터는 이 env var가 project의 model pin을 더 이상 깨뜨릴 수 없습니다(단, 이전 버전에서 실행된 세션은 여전히 영향받았을 수 있습니다).
 

package/templates/.claude/rules/SHOULD-ecomode.md

@@ -90,7 +90,7 @@ Active removal of irrelevant retrieved content from agent context. Complements o
 
 > **v2.1.223+**: `CLAUDE_CODE_DISABLE_1M_CONTEXT`가 native 1M 창을 가진 **모든** Claude 모델을 auto-compaction으로 200K에 유지하도록 확대되었고(이전에는 고정 모델 목록), 미인식 model ID도 가정 컨텍스트 창 내로 유지됩니다(`CLAUDE_CODE_DISABLE_UNKNOWN_MODEL_WINDOW_ENFORCEMENT=1`로 복원). 위 임계값은 **창 대비 백분율**이므로 절대 토큰량은 이 env 설정에 따라 5배까지 달라집니다 — 1M 전제로 예산을 잡기 전 env 설정 여부를 확인합니다(cross-ref R006).
 
-> **v2.1.251+**: Sonnet 5의 기본 auto-compact 창이 **전체 1M 컨텍스트로 변경**되어, 1M 창 세션이 이제 ~934K가 아니라 ~967K 토큰에서 auto-compact됩니다. 위 `CLAUDE_CODE_DISABLE_1M_CONTEXT` 노트와 **직접 상호작용**합니다 — 그 env가 **설정된 환경**에서는 여전히 200K로 강제 유지되지만, **비활성 환경**(기본값)에서는 이번 변경으로 실효 auto-compact 임계값 자체가 상향됩니다. 이 저장소 에이전트 다수가 `claude-sonnet-5`이므로, 위 임계값 표의 백분율 계산은 env 설정 여부에 더해 이 CC 버전 여부까지 함께 확인해야 절대 토큰량이 정확합니다.
+> **v2.1.251+**: Sonnet 5의 기본 auto-compact 창이 **전체 1M 컨텍스트로 변경**되어, 1M 창 세션이 이제 ~934K가 아니라 ~967K 토큰에서 auto-compact됩니다. 위 `CLAUDE_CODE_DISABLE_1M_CONTEXT` 노트와 **직접 상호작용**합니다 — 그 env가 **설정된 환경**에서는 여전히 200K로 강제 유지되지만, **비활성 환경**(기본값)에서는 이번 변경으로 실효 auto-compact 임계값 자체가 상향됩니다. 위 임계값 표의 백분율 계산은 env 설정 여부에 더해 이 CC 버전 여부까지 함께 확인해야 절대 토큰량이 정확합니다. **현재 정정**: 이 노트는 Sonnet 5에 대한 CHANGELOG 항목("Changed Sonnet 5's default auto-compact window to its full 1M context")에 근거하며 실측이 아닙니다. 이 저장소 에이전트는 이제 `claude-sonnet-5-5`로 실행되지만(#1755), 동일한 auto-compact 지점이 5.5에도 적용되는지는 CHANGELOG에 명시되어 있지 않으므로 의존하기 전에 실측합니다.
 
 > **v2.1.260+**: 1M 컨텍스트를 가진 모델의 auto-compact 시점이 확대되어, Opus·Fable 세션도 이제 1M 토큰 한도 직전에 compact되고 매우 큰 컨텍스트에서의 recovery compaction이 더 이상 10분 타임아웃으로 실패하지 않습니다 — 위 v2.1.251 Sonnet 5 노트를 Opus/Fable 계열로 확장하는 것이므로, `CLAUDE_CODE_DISABLE_1M_CONTEXT`가 설정되지 않은 한 이 섹션의 백분율 임계값은 이제 세 모델군 전체에서 절대 토큰량 ~1M에 대응합니다. 같은 릴리즈에서 `/cost`와 statusline의 `prompt_cache` 필드가 prompt-cache miss의 **가능성 있는 원인**(도구 정의·시스템 프롬프트 변경, TTL 경과 idle)을 표시하도록 개선되어, 이 규칙이 다루는 캐시 관련 비용 이상 징후를 진단할 때 그 원인 후보를 출발점으로 삼을 수 있습니다 — 후보이지 확정 원인이 아니므로 R020 Proxy Signal 원칙대로 실측으로 확정합니다(cross-ref R012 statusline).
 

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

@@ -317,7 +317,7 @@ steps:
       | 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 |
+      | implement | `gh issue edit <N> --add-label in-progress --add-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}" |
@@ -421,7 +421,7 @@ steps:
       Execute the deep-plan output for the scoped release manifest.
 
       Per-issue lifecycle:
-      1. Start: gh issue edit <N> --add-label in-progress --assignee @me
+      1. Start: gh issue edit <N> --add-label in-progress --add-assignee @me
       2. Comment: gh issue comment <N> --body "Implementation started via auto-dev pipeline"
       3. Dispatch specialist agents per file domain:
          - Detect file types in scope and route to matching agent
@@ -527,11 +527,40 @@ steps:
         contaminate the very command a clause cites (#1711 찐빠 #2); (h) any temporary file the
         delegation creates MUST live under a per-agent-unique path (`$TMPDIR` or the session
         scratchpad), never a fixed shared path (#1722 찐빠 #7).
+      - Any implement-stage delegation that writes an executable command or code snippet into
+        rule/skill/guide/workflow TEXT (not a prose-only edit) MUST require, as a completion-report
+        item, that the agent copy the command OUT of the edited file and run it once on a positive
+        fixture (the check-triggering case) and once on a negative fixture (the check-passing
+        case), reporting both raw outputs (룰/스킬/워크플로 텍스트에 넣는 실행 명령은 편집 파일에서
+        그대로 복사해 양성·음성 픽스처로 실행한 출력을 완료 보고에 포함해야 합니다; 정정 위임은 이미
+        적용해 통과한 결과로 갈음합니다) (R023 「Sample-Value Assembly」, #1752 찐빠 #1).
+      - The fixture-execution norm above (copy the command OUT of the edited file and run it,
+        reporting raw output) extends to CI workflow scripts (e.g. GitHub Actions YAML steps)
+        being verified during implement/verify-build/deep-verify: when the agent extracts a step
+        into a runnable copy to verify it, edits to that copy are LIMITED to execution-environment
+        substitution ONLY (e.g. disabling `sleep`, or pointing a summary-output target such as
+        `$GITHUB_STEP_SUMMARY` at a local file) — the step's logic and echo/output text MUST
+        remain exactly as written in the source file (editing a step's command line to fake a
+        network response is a logic edit; if a response must be simulated, do it via the
+        environment, e.g. a PATH shim, never by editing the step's lines), and the completion
+        report MUST show the RAW fixture output, not a summarized or paraphrased rendering (CI
+        워크플로 스크립트를 사본으로 추출해 검증할 때 사본 수정은 `sleep` 무력화·요약 출력 대상
+        지정처럼 실행 환경 대체로만 제한하고 로직·echo 문구는 원문 그대로 유지하며, 완료 보고에는
+        요약이 아닌 raw 출력을 포함해야 합니다) (R023 「Sample-Value Assembly」, #1754 찐빠 #2).
       - Every delegation prompt (not only rule/skill/guide TEXT edits) MUST instruct the agent
         that if a guard, classifier, or permission check blocks an action, it MUST NOT route
         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).
+      - The standard wording of STATE-CHANGING delegation prompts (git/gh commands,
+        file-creating and file-editing delegations — NOT read-only review/analysis delegations) MUST instruct
+        the agent to report ONLY what it directly observed within its own execution context, and
+        MUST NOT narrate history it did not itself observe (e.g. asserting a branch/file
+        "originally didn't exist" or "already had unrelated uncommitted changes before this
+        session" without having checked) — where the delegation prompt's context leaves a gap, the
+        agent MUST state it as "not observed" rather than fill it by inference (상태 변경 위임서의 표준 문안에 "직접 관측한
+        것만 보고하고, 관측하지 않은 이력은 서술하지 말 것"을 포함해야 합니다) (R020 「보유
+        실측값과 어긋나는 서브에이전트 서술은 즉시 정정」, R010, #1754 찐빠 #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
@@ -885,6 +914,12 @@ steps:
            (loop_count × sleep_interval + command time ≤ timeout, with margin), or prefer a
            single bounded call `gh run watch <run-id> --exit-status` (optionally
            run_in_background) over an unbounded manual poll loop (#1711 찐빠 #6).
+         - Any wait/poll loop in this step, including a release-publish package-availability
+           wait, MUST print one progress line per iteration (attempt count, current observed
+           value) so a long-but-normal wait is not mistaken for a stall — a single bounded
+           `gh run watch`/`gh pr checks --watch` call already streams periodic status, which
+           serves the same anti-stall purpose and satisfies this requirement without extra
+           instrumentation (#1752 찐빠 #2).
          - If failures: diagnose, fix, re-verify
       3. For npm projects with auto-tag.yml: MANDATORY additional check:
          gh run list --workflow auto-tag.yml --limit 1 --json conclusion,displayTitle

package/templates/guides/claude-code/03-tools.md

@@ -42,7 +42,7 @@ import anthropic
 client = anthropic.Anthropic()
 
 response = client.messages.create(
-    model="claude-sonnet-5",
+    model="claude-sonnet-5-5",
     max_tokens=1024,
     tools=[
         {

package/templates/guides/claude-code/06-mcp.md

@@ -26,7 +26,7 @@ import anthropic
 client = anthropic.Anthropic()
 
 response = client.beta.messages.create(
-    model="claude-sonnet-5",
+    model="claude-sonnet-5-5",
     max_tokens=1000,
     messages=[{
         "role": "user",

package/templates/guides/claude-code/13-cli-flags.md

@@ -123,7 +123,7 @@ claude auto-mode critique    # Review auto mode decisions
 
 | Variable | Description | Example |
 |----------|-------------|---------|
-| `ANTHROPIC_MODEL` | Override default model | `claude-opus-5` (default Opus, v2.1.219+) |
+| `ANTHROPIC_MODEL` | Override default model | `claude-opus-5-5` (default Opus, v2.1.280+) |
 | `CLAUDE_CODE_SUBAGENT_MODEL` | Override subagent model | `claude-haiku-4-5` |
 | `CLAUDE_CODE_EFFORT_LEVEL` | Set effort level | `high` |
 | `CLAUDE_CODE_DISABLE_FAST_MODE` | Disable fast mode | `1` |

package/templates/guides/claude-code/15-version-compatibility.md

@@ -9,7 +9,7 @@
 
 ## Compatibility Baseline
 
-oh-my-customcode v1.1.9 targets Claude Code v2.1.201+ (Sonnet 5 = CC 기본 모델). 이 파일에 정리된 v2.1.117-160 항목은 하위호환이며 config 변경이 불필요합니다.
+oh-my-customcode v1.1.9 targets Claude Code v2.1.201+ (v2.1.197부터 Sonnet 5가 CC 기본 Sonnet 모델이었고, v2.1.284부터 Anthropic API의 기본 Sonnet 모델은 Sonnet 5.5). 이 파일에 정리된 v2.1.117-160 항목은 하위호환이며 config 변경이 불필요합니다.
 
 ## v2.1.117 (2026-04-22)
 
@@ -1551,6 +1551,63 @@ Opus 4.8에서 thinking blocks가 수정되어 API 오류가 발생하던 버그
 
 ---
 
+## v2.1.284 (2026-09-28)
+
+> Issue: #1755 — Claude Code v2.1.284 compatibility documentation
+> Scope-ceiling check (R017): 설치 CC·npm latest 모두 **2.1.284**(`claude --version`=2.1.284, `npm view @anthropic-ai/claude-code version`=2.1.284 실측)로 이 릴리즈가 상한이며, 릴리즈 게시 시각은 2026-09-28T18:02:03Z(`gh release view v2.1.284 -R anthropics/claude-code --json publishedAt` 실측)입니다. 2.1.284보다 나중 릴리즈는 없습니다.
+
+### Sonnet 5.5 · 모델 핀 이전
+
+- CHANGELOG 원문: "Added Claude Sonnet 5.5 (`claude-sonnet-5-5`), now the default Sonnet model on the Anthropic API — 1M context, $2/$10 per Mtok with $0.20/Mtok cache reads"
+  (284) Sonnet 5.5(`claude-sonnet-5-5`)가 추가되어 Anthropic API의 기본 Sonnet 모델이 되었습니다. #1755의 범위 결정에 따라 이 저장소는 v1.1.89에서 에이전트 모델 핀 전체를 `claude-sonnet-5-5`/`claude-opus-5-5`로 이전했으며, R006 Model Specification Tier 2 표에 `claude-sonnet-5-5` 행이 추가되었습니다. Tier 1 alias(`sonnet`)는 계속 CC가 해석하므로 프로젝트가 고정할 수 없다는 R006의 설명은 그대로입니다.
+
+### 권한 · 시작 모드
+
+- CHANGELOG 원문: "Added a "Yes, but ask again next time" answer to auto mode's prompt before a read outside the working directories, so you can allow that one read and still be asked about later ones"
+  (284) 작업 디렉터리 밖 읽기를 묻는 auto mode 프롬프트에 "Yes, but ask again next time" 응답이 추가되어, 해당 읽기 한 건만 허용하고 이후 읽기는 계속 확인받을 수 있습니다. 이는 사용자 대화형 프롬프트의 응답 선택지이며 R010 Self-Check가 실측하는 유효 permission mode 판정과 R002 도구 티어 정책을 바꾸지 않습니다.
+- CHANGELOG 원문: "Changed interactive terminal and VS Code sessions to start in auto mode when no permission mode is configured, on every plan and provider; `permissions.defaultMode` still overrides it"
+  (284) permission mode가 설정되지 않은 대화형 터미널·VS Code 세션은 모든 플랜과 provider에서 auto mode로 시작합니다(`permissions.defaultMode`가 설정돼 있으면 계속 그 값이 우선). 위 v2.1.283 섹션의 "서드파티 provider 또는 텔레메트리 off" 조건이 모든 플랜·provider로 넓어진 것입니다. 이 변경은 대화형 터미널·VS Code 세션에 대한 것이므로, R010 Self-Check의 `jq -r '.permissions.defaultMode // "unset"'`(user scope 실측, 무인 실행 전 점검)가 "unset"을 내더라도 무인(`-p`/headless) 실행의 모드를 이 변경으로 판단해서는 안 됩니다. 무인 실행은 이 변경의 대상이 아닙니다.
+
+### 상태줄 · 재시도 · 컨텍스트
+
+- CHANGELOG 원문: "Added dollar amounts to the Claude apps gateway spend limit in `/usage` and the status line (for example "$271.40 / $500.00 spent this month") when the gateway runs this version or later; the status line's `rate_limits.spend_limit` also gains `used_usd`, `limit_usd` and `period`"
+  (284) 상태줄의 `rate_limits.spend_limit`에 `used_usd`, `limit_usd`, `period` 필드가 추가되었습니다(gateway가 이 버전 이상일 때). R012 Statusline API 포맷은 이 필드를 요구하지 않으므로 `.claude/statusline.sh` 확장은 선택 사항입니다.
+- CHANGELOG 원문: "Fixed a damaged response stream showing raw errors such as "JSON Parse error" or "undefined is not an object", or writing the word "undefined" into an answer, instead of being retried or reported as an interrupted response"
+  (284) 손상된 응답 스트림이 원시 오류("JSON Parse error" 등)나 답변 속 "undefined" 문자열로 노출되던 결함이 수정되어 재시도되거나 중단된 응답으로 보고됩니다. R004 Retryable 재시도 전략을 플랫폼이 이 경로에서도 수행하므로, 구버전 세션의 "undefined" 혼입은 모델 오류가 아니라 스트림 손상이었을 수 있습니다.
+- CHANGELOG 원문: "Fixed an overloaded or server error arriving right after a thinking block ending the turn with an error instead of being retried"
+  (284) thinking 블록 직후에 도착한 overloaded·서버 오류가 재시도되지 않고 턴을 오류로 끝내던 결함이 수정되었습니다. R004 v2.1.246/257 자동 이어감 노트와 같은 계열이며, 무인 루프 중단을 "재시도 로직 부재"로 오진하기 전에 확인할 경계가 하나 더 생겼습니다.
+- CHANGELOG 원문: "Fixed "Prompt is too long" errors that persisted after compacting: when the compacted request is still too long, Claude Code now compacts once more, keeping less of the recent conversation"
+  (284) compact 후에도 요청이 너무 길면 CC가 최근 대화를 덜 남기고 한 번 더 compact합니다. R013의 v2.1.269/274 "Prompt is too long" 수정 노트를 이어받는 항목이며, 재compact 이후에는 최근 대화 보존량이 줄어든다는 점을 컨텍스트 예산 판단에 반영해야 합니다.
+
+### 규칙 · 훅 · 메시징
+
+- CHANGELOG 원문: "Fixed rules symlinked into `.claude/rules` from outside the project being skipped without ever showing the external-imports approval prompt; a `.claude` directory symlinked from outside the project now asks for the same approval"
+  (284) 프로젝트 밖에서 `.claude/rules`로 symlink된 룰이 승인 프롬프트 없이 건너뛰어지던 결함이 수정되었고, 프로젝트 밖에서 symlink된 `.claude` 디렉터리도 같은 승인을 요구합니다. 이 저장소의 룰은 프로젝트 내부 실파일이므로 영향이 없지만, 룰을 외부 경로에서 링크하는 사용자 환경에서는 승인 프롬프트가 새로 나타납니다.
+- CHANGELOG 원문: "Fixed the debug log dropping a failed hook's stderr when the hook also wrote to stdout, and logging nothing for a failed hook with no output; failed hooks now also log their status code"
+  (284) 실패한 훅의 stderr가 stdout과 함께 쓰였을 때 debug 로그에서 누락되던 결함과, 출력 없는 실패 훅이 아무것도 기록되지 않던 결함이 수정되었고 상태 코드도 기록됩니다. R021 훅 발화 진단(배선 확인 ≠ 발화 확인)에서 debug 로그를 근거로 삼을 때 신뢰도가 높아집니다.
+- CHANGELOG 원문: "Fixed `{"decision":"block"}` returned by Elicitation and ElicitationResult hooks being ignored; it now declines the MCP elicitation, as exit code 2 does"
+  (284) Elicitation·ElicitationResult 훅이 반환한 `{"decision":"block"}`이 무시되던 결함이 수정되어 exit code 2와 같이 MCP elicitation을 거부합니다. 이 저장소는 해당 훅을 배선하지 않으므로 R021 Enforcement Tiers 변경은 불필요합니다.
+- CHANGELOG 원문: "Fixed sessions launched without the `SendMessage` tool (such as by Claude Desktop) still being told to message other sessions with it"
+  (284) `SendMessage` 도구 없이 시작된 세션(예: Claude Desktop)에 여전히 그 도구로 메시지를 보내라고 안내하던 결함이 수정되었습니다. R018 Detection이 이미 `SendMessage` 존재를 Teams 활성 증거로 쓰지 않으므로 판정표 변경은 불필요합니다.
+
+### 서브에이전트 · 출력 · 메모리
+
+- CHANGELOG 원문: "Fixed the Explore subagent switching to Opus on the Claude API when the session runs a model ID Claude Code doesn't recognize, such as a custom model behind a proxy; Explore now inherits that model"
+  (284) 세션이 CC가 인식하지 못하는 모델 ID(예: proxy 뒤 custom 모델)로 실행될 때 Explore 서브에이전트가 Opus로 전환되던 결함이 수정되어 이제 그 모델을 상속합니다. R006 모델 명세 표의 `inherit` 의미와 같은 방향이며, 구버전에서 Explore가 Opus로 전환된 관측은 이 결함이 원인일 수 있습니다.
+- CHANGELOG 원문: "Fixed `/loop` status updates in self-paced mode often not being shown because Claude wrote them only in its reasoning; Claude now writes each update, and the outcome when the loop stops, as visible text"
+  (284) self-paced `/loop`의 상태 갱신이 reasoning에만 쓰여 표시되지 않던 결함이 수정되어, 각 갱신과 루프 종료 결과가 visible text로 기록됩니다. 원문상 원인은 Claude가 갱신을 reasoning에만 썼다는 모델 출력 동작이며, R007/R008 헤더·접두사가 text 블록에 남지 않던 문제(R008 원인 귀속 노트)와 같은 원인이라는 근거는 없습니다. 이 수정이 R008 text 블록 부재율 전반을 해소한다는 증거는 없으므로 계수 결과는 실측으로 확인해야 합니다.
+- CHANGELOG 원문: "Improved auto-memory loading: invisible characters and tags that imitate Claude Code's own markup are neutralized in `MEMORY.md` and recalled memory notes before they reach Claude"
+  (284) `MEMORY.md`와 회상된 메모리 노트에서 보이지 않는 문자와 CC 자체 markup을 흉내 내는 태그가 Claude에 도달하기 전에 무력화됩니다. R011 native auto memory 경로의 방어가 강화된 것이며, 메모리에 `<system-reminder>` 류 태그를 그대로 적어 두는 관행은 더 이상 원문 그대로 전달되지 않는다고 봐야 합니다.
+
+기타 86건 — 이 저장소 비해당(VSCode 18건, Claude Tag 10건, Cloud sessions 1건, Code Review 1건 포함, 나머지 56건은 gateway·vim 모드·키바인딩·UI 리스트·plugin 화면·Windows/Linux 세부사항 등 harness 비영향). 실측: `gh issue view 1755 --json body --jq .body | sed -n '/^## 릴리즈 요약/,$p' | grep -c '^- '` = 100건 중 위 본문 14건(Sonnet 5.5·모델 핀 1, 권한·시작 모드 2, 상태줄·재시도·컨텍스트 4, 규칙·훅·메시징 4, 서브에이전트·출력·메모리 3)을 다뤘으므로 100 − 14 = 86건입니다.
+
+**Action items**:
+- v1.1.89에서 에이전트 모델 핀을 `claude-sonnet-5-5`/`claude-opus-5-5`로 이전했고 R006 Tier 2 표에 `claude-sonnet-5-5` 행을 추가했습니다(#1755 범위 결정).
+- auto mode 시작 조건 확대와 "ask again next time" 응답은 R010 Self-Check의 유효 permission mode 실측 절차를 바꾸지 않으므로 룰 수정은 불필요합니다.
+- 상태줄 `spend_limit` 필드, 재시도·재compact 수정, 훅 로그·Elicitation·`SendMessage` 안내 수정, Explore 상속, `/loop` 표시, auto-memory 무력화는 기존 룰이 이미 다루는 전제를 강화하는 방향이며 룰 문안 변경은 불필요합니다.
+
+---
+
 ## Known Platform Issues & Workarounds
 
 ### Agent tool malformed parsing on long / special-character prompts (#1241)
@@ -1596,6 +1653,7 @@ Opus 4.8에서 thinking blocks가 수정되어 API 오류가 발생하던 버그
 - #1717 — 컨텍스트 예산 초과 대응: CC 버전 노트 이관 정책 전환(룰 → 가이드)
 - #1746 — Claude Code v2.1.282 compatibility documentation
 - #1747 — Claude Code v2.1.283 compatibility documentation
+- #1755 — Claude Code v2.1.284 compatibility documentation
 - `.claude/skills/claude-native/` — auto-generation source
 - `.claude/rules/SHOULD-hud-statusline.md` — R012 statusline integration
 - `.claude/rules/MUST-agent-design.md` — R006 agent frontmatter spec

package/templates/guides/claude-code/16-fable5-prompting.md

@@ -5,7 +5,7 @@
 
 ## 개요
 
-Claude Fable 5(`claude-fable-5`)는 Mythos-class 모델로, **Opus 4.8 대비** 상위 티어의 GA 역량을 가집니다(GA 시점 기준, R006 Model Aliases 참조). **Opus 5**(`claude-opus-5`, CC v2.1.219+에서 도입되어 현재 CC의 기본 Opus 모델)와의 상대 위계는 공식 자료로 확인되지 않았으므로, 이 문서는 어느 쪽이 상위 티어인지 단정하지 않습니다. Fable 5는 기존 모델 대비 다른 행동 프로파일을 가지므로, 기존 Opus/Sonnet용으로 튜닝된 하네스(rules, skills, system prompt)를 그대로 재사용하면 오히려 품질이 저하될 수 있습니다. 이 문서는 Fable 5 전용 프롬프팅·스캐폴딩 조정 패턴을 정리합니다.
+Claude Fable 5(`claude-fable-5`)는 Mythos-class 모델로, **Opus 4.8 대비** 상위 티어의 GA 역량을 가집니다(GA 시점 기준, R006 Model Aliases 참조). **Opus 5**(`claude-opus-5`)는 CC v2.1.219+에서 도입된 이전 세대 Opus 모델입니다. 현재 CC의 기본 Opus 모델은 Opus 5.5(`claude-opus-5-5`, v2.1.280+)입니다. Fable 5와 Opus 5 및 Opus 5.5의 상대 위계는 공식 자료로 확인되지 않았으므로, 이 문서는 어느 쪽이 상위 티어인지 단정하지 않습니다. Fable 5는 기존 모델 대비 다른 행동 프로파일을 가지므로, 기존 Opus/Sonnet용으로 튜닝된 하네스(rules, skills, system prompt)를 그대로 재사용하면 오히려 품질이 저하될 수 있습니다. 이 문서는 Fable 5 전용 프롬프팅·스캐폴딩 조정 패턴을 정리합니다.
 
 ## Opus 4.8 대비 행동 차이
 

package/templates/guides/multi-model-routing/README.md

@@ -16,7 +16,7 @@ Valid in BOTH agent frontmatter `model:` AND the Agent tool `model` parameter. *
 
 ### Tier 2 — Full Model ID (frontmatter only)
 
-Values: `claude-sonnet-5` | `claude-opus-5` | `claude-haiku-4-5` | `claude-opus-4-6` | `claude-opus-4-8` | `claude-fable-5`, etc.
+Values: `claude-sonnet-5-5` | `claude-sonnet-5` | `claude-opus-5-5` | `claude-opus-5` | `claude-haiku-4-5` | `claude-opus-4-6` | `claude-opus-4-8` | `claude-fable-5`, etc.
 
 Valid ONLY in frontmatter `model:` — the Agent tool `model` parameter does NOT accept full model IDs. Use a Tier 2 ID when you want the agent pinned to a specific model regardless of any future drift in what CC's Tier 1 aliases resolve to.
 
@@ -34,15 +34,17 @@ Values: `sonnet` | `opus` | `haiku` | `fable` — **only these four**. Does NOT
 |---------------|------|-------|----------|
 | `claude-haiku-4-5` | $ | Fast | Search, simple edits, file discovery |
 | `claude-sonnet-4-6` | $$ | Moderate | Code generation, general tasks — historically what the Tier 1 `sonnet` alias resolved to; CC's actual resolution target can drift (see Tier 1 above) |
-| `claude-sonnet-5` | $$ | Moderate | Native 1M context; use as an explicit frontmatter pin |
+| `claude-sonnet-5-5` | $$ | Moderate | Native 1M context; now the default Sonnet model on the Anthropic API, $2/$10 per Mtok with $0.20/Mtok cache reads |
+| `claude-sonnet-5` | $$ | Moderate | Previous-generation Sonnet; native 1M context — use as an explicit frontmatter pin |
 | `claude-opus-4-6` | $$$ | Slower | Complex reasoning, architecture, planning |
-| `claude-opus-5` | $$$ | Fast mode available | Native 1M context, fast mode at $10/$50 per Mtok |
+| `claude-opus-5-5` | $$$ | — | Latest Opus (GA), default Opus model; native 1M context, $4/$20 per Mtok, $0.20/Mtok cache reads |
+| `claude-opus-5` | $$$ | Fast mode available | Previous-generation Opus (GA); native 1M context, fast mode at $10/$50 per Mtok |
 | `claude-opus-4-8` | $$$ | Slower | Previous-generation Opus; supports xhigh effort |
 | `claude-fable-5` | $$$$ | Slower | Mythos-class; use the full ID in frontmatter (bare `fable` is Tier 3 Agent-tool-only) |
 
-Extended context: `[1m]` suffix enables 1M token context (e.g., `claude-opus-4-6[1m]`). Sonnet 5, Opus 5, and Fable 5 include 1M context by default — no `[1m]` suffix needed.
+Extended context: `[1m]` suffix enables 1M token context (e.g., `claude-opus-4-6[1m]`). Sonnet 5, Sonnet 5.5, Opus 5, Opus 5.5, and Fable 5 include 1M context by default — no `[1m]` suffix needed.
 
-> Relative standing of Fable 5 vs Opus 5 is not officially confirmed — do not assert an ordering.
+> Relative standing of Fable 5 vs Opus 5 and Opus 5.5 is not officially confirmed — do not assert an ordering.
 
 ## Role-Based Routing Table
 
@@ -51,15 +53,15 @@ This table recommends **frontmatter (Tier 2) full model IDs** for pinning an age
 | Role | Recommended Frontmatter ID (Tier 2) | Agent-Tool Equivalent (Tier 3) | Rationale |
 |------|--------------------------------------|----------------------------------|-----------|
 | Code search / file discovery | `claude-haiku-4-5` | `haiku` | Fast, cheap, sufficient for retrieval |
-| Code review | `claude-sonnet-5` | `sonnet` | Needs understanding, not deep reasoning |
-| Code generation | `claude-sonnet-5` | `sonnet` | Good balance of quality and speed |
-| Bug fix (simple) | `claude-sonnet-5` | `sonnet` | Pattern recognition sufficient |
-| Bug fix (complex) | `claude-opus-5` | `opus` | Needs deep reasoning across modules |
-| Architecture design | `claude-opus-5` / `opusplan` | `opus` | Requires holistic thinking |
-| Test generation | `claude-sonnet-5` | `sonnet` | Template-driven, moderate complexity |
-| Documentation | `claude-sonnet-5` | `sonnet` | Straightforward generation |
-| Release verification | `claude-opus-5` | `opus` | Cross-cutting validation |
-| Orchestration | `claude-opus-5` | `opus` | Routing decisions need broad context |
+| Code review | `claude-sonnet-5-5` | `sonnet` | Needs understanding, not deep reasoning |
+| Code generation | `claude-sonnet-5-5` | `sonnet` | Good balance of quality and speed |
+| Bug fix (simple) | `claude-sonnet-5-5` | `sonnet` | Pattern recognition sufficient |
+| Bug fix (complex) | `claude-opus-5-5` | `opus` | Needs deep reasoning across modules |
+| Architecture design | `claude-opus-5-5` / `opusplan` | `opus` | Requires holistic thinking |
+| Test generation | `claude-sonnet-5-5` | `sonnet` | Template-driven, moderate complexity |
+| Documentation | `claude-sonnet-5-5` | `sonnet` | Straightforward generation |
+| Release verification | `claude-opus-5-5` | `opus` | Cross-cutting validation |
+| Orchestration | `claude-opus-5-5` | `opus` | Routing decisions need broad context |
 
 ## Cost-Quality Tradeoff Matrix
 
@@ -88,8 +90,8 @@ Projects can declare a `MODEL_ROUTING.md` file to override default routing. This
 
 | Agent Pattern | Model | Override Reason |
 |---------------|-------|-----------------|
-| lang-*-expert | claude-sonnet-5 | Default sufficient for code generation |
-| mgr-sauron | claude-opus-5 | Verification requires deep analysis |
+| lang-*-expert | claude-sonnet-5-5 | Default sufficient for code generation |
+| mgr-sauron | claude-opus-5-5 | Verification requires deep analysis |
 | Explore | claude-haiku-4-5 | Search-only, no generation needed |
 ```
 
@@ -100,7 +102,7 @@ Place in project root or `.claude/` directory.
 ```yaml
 # .claude/agents/example.md
 name: example-agent
-model: claude-sonnet-5  # Tier 2 full model ID (recommended) — see Model Specification — 3 Tiers above
+model: claude-sonnet-5-5  # Tier 2 full model ID (recommended) — see Model Specification — 3 Tiers above
 ```
 
 The `model` field in agent frontmatter accepts EITHER a Tier 1 alias (`sonnet`/`opus`/`haiku`/`opusplan`/`inherit`) OR a Tier 2 full model ID, and sets the agent's default. The Agent tool's `model` parameter at spawn time accepts ONLY the Tier 3 enum (`sonnet`/`opus`/`haiku`/`fable`) and overrides the frontmatter default when supplied.

package/templates/manifest.json

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

@@ -317,7 +317,7 @@ steps:
       | 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 |
+      | implement | `gh issue edit <N> --add-label in-progress --add-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}" |
@@ -421,7 +421,7 @@ steps:
       Execute the deep-plan output for the scoped release manifest.
 
       Per-issue lifecycle:
-      1. Start: gh issue edit <N> --add-label in-progress --assignee @me
+      1. Start: gh issue edit <N> --add-label in-progress --add-assignee @me
       2. Comment: gh issue comment <N> --body "Implementation started via auto-dev pipeline"
       3. Dispatch specialist agents per file domain:
          - Detect file types in scope and route to matching agent
@@ -527,11 +527,40 @@ steps:
         contaminate the very command a clause cites (#1711 찐빠 #2); (h) any temporary file the
         delegation creates MUST live under a per-agent-unique path (`$TMPDIR` or the session
         scratchpad), never a fixed shared path (#1722 찐빠 #7).
+      - Any implement-stage delegation that writes an executable command or code snippet into
+        rule/skill/guide/workflow TEXT (not a prose-only edit) MUST require, as a completion-report
+        item, that the agent copy the command OUT of the edited file and run it once on a positive
+        fixture (the check-triggering case) and once on a negative fixture (the check-passing
+        case), reporting both raw outputs (룰/스킬/워크플로 텍스트에 넣는 실행 명령은 편집 파일에서
+        그대로 복사해 양성·음성 픽스처로 실행한 출력을 완료 보고에 포함해야 합니다; 정정 위임은 이미
+        적용해 통과한 결과로 갈음합니다) (R023 「Sample-Value Assembly」, #1752 찐빠 #1).
+      - The fixture-execution norm above (copy the command OUT of the edited file and run it,
+        reporting raw output) extends to CI workflow scripts (e.g. GitHub Actions YAML steps)
+        being verified during implement/verify-build/deep-verify: when the agent extracts a step
+        into a runnable copy to verify it, edits to that copy are LIMITED to execution-environment
+        substitution ONLY (e.g. disabling `sleep`, or pointing a summary-output target such as
+        `$GITHUB_STEP_SUMMARY` at a local file) — the step's logic and echo/output text MUST
+        remain exactly as written in the source file (editing a step's command line to fake a
+        network response is a logic edit; if a response must be simulated, do it via the
+        environment, e.g. a PATH shim, never by editing the step's lines), and the completion
+        report MUST show the RAW fixture output, not a summarized or paraphrased rendering (CI
+        워크플로 스크립트를 사본으로 추출해 검증할 때 사본 수정은 `sleep` 무력화·요약 출력 대상
+        지정처럼 실행 환경 대체로만 제한하고 로직·echo 문구는 원문 그대로 유지하며, 완료 보고에는
+        요약이 아닌 raw 출력을 포함해야 합니다) (R023 「Sample-Value Assembly」, #1754 찐빠 #2).
       - Every delegation prompt (not only rule/skill/guide TEXT edits) MUST instruct the agent
         that if a guard, classifier, or permission check blocks an action, it MUST NOT route
         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).
+      - The standard wording of STATE-CHANGING delegation prompts (git/gh commands,
+        file-creating and file-editing delegations — NOT read-only review/analysis delegations) MUST instruct
+        the agent to report ONLY what it directly observed within its own execution context, and
+        MUST NOT narrate history it did not itself observe (e.g. asserting a branch/file
+        "originally didn't exist" or "already had unrelated uncommitted changes before this
+        session" without having checked) — where the delegation prompt's context leaves a gap, the
+        agent MUST state it as "not observed" rather than fill it by inference (상태 변경 위임서의 표준 문안에 "직접 관측한
+        것만 보고하고, 관측하지 않은 이력은 서술하지 말 것"을 포함해야 합니다) (R020 「보유
+        실측값과 어긋나는 서브에이전트 서술은 즉시 정정」, R010, #1754 찐빠 #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
@@ -885,6 +914,12 @@ steps:
            (loop_count × sleep_interval + command time ≤ timeout, with margin), or prefer a
            single bounded call `gh run watch <run-id> --exit-status` (optionally
            run_in_background) over an unbounded manual poll loop (#1711 찐빠 #6).
+         - Any wait/poll loop in this step, including a release-publish package-availability
+           wait, MUST print one progress line per iteration (attempt count, current observed
+           value) so a long-but-normal wait is not mistaken for a stall — a single bounded
+           `gh run watch`/`gh pr checks --watch` call already streams periodic status, which
+           serves the same anti-stall purpose and satisfies this requirement without extra
+           instrumentation (#1752 찐빠 #2).
          - If failures: diagnose, fix, re-verify
       3. For npm projects with auto-tag.yml: MANDATORY additional check:
          gh run list --workflow auto-tag.yml --limit 1 --json conclusion,displayTitle