oh-my-customcode 0.91.0 → 0.93.0

package/README.md

@@ -13,7 +13,7 @@
 
 **[한국어 문서 (Korean)](./README_ko.md)**
 
-48 agents. 105 skills. 22 rules. One command.
+48 agents. 106 skills. 22 rules. One command.
 
 ```bash
 npm install -g oh-my-customcode && cd your-project && omcustom init
@@ -132,7 +132,7 @@ Each agent declares its tools, model, memory scope, and limitations in YAML fron
 
 ---
 
-### Skills (105)
+### Skills (106)
 
 | Category | Count | Includes |
 |----------|-------|----------|
@@ -222,7 +222,7 @@ Key rules: R010 (orchestrator never writes files), R009 (parallel execution mand
 
 ---
 
-### Guides (36)
+### Guides (37)
 
 Reference documentation covering best practices, architecture decisions, and integration patterns. Located in `guides/` at project root, covering topics from agent design to CI/CD to observability.
 
@@ -272,14 +272,14 @@ your-project/
 ├── CLAUDE.md                   # Entry point
 ├── .claude/
 │   ├── agents/                 # 48 agent definitions
-│   ├── skills/                 # 105 skill modules
+│   ├── skills/                 # 106 skill modules
 │   ├── rules/                  # 22 governance rules (R000-R021)
 │   ├── hooks/                  # 15 lifecycle hook scripts
 │   ├── schemas/                # Tool input validation schemas
 │   ├── specs/                  # Extracted canonical specs
 │   ├── contexts/               # 4 shared context files
 │   └── ontology/               # Knowledge graph for RAG
-└── guides/                     # 36 reference documents
+└── guides/                     # 37 reference documents
 ```
 
 ---

package/dist/cli/index.js

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

package/dist/index.js

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

package/package.json

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

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

@@ -17,19 +17,31 @@ tools:
 permissionMode: bypassPermissions
 ---
 
-You are an expert Apache Airflow developer for production-ready DAGs following official best practices.
+You are an expert Apache Airflow developer for production-ready DAGs following official best practices, targeting **Airflow 3.1.8**.
 
 ## Capabilities
 
-- DAG authoring (top-level code avoidance, TaskFlow API, classic operators)
-- Task dependency design and scheduling (cron, timetables, data-aware)
-- DAG and task unit testing
+- DAG authoring with `airflow.sdk` namespace (`DAG`, `@task`, `Asset`)
+- TaskFlow API patterns and dynamic task mapping (`expand()`)
+- Task dependency design and scheduling (cron, timetables, data-aware with Assets)
+- DAG and task testing (`dag.test()`, unit tests, integration tests)
 - Connection/variable management and secret backend integration
 - DAG parsing and execution optimization
+- Airflow 2.x → 3.x migration guidance (import paths, deprecated context vars, AIP-72/AIP-44)
+
+## Key Airflow 3.x Differences
+
+| Area | Airflow 2.x | Airflow 3.x |
+|------|-------------|-------------|
+| Imports | `from airflow.models import DAG` | `from airflow.sdk import DAG, task` |
+| Data-aware | `Dataset` | `Asset` |
+| Context | `execution_date` | `dag_run.logical_date` |
+| Architecture | Tight coupling | Task Execution Interface (AIP-72) |
+| API | DB direct access | Internal API (AIP-44) |
 
 ## Skills
 
-Apply **airflow-best-practices** for core Airflow guidelines.
+Apply **airflow-best-practices** for core Airflow 3.1.8 guidelines.
 
 ## Reference Guides
 

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

@@ -103,3 +103,12 @@ The `context-budget-advisor.sh` hook monitors context usage and emits warnings w
 - Does NOT override explicit user settings
 - Advisory only — never blocks operations
 - Context percentage from statusline data when available
+
+## Token Guardian Coexistence (cc-token-saver)
+
+| Component | Trigger | Scope |
+|-----------|---------|-------|
+| `context-budget-advisor.sh` (R013) | Context usage % approaching threshold | In-session budget |
+| Token Guardian (cc-token-saver) | 1h cache TTL idle detection | Cross-session cost |
+
+Both can run simultaneously — different triggers, complementary coverage. R013's context budget is usage-based (approaching limit), Token Guardian is time-based (idle cache expiry).

package/templates/.claude/rules/SHOULD-hud-statusline.md

@@ -41,3 +41,11 @@ RL/WL segments omitted on CC older than v2.1.80.
 ## Integration
 
 Integrates with R007 (Agent ID), R008 (Tool ID), R009 (Parallel).
+
+## External Plugin Statusline Conflict
+
+| Plugin | Component | Resolution |
+|--------|-----------|------------|
+| cc-token-saver | Live Status Line | R012 `.claude/statusline.sh` has priority. Disable cc-token-saver statusline to avoid duplicate status bars. |
+
+Internal statusline (`.claude/statusline.sh`) is the primary status display. External plugin status lines are supplementary or disabled.

package/templates/.claude/skills/action-validator/SKILL.md

@@ -67,6 +67,20 @@ policy_cache:
 
 Policy caching reduces redundant LLM calls for well-understood workflows. Policies are advisory — the orchestrator may override.
 
+## Code Harness Integration (AutoHarness)
+
+When a synthesized harness exists for an agent (`.claude/outputs/harnesses/{agent-name}-*.yaml`), action-validator can use it for enhanced validation:
+
+| Mode | Source | Behavior |
+|------|--------|----------|
+| Advisory (default) | Prompt-based checks | Emit warnings only |
+| Code-verified | harness-synthesizer output | Run harness validation code, emit advisory results |
+| Hard-enforce (opt-in) | harness-synthesizer `--hard-enforce` | Block invalid actions (requires explicit opt-in, see R021) |
+
+To generate a harness for an agent: `/harness-synthesizer --agent {name} --mode verifier`
+
+Code harness validation is additive — it supplements prompt-based checks, not replaces them.
+
 ## Scope
 
 This skill is an advisory layer, not a hard enforcement mechanism:

package/templates/.claude/skills/airflow-best-practices/SKILL.md

@@ -5,29 +5,48 @@ scope: core
 user-invocable: false
 ---
 
-# Apache Airflow Best Practices
+# Apache Airflow Best Practices (3.1.8)
 
 ## DAG Authoring
 
+### Imports (Airflow 3.x)
+- Use `from airflow.sdk import DAG, task, Asset` — the stable public API
+- Legacy `from airflow.models import DAG` and `from airflow.decorators import task` are deprecated
+
 ### Top-Level Code (CRITICAL)
 - Avoid heavy computation at module level (executed on every DAG parse)
-- Minimize imports at module level
-- Use `@task` decorator (TaskFlow API) for Python tasks
-- Keep DAG file under 1000 lines
+- Minimize imports at module level — lazy-load inside `@task` functions
+- Never call APIs, query databases, or access Variables at top level
+- If Variables needed at top level, enable experimental cache with TTL
+
+### TaskFlow API (Default Pattern)
+- Use `@task` decorator for all Python tasks (preferred over classic operators)
+- XCom serialization is automatic — return values become XCom
+- Use `@task.branch` for branching logic
+- Use `@task.sensor` for sensor tasks
+
+### Dynamic Task Mapping
+- Use `task.expand()` for runtime-determined task instances
+- Combine with `.partial()` for fixed kwargs
+- Map over lists, dicts, or XCom outputs from upstream tasks
 
 ### Scheduling
-- Use cron expressions or timetables
-- Set `catchup=False` for most cases
-- Use data-aware scheduling (datasets) for dependencies
+- Use cron expressions or timetables for `schedule` parameter
+- Set `catchup=False` for most DAGs
+- Use data-aware scheduling with `Asset` (replaces `Dataset`) for dependencies
 - Configure SLA monitoring
 
 ### Task Dependencies
-- Use `>>` / `<<` for clarity
-- Group related tasks with TaskGroup
+- Use `>>` / `<<` operators for clarity
+- Group related tasks with `TaskGroup`
 - Avoid deep nesting (max 3 levels)
 
 ## Testing
 
+### Local Testing
+- Use `dag.test()` in `if __name__ == "__main__":` block for IDE debugging
+- Runs all tasks in single serialized process without executor
+
 ### Unit Tests
 - Test DAG import without errors
 - Detect cycles in dependencies
@@ -42,16 +61,34 @@ user-invocable: false
 ## Production Deployment
 
 ### Performance
-- Lazy-load heavy libraries inside tasks
+- Lazy-load heavy libraries inside `@task` functions
 - Use connection pooling
-- Minimize DAG parse time
-- Enable parallelism
+- Minimize DAG parse time (target < 30s for all DAGs)
+- Enable parallelism appropriately
 
 ### Reliability
-- Set appropriate retries and retry_delay
+- Set appropriate `retries` and `retry_delay`
 - Use SLA callbacks for monitoring
-- Implement proper error handling
+- Implement proper error handling with `on_failure_callback`
 - Log important events
 
+## Migration: 2.x → 3.x
+
+### Deprecated (Remove or Replace)
+| Deprecated | Replacement |
+|-----------|-------------|
+| `from airflow.models import DAG` | `from airflow.sdk import DAG` |
+| `from airflow.decorators import task` | `from airflow.sdk import task` |
+| `Dataset` | `Asset` |
+| `execution_date` in context | `dag_run.logical_date` |
+| `conf` in task context | Removed — use Variables or params |
+
+### Architecture Changes
+- **AIP-72**: Task Execution Interface — tasks run in isolated subprocesses via Execution API Server
+- **AIP-44**: Internal API — components communicate via API, not direct DB access
+- **New UI**: React-based web interface (replaces Flask-based UI)
+
 ## References
-- [Airflow Best Practices](https://airflow.apache.org/docs/apache-airflow/stable/best-practices.html)
+- [Airflow 3.1.8 Best Practices](https://airflow.apache.org/docs/apache-airflow/3.1.8/best-practices.html)
+- [Airflow SDK (Task SDK)](https://airflow.apache.org/docs/apache-airflow/3.1.8/authoring-and-scheduling/index.html)
+- [Migration Guide 2.x → 3.x](https://airflow.apache.org/docs/apache-airflow/3.1.8/migration-guide.html)

package/templates/.claude/skills/harness-synthesizer/SKILL.md

@@ -0,0 +1,145 @@
+---
+name: harness-synthesizer
+description: Synthesize code harnesses for agent action validation — AutoHarness-inspired verifier/filter/policy generation
+scope: core
+version: 1.0.0
+user-invocable: true
+argument-hint: "[--mode verifier|filter|policy] [--agent <name>] [--dry-run]"
+effort: high
+---
+
+# Harness Synthesizer Skill
+
+## Purpose
+
+Synthesize executable validation harnesses for agent tool calls, inspired by AutoHarness (Google DeepMind, arxiv 2603.03329). Generates code-level verifiers that check action validity before or after execution, reducing agent errors through structured constraint enforcement.
+
+Default mode is advisory (verifier). Hard enforcement requires explicit `--hard-enforce` opt-in per R021.
+
+## Three Modes
+
+| Mode | Flag | Behavior | Enforcement |
+|------|------|----------|-------------|
+| `verifier` | default | Post-hoc check: validates tool call results after execution | Advisory only |
+| `filter` | `--mode filter` | Pre-execution check: blocks invalid tool calls | Opt-in, requires `--hard-enforce` |
+| `policy` | `--mode policy` | Suggests the best valid action from available options | Advisory only |
+
+### Verifier Mode (Default)
+
+Generates a YAML harness that describes post-execution checks for each tool the agent uses. Checks are emitted as advisory warnings — they do not block execution.
+
+```yaml
+# Example verifier harness output
+harness:
+  agent: lang-golang-expert
+  mode: verifier
+  rules:
+    - tool: Write
+      checks:
+        - field: file_path
+          pattern: ".*\\.go$"
+          on_fail: warn  # advisory
+        - field: content
+          must_not_contain: "TODO:"
+          on_fail: warn
+    - tool: Bash
+      checks:
+        - command_pattern: "^(go build|go test|go fmt|go vet)"
+          on_fail: warn
+```
+
+### Filter Mode (Opt-in)
+
+Generates pre-execution filter rules. Requires `--hard-enforce` flag. Used when advisory warnings are insufficient and the risk of invalid actions is high.
+
+```yaml
+# Example filter harness output (--hard-enforce)
+harness:
+  agent: mgr-gitnerd
+  mode: filter
+  enforcement: hard
+  rules:
+    - tool: Bash
+      blocks:
+        - pattern: "git push --force"
+          reason: "Force push to protected branch"
+        - pattern: "git reset --hard"
+          reason: "Destructive reset without confirmation"
+```
+
+### Policy Mode
+
+Generates a policy function that ranks valid actions and suggests the best one. Useful for agents with multiple valid paths to the same goal.
+
+```yaml
+# Example policy harness output
+harness:
+  agent: qa-engineer
+  mode: policy
+  policies:
+    - scenario: "test file modification"
+      preferred_sequence:
+        - tool: Read
+          reason: "Read before modifying"
+        - tool: Edit
+          reason: "Edit is safer than Write for existing files"
+      avoid:
+        - tool: Write
+          on_existing_file: true
+          reason: "Overwrites without diff"
+```
+
+## Workflow
+
+1. **Read target agent frontmatter** — extract `tools`, `domain`, `limitations` fields
+2. **Analyze recent tool call patterns** — check `.claude/outputs/` for prior session logs (if available)
+3. **Synthesize validation harness** — generate YAML harness matching agent's declared capabilities
+4. **Refine via evaluator-optimizer loop** — iterate harness against edge cases (3 rounds max)
+5. **Save output** — write to `.claude/outputs/harnesses/{agent-name}-{mode}.yaml`
+6. **Report** — print harness summary and integration instructions
+
+## Integration
+
+| System | How |
+|--------|-----|
+| `action-validator` | Harness output feeds into action-validator's code-verified mode |
+| `adaptive-harness --learn` | Auto-triggers harness-synthesizer for project-specific patterns |
+| `evaluator-optimizer` | Provides iterative refinement loop (gradient-free optimization) |
+| `pipeline-guards` | Harness checks usable as pipeline quality gates |
+
+## Usage Examples
+
+```bash
+# Generate advisory verifier for lang-golang-expert
+/harness-synthesizer --agent lang-golang-expert --mode verifier
+
+# Dry-run: preview harness without saving
+/harness-synthesizer --agent mgr-gitnerd --mode filter --dry-run
+
+# Generate hard-enforce filter (explicit opt-in)
+/harness-synthesizer --agent mgr-gitnerd --mode filter --hard-enforce
+
+# Generate policy harness
+/harness-synthesizer --agent qa-engineer --mode policy
+```
+
+## R021 Compliance
+
+- Default `verifier` mode: advisory only — never blocks tool execution
+- `filter` mode without `--hard-enforce`: advisory only — emits warnings
+- `filter --hard-enforce`: opt-in hard enforcement — requires explicit user flag
+- All harness output is saved to `.claude/outputs/harnesses/` (git-untracked)
+
+## Output Format
+
+Harnesses are saved as YAML at `.claude/outputs/harnesses/{agent-name}-{mode}.yaml`. Each harness includes:
+
+```yaml
+harness:
+  agent: {agent-name}
+  mode: verifier | filter | policy
+  version: 1.0.0
+  generated: {ISO-8601 timestamp}
+  enforcement: advisory | hard  # hard only with --hard-enforce
+  rules: [...]
+```

package/templates/CLAUDE.md

@@ -135,6 +135,7 @@ oh-my-customcode로 구동됩니다.
 | `/skill-extractor` | 세션 성공 패턴에서 스킬 후보 추출 |
 | `/deep-plan` | 연구 검증 기반 계획 수립 (research → plan → verify) |
 | `/deep-verify` | 다중 관점 릴리즈 품질 검증 |
+| `/harness-synthesizer` | 에이전트 액션 검증용 코드 하네스 합성 (AutoHarness 기반) |
 | `/professor-triage` | 이슈 교차 분석 트리아지 (omc_issue_analyzer 댓글 기반) |
 | `/release-plan` | verify-done 이슈 릴리즈 유닛 계획 생성 |
 | `/pipeline` | YAML 파이프라인 실행 (예: /pipeline auto-dev) |
@@ -157,11 +158,11 @@ project/
 +-- CLAUDE.md                    # 진입점
 +-- .claude/
 |   +-- agents/                  # 서브에이전트 정의 (48 파일)
-|   +-- skills/                  # 스킬 (105 디렉토리)
+|   +-- skills/                  # 스킬 (106 디렉토리)
 |   +-- rules/                   # 전역 규칙 (R000-R022)
 |   +-- hooks/                   # 훅 스크립트 (보안, 검증, HUD)
 |   +-- contexts/                # 컨텍스트 파일 (ecomode)
-+-- guides/                      # 레퍼런스 문서 (36 토픽)
++-- guides/                      # 레퍼런스 문서 (37 토픽)
 ```
 
 ## 오케스트레이션
@@ -273,6 +274,12 @@ Claude Code의 Agent Teams 기능이 활성화되어 있으면 (`CLAUDE_CODE_EXP
 | obsidian-skills | - | 옵시디언 마크다운 지원 |
 | context7 | claude-plugins-official | 라이브러리 문서 조회 |
 
+### 권장 플러그인
+
+| 플러그인 | 소스 | 용도 |
+|----------|------|------|
+| cc-token-saver | ww-w-ai/cc-token-saver | 토큰/비용 최적화 (Token Guardian, /continue, /usage-view) |
+
 ### 권장 MCP 서버
 
 | 서버 | 용도 |

package/templates/guides/airflow/README.md

@@ -1,22 +1,35 @@
-# Apache Airflow Guide
+# Apache Airflow Guide (3.1.8)
 
-Reference documentation for Apache Airflow DAG development best practices.
+Reference documentation for Apache Airflow 3.1.8 DAG development best practices.
 
 ## Source
 
-Based on [Apache Airflow official documentation](https://airflow.apache.org/docs/) and [Astronomer best practices](https://github.com/astronomer/agents).
+Based on [Apache Airflow 3.1.8 official documentation](https://airflow.apache.org/docs/apache-airflow/3.1.8/) and [Astronomer best practices](https://docs.astronomer.io/).
+
+## Airflow 3.x Key Changes
+
+| Change | Details |
+|--------|---------|
+| SDK namespace | `from airflow.sdk import DAG, task, Asset` |
+| Task Execution (AIP-72) | Isolated subprocess execution via Execution API Server |
+| Internal API (AIP-44) | Components use API instead of direct DB access |
+| Asset (was Dataset) | Data-aware scheduling primitive renamed |
+| Context cleanup | `execution_date` → `dag_run.logical_date` |
+| New UI | React-based web interface |
+| TaskFlow API | `@task` is the default pattern for Python tasks |
 
 ## Categories
 
 | Priority | Category | Impact |
 |----------|----------|--------|
-| 1 | DAG Authoring | CRITICAL |
-| 2 | Task Design | CRITICAL |
-| 3 | Testing | HIGH |
-| 4 | Scheduling | HIGH |
+| 1 | DAG Authoring (airflow.sdk) | CRITICAL |
+| 2 | TaskFlow API & Dynamic Mapping | CRITICAL |
+| 3 | Testing (dag.test()) | HIGH |
+| 4 | Scheduling & Assets | HIGH |
 | 5 | Connections & Variables | MEDIUM |
 | 6 | Monitoring & SLA | MEDIUM |
 | 7 | Performance Optimization | LOW-MEDIUM |
+| 8 | 2.x → 3.x Migration | HIGH |
 
 ## Usage
 
@@ -26,7 +39,9 @@ This guide is referenced by:
 
 ## External Resources
 
-- [Airflow Official Docs](https://airflow.apache.org/docs/)
-- [Airflow Best Practices](https://airflow.apache.org/docs/apache-airflow/stable/best-practices.html)
-- [Astronomer Agents](https://github.com/astronomer/agents)
-- [Airflow TaskFlow API](https://airflow.apache.org/docs/apache-airflow/stable/tutorial/taskflow.html)
+- [Airflow 3.1.8 Official Docs](https://airflow.apache.org/docs/apache-airflow/3.1.8/)
+- [Airflow 3.1.8 Best Practices](https://airflow.apache.org/docs/apache-airflow/3.1.8/best-practices.html)
+- [Airflow Task SDK](https://airflow.apache.org/docs/apache-airflow/3.1.8/authoring-and-scheduling/index.html)
+- [Airflow TaskFlow API](https://airflow.apache.org/docs/apache-airflow/3.1.8/core-concepts/taskflow.html)
+- [Migration Guide 2.x → 3.x](https://airflow.apache.org/docs/apache-airflow/3.1.8/migration-guide.html)
+- [Astronomer Docs](https://docs.astronomer.io/)

package/templates/guides/cc-token-saver/README.md

@@ -0,0 +1,97 @@
+# cc-token-saver Integration Guide
+
+> **Source**: https://github.com/ww-w-ai/cc-token-saver (Apache-2.0)
+> **Strategy**: External plugin — keep as plugin, no internalization
+
+## Installation
+
+```bash
+claude plugin marketplace add ww-w-ai/cc-token-saver
+claude plugin install cc-token-saver
+```
+
+## Feature Overview
+
+| Feature | Description |
+|---------|-------------|
+| Token Guardian | Detects 1h prompt cache TTL idle expiry and warns before cache invalidates |
+| Smart Session Architecture | Auto-injects SubTask delegation patterns into context |
+| `/continue` | Zero-cost context restore after session pause |
+| Live Status Line | Real-time token/cost status bar |
+| `/usage-view` | Cost dashboard showing per-session and cumulative spend |
+| `/report-limit` | Community-sourced rate limit reporting |
+
+## Conflict Resolution with oh-my-customcode
+
+### Live Status Line (R012 Priority)
+
+oh-my-customcode runs its own statusline via `.claude/statusline.sh` (R012). Two simultaneous status bars create visual clutter.
+
+**Resolution**: R012 statusline has priority. Disable cc-token-saver's Live Status Line:
+
+```bash
+# In cc-token-saver config (if supported), or ignore its statusline output
+# oh-my-customcode statusline is configured in .claude/settings.local.json
+```
+
+The R012 statusline already covers: Cost, Rate Limit %, Weekly Limit %, Context %. cc-token-saver's Live Status Line is redundant when R012 is active.
+
+### SubTask Delegation (R009/R010/R018 Priority)
+
+cc-token-saver's Smart Session Architecture auto-injects SubTask delegation patterns. oh-my-customcode has its own delegation rules (R010) and parallel execution rules (R009/R018).
+
+**Resolution**: Internal rules always take precedence (R010 External Skills vs Internal Rules).
+
+| cc-token-saver suggests | oh-my-customcode rule |
+|-------------------------|----------------------|
+| Use SubTask for delegation | Agent tool via routing skills (R010) |
+| Sequential delegation pattern | Parallel when independent (R009) |
+| Generic subtask agent | Specialized agent by domain (R010) |
+
+Ignore cc-token-saver's SubTask suggestions when they conflict with R009/R010/R018.
+
+### Token Guardian ↔ R013 context-budget-advisor.sh (Coexistence)
+
+These two components solve different problems and can run simultaneously:
+
+| Component | Trigger | Scope |
+|-----------|---------|-------|
+| `context-budget-advisor.sh` (R013) | Context usage % approaching threshold | In-session budget management |
+| Token Guardian (cc-token-saver) | 1h cache TTL idle detection | Cross-session cache cost |
+
+**No conflict** — Token Guardian fires on idle time, R013 fires on context percentage. Both warnings are useful.
+
+## Usage Scenarios
+
+### `/continue` — Zero-cost context restore
+
+Use after interrupting and resuming a session. Restores context without re-spending tokens.
+
+```
+/continue
+```
+
+Best for: returning to a paused task, recovering from accidental session close.
+
+### `/usage-view` — Cost dashboard
+
+```
+/usage-view
+```
+
+Shows per-session and cumulative cost. Useful for budget tracking across long sessions.
+
+### `/report-limit` — Community rate limit data
+
+```
+/report-limit
+```
+
+Reports your current rate limit hit to the community pool and shows aggregate rate limit data from other users. Helps gauge when limits reset.
+
+## Integration Notes
+
+- R013 ecomode and Token Guardian are complementary, not competing
+- R012 statusline supersedes cc-token-saver's Live Status Line
+- R009/R010/R018 delegation rules override cc-token-saver's SubTask patterns
+- `/continue`, `/usage-view`, `/report-limit` have no conflicts with internal rules — use freely

package/templates/manifest.json

@@ -1,6 +1,6 @@
 {
-  "version": "0.91.0",
-  "lastUpdated": "2026-04-17T00:00:00.000Z",
+  "version": "0.93.0",
+  "lastUpdated": "2026-04-18T00:00:00.000Z",
   "components": [
     {
       "name": "rules",
@@ -18,13 +18,13 @@
       "name": "skills",
       "path": ".claude/skills",
       "description": "Reusable skill modules (includes slash commands)",
-      "files": 105
+      "files": 106
     },
     {
       "name": "guides",
       "path": "guides",
       "description": "Reference documentation",
-      "files": 36
+      "files": 37
     },
     {
       "name": "hooks",