chore(deps): bump the cargo group across 1 directory with 2 updates

Bumps the cargo group with 2 updates in the /ecc2 directory: [rand](https://github.com/rust-random/rand) and [rustls-webpki](https://github.com/rustls/webpki).


Updates `rand` from 0.8.5 to 0.8.6
- [Release notes](https://github.com/rust-random/rand/releases)
- [Changelog](https://github.com/rust-random/rand/blob/0.8.6/CHANGELOG.md)
- [Commits](https://github.com/rust-random/rand/compare/0.8.5...0.8.6)

Updates `rustls-webpki` from 0.103.10 to 0.103.13
- [Release notes](https://github.com/rustls/webpki/releases)
- [Commits](https://github.com/rustls/webpki/compare/v/0.103.10...v/0.103.13)

---
updated-dependencies:
- dependency-name: rand
  dependency-version: 0.8.6
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: rustls-webpki
  dependency-version: 0.103.13
  dependency-type: indirect
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <support@github.com>

.agents/plugins/marketplace.json

@@ -6,7 +6,7 @@
   "plugins": [
     {
       "name": "ecc",
-      "version": "2.0.0-rc.1",
+      "version": "1.10.0",
       "source": {
         "source": "local",
         "path": "../.."

.agents/skills/agent-introspection-debugging/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: agent-introspection-debugging
 description: Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.
+origin: ECC
 ---
 
 # Agent Introspection Debugging

.agents/skills/agent-introspection-debugging/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Agent Introspection Debugging"
-  short_description: "Structured self-debugging for AI agent failures"
-  brand_color: "#0EA5E9"
-  default_prompt: "Use $agent-introspection-debugging to diagnose and recover from an AI agent failure."
-policy:
-  allow_implicit_invocation: true

.agents/skills/agent-sort/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: agent-sort
 description: Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
+origin: ECC
 ---
 
 # Agent Sort

.agents/skills/agent-sort/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Agent Sort"
-  short_description: "Evidence-backed ECC install planning"
-  brand_color: "#0EA5E9"
-  default_prompt: "Use $agent-sort to build an evidence-backed ECC install plan."
-policy:
-  allow_implicit_invocation: true

.agents/skills/api-design/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: api-design
 description: REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
+origin: ECC
 ---
 
 # API Design Patterns

.agents/skills/api-design/agents/openai.yaml

@@ -2,6 +2,6 @@ interface:
   display_name: "API Design"
   short_description: "REST API design patterns and best practices"
   brand_color: "#F97316"
-  default_prompt: "Use $api-design to design production REST API resources and responses."
+  default_prompt: "Design REST API: resources, status codes, pagination"
 policy:
   allow_implicit_invocation: true

.agents/skills/article-writing/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: article-writing
 description: Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
+origin: ECC
 ---
 
 # Article Writing

.agents/skills/article-writing/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Article Writing"
-  short_description: "Long-form content in a supplied voice"
+  short_description: "Write long-form content in a supplied voice without sounding templated"
   brand_color: "#B45309"
-  default_prompt: "Use $article-writing to draft polished long-form content in the supplied voice."
+  default_prompt: "Draft a sharp long-form article from these notes and examples"
 policy:
   allow_implicit_invocation: true

.agents/skills/backend-patterns/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: backend-patterns
 description: Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
+origin: ECC
 ---
 
 # Backend Development Patterns

.agents/skills/backend-patterns/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Backend Patterns"
-  short_description: "API, database, and server-side patterns"
+  short_description: "API design, database, and server-side patterns"
   brand_color: "#F59E0B"
-  default_prompt: "Use $backend-patterns to apply backend architecture and API patterns."
+  default_prompt: "Apply backend patterns: API design, repository, caching"
 policy:
   allow_implicit_invocation: true

.agents/skills/brand-voice/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: brand-voice
 description: Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.
+origin: ECC
 ---
 
 # Brand Voice

.agents/skills/brand-voice/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Brand Voice"
-  short_description: "Source-derived writing style profiles"
-  brand_color: "#0EA5E9"
-  default_prompt: "Use $brand-voice to derive and reuse a source-grounded writing style."
-policy:
-  allow_implicit_invocation: true

.agents/skills/bun-runtime/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: bun-runtime
 description: Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.
+origin: ECC
 ---
 
 # Bun Runtime

.agents/skills/bun-runtime/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Bun Runtime"
-  short_description: "Bun runtime, package manager, and test runner"
+  short_description: "Bun as runtime, package manager, bundler, and test runner"
   brand_color: "#FBF0DF"
-  default_prompt: "Use $bun-runtime to choose and apply Bun runtime workflows."
+  default_prompt: "Use Bun for scripts, install, or run"
 policy:
   allow_implicit_invocation: true

.agents/skills/claude-api/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: claude-api
 description: Anthropic Claude API patterns for Python and TypeScript. Covers Messages API, streaming, tool use, vision, extended thinking, batches, prompt caching, and Claude Agent SDK. Use when building applications with the Claude API or Anthropic SDKs.
+origin: ECC
 ---
 
 # Claude API

.agents/skills/claude-api/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Claude API"
-  short_description: "Claude API patterns for Python and TypeScript"
+  short_description: "Anthropic Claude API patterns and SDKs"
   brand_color: "#D97706"
-  default_prompt: "Use $claude-api to build with Claude API and Anthropic SDK patterns."
+  default_prompt: "Build applications with the Claude API using Messages, tool use, streaming, and Agent SDK"
 policy:
   allow_implicit_invocation: true

.agents/skills/coding-standards/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: coding-standards
 description: Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.
+origin: ECC
 ---
 
 # Coding Standards & Best Practices

.agents/skills/coding-standards/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Coding Standards"
-  short_description: "Cross-project coding conventions and review"
+  short_description: "Universal coding standards and best practices"
   brand_color: "#3B82F6"
-  default_prompt: "Use $coding-standards to review code against cross-project standards."
+  default_prompt: "Apply standards: immutability, error handling, type safety"
 policy:
   allow_implicit_invocation: true

.agents/skills/content-engine/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: content-engine
 description: Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.
+origin: ECC
 ---
 
 # Content Engine

.agents/skills/content-engine/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Content Engine"
-  short_description: "Platform-native content systems and campaigns"
+  short_description: "Turn one idea into platform-native social and content outputs"
   brand_color: "#DC2626"
-  default_prompt: "Use $content-engine to turn source material into platform-native content."
+  default_prompt: "Turn this source asset into strong multi-platform content"
 policy:
   allow_implicit_invocation: true

.agents/skills/crosspost/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: crosspost
 description: Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.
+origin: ECC
 ---
 
 # Crosspost

.agents/skills/crosspost/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Crosspost"
-  short_description: "Multi-platform social distribution"
+  short_description: "Multi-platform content distribution with native adaptation"
   brand_color: "#EC4899"
-  default_prompt: "Use $crosspost to adapt content for multiple social platforms."
+  default_prompt: "Distribute content across X, LinkedIn, Threads, and Bluesky with platform-native adaptation"
 policy:
   allow_implicit_invocation: true

.agents/skills/deep-research/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: deep-research
 description: Multi-source deep research using firecrawl and exa MCPs. Searches the web, synthesizes findings, and delivers cited reports with source attribution. Use when the user wants thorough research on any topic with evidence and citations.
+origin: ECC
 ---
 
 # Deep Research

.agents/skills/deep-research/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Deep Research"
-  short_description: "Multi-source cited research reports"
+  short_description: "Multi-source deep research with firecrawl and exa MCPs"
   brand_color: "#6366F1"
-  default_prompt: "Use $deep-research to produce a cited multi-source research report."
+  default_prompt: "Research the given topic using firecrawl and exa, produce a cited report"
 policy:
   allow_implicit_invocation: true

.agents/skills/dmux-workflows/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: dmux-workflows
 description: Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.
+origin: ECC
 ---
 
 # dmux Workflows

.agents/skills/dmux-workflows/agents/openai.yaml

@@ -2,6 +2,6 @@ interface:
   display_name: "dmux Workflows"
   short_description: "Multi-agent orchestration with dmux"
   brand_color: "#14B8A6"
-  default_prompt: "Use $dmux-workflows to orchestrate parallel agent sessions with dmux."
+  default_prompt: "Orchestrate parallel agent sessions using dmux pane manager"
 policy:
   allow_implicit_invocation: true

.agents/skills/documentation-lookup/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: documentation-lookup
 description: Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma).
+origin: ECC
 ---
 
 # Documentation Lookup (Context7)

.agents/skills/documentation-lookup/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Documentation Lookup"
-  short_description: "Current library docs via Context7"
+  short_description: "Fetch up-to-date library docs via Context7 MCP"
   brand_color: "#6366F1"
-  default_prompt: "Use $documentation-lookup to fetch current library documentation via Context7."
+  default_prompt: "Look up docs for a library or API"
 policy:
   allow_implicit_invocation: true

.agents/skills/e2e-testing/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: e2e-testing
 description: Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.
+origin: ECC
 ---
 
 # E2E Testing Patterns

.agents/skills/e2e-testing/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "E2E Testing"
-  short_description: "Playwright E2E testing patterns"
+  short_description: "Playwright end-to-end testing"
   brand_color: "#06B6D4"
-  default_prompt: "Use $e2e-testing to design Playwright end-to-end test coverage."
+  default_prompt: "Generate Playwright E2E tests with Page Object Model"
 policy:
   allow_implicit_invocation: true

.agents/skills/eval-harness/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: eval-harness
 description: Formal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles
-allowed-tools: Read, Write, Edit, Bash, Grep, Glob
+origin: ECC
+tools: Read, Write, Edit, Bash, Grep, Glob
 ---
 
 # Eval Harness Skill

.agents/skills/eval-harness/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Eval Harness"
-  short_description: "Eval-driven development harnesses"
+  short_description: "Eval-driven development with pass/fail criteria"
   brand_color: "#EC4899"
-  default_prompt: "Use $eval-harness to define eval-driven development checks."
+  default_prompt: "Set up eval-driven development with pass/fail criteria"
 policy:
   allow_implicit_invocation: true

.agents/skills/everything-claude-code/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: everything-claude-code
+name: everything-claude-code-conventions
 description: Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
 ---
 

.agents/skills/everything-claude-code/agents/openai.yaml

@@ -1,7 +1,6 @@
 interface:
   display_name: "Everything Claude Code"
-  short_description: "Repo workflows for everything-claude-code"
+  short_description: "Repo-specific patterns and workflows for everything-claude-code"
-  brand_color: "#0EA5E9"
+  default_prompt: "Use the everything-claude-code repo skill to follow existing architecture, testing, and workflow conventions."
-  default_prompt: "Use $everything-claude-code to follow this repository's conventions and workflows."
 policy:
-  allow_implicit_invocation: true
+  allow_implicit_invocation: true

.agents/skills/exa-search/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: exa-search
 description: Neural search via Exa MCP for web, code, and company research. Use when the user needs web search, code examples, company intel, people lookup, or AI-powered deep research with Exa's neural search engine.
+origin: ECC
 ---
 
 # Exa Search

.agents/skills/exa-search/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Exa Search"
-  short_description: "Neural search via Exa MCP"
+  short_description: "Neural search via Exa MCP for web, code, and companies"
   brand_color: "#8B5CF6"
-  default_prompt: "Use $exa-search to search web, code, or company data through Exa."
+  default_prompt: "Search using Exa MCP tools for web content, code, or company research"
 policy:
   allow_implicit_invocation: true

.agents/skills/fal-ai-media/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: fal-ai-media
 description: Unified media generation via fal.ai MCP — image, video, and audio. Covers text-to-image (Nano Banana), text/image-to-video (Seedance, Kling, Veo 3), text-to-speech (CSM-1B), and video-to-audio (ThinkSound). Use when the user wants to generate images, videos, or audio with AI.
+origin: ECC
 ---
 
 # fal.ai Media Generation

.agents/skills/fal-ai-media/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "fal.ai Media"
-  short_description: "AI media generation via fal.ai"
+  short_description: "AI image, video, and audio generation via fal.ai"
   brand_color: "#F43F5E"
-  default_prompt: "Use $fal-ai-media to generate image, video, or audio assets with fal.ai."
+  default_prompt: "Generate images, videos, or audio using fal.ai models"
 policy:
   allow_implicit_invocation: true

.agents/skills/frontend-design/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: frontend-design
 description: Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build web components, pages, or applications and the visual direction matters as much as the code quality.
+origin: ECC
 ---
 
 # Frontend Design

.agents/skills/frontend-design/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Frontend Design"
-  short_description: "Production-grade frontend interface design"
-  brand_color: "#0EA5E9"
-  default_prompt: "Use $frontend-design to build a distinctive production-grade interface."
-policy:
-  allow_implicit_invocation: true

.agents/skills/frontend-patterns/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: frontend-patterns
 description: Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.
+origin: ECC
 ---
 
 # Frontend Development Patterns

.agents/skills/frontend-patterns/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Frontend Patterns"
-  short_description: "React and Next.js frontend patterns"
+  short_description: "React and Next.js patterns and best practices"
   brand_color: "#8B5CF6"
-  default_prompt: "Use $frontend-patterns to apply React and Next.js frontend patterns."
+  default_prompt: "Apply React/Next.js patterns and best practices"
 policy:
   allow_implicit_invocation: true

.agents/skills/frontend-slides/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: frontend-slides
 description: Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.
+origin: ECC
 ---
 
 # Frontend Slides

.agents/skills/frontend-slides/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Frontend Slides"
-  short_description: "Animation-rich HTML presentation decks"
+  short_description: "Create distinctive HTML slide decks and convert PPTX to web"
   brand_color: "#FF6B3D"
-  default_prompt: "Use $frontend-slides to create an animation-rich HTML presentation deck."
+  default_prompt: "Create a viewport-safe HTML presentation with strong visual direction"
 policy:
   allow_implicit_invocation: true

.agents/skills/investor-materials/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: investor-materials
 description: Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.
+origin: ECC
 ---
 
 # Investor Materials

.agents/skills/investor-materials/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Investor Materials"
-  short_description: "Investor decks, memos, and financial materials"
+  short_description: "Create decks, memos, and financial materials from one source of truth"
   brand_color: "#7C3AED"
-  default_prompt: "Use $investor-materials to draft consistent investor-facing fundraising assets."
+  default_prompt: "Draft investor materials that stay numerically consistent across assets"
 policy:
   allow_implicit_invocation: true

.agents/skills/investor-outreach/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: investor-outreach
 description: Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging.
+origin: ECC
 ---
 
 # Investor Outreach

.agents/skills/investor-outreach/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Investor Outreach"
-  short_description: "Personalized investor outreach and follow-ups"
+  short_description: "Write concise, personalized outreach and follow-ups for fundraising"
   brand_color: "#059669"
-  default_prompt: "Use $investor-outreach to write concise personalized investor outreach."
+  default_prompt: "Draft a personalized investor outreach email with a clear low-friction ask"
 policy:
   allow_implicit_invocation: true

.agents/skills/market-research/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: market-research
 description: Conduct market research, competitive analysis, investor due diligence, and industry intelligence with source attribution and decision-oriented summaries. Use when the user wants market sizing, competitor comparisons, fund research, technology scans, or research that informs business decisions.
+origin: ECC
 ---
 
 # Market Research

.agents/skills/market-research/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Market Research"
-  short_description: "Source-attributed market research"
+  short_description: "Source-attributed market, competitor, and investor research"
   brand_color: "#2563EB"
-  default_prompt: "Use $market-research to research markets with source-attributed findings."
+  default_prompt: "Research this market and summarize the decision-relevant findings"
 policy:
   allow_implicit_invocation: true

.agents/skills/mcp-server-patterns/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: mcp-server-patterns
 description: Build MCP servers with Node/TypeScript SDK — tools, resources, prompts, Zod validation, stdio vs Streamable HTTP. Use Context7 or official MCP docs for latest API.
+origin: ECC
 ---
 
 # MCP Server Patterns

.agents/skills/mcp-server-patterns/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "MCP Server Patterns"
-  short_description: "MCP server tools, resources, and prompts"
-  brand_color: "#0EA5E9"
-  default_prompt: "Use $mcp-server-patterns to build MCP tools, resources, and prompts."
-policy:
-  allow_implicit_invocation: true

.agents/skills/nextjs-turbopack/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: nextjs-turbopack
 description: Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.
+origin: ECC
 ---
 
 # Next.js and Turbopack

.agents/skills/nextjs-turbopack/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Next.js Turbopack"
-  short_description: "Next.js and Turbopack workflow guidance"
+  short_description: "Next.js 16+ and Turbopack dev bundler"
   brand_color: "#000000"
-  default_prompt: "Use $nextjs-turbopack to work through Next.js and Turbopack decisions."
+  default_prompt: "Next.js dev, Turbopack, or bundle optimization"
 policy:
   allow_implicit_invocation: true

.agents/skills/product-capability/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: product-capability
 description: Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before multi-service work starts. Use when the user needs an ECC-native PRD-to-SRS lane instead of vague planning prose.
+origin: ECC
 ---
 
 # Product Capability

.agents/skills/product-capability/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Product Capability"
-  short_description: "Implementation-ready product capability plans"
-  brand_color: "#0EA5E9"
-  default_prompt: "Use $product-capability to turn product intent into an implementation plan."
-policy:
-  allow_implicit_invocation: true

.agents/skills/security-review/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: security-review
 description: Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
+origin: ECC
 ---
 
 # Security Review Skill

.agents/skills/security-review/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Security Review"
-  short_description: "Security checklist and vulnerability review"
+  short_description: "Comprehensive security checklist and vulnerability detection"
   brand_color: "#EF4444"
-  default_prompt: "Use $security-review to review sensitive code with the security checklist."
+  default_prompt: "Run security checklist: secrets, input validation, injection prevention"
 policy:
   allow_implicit_invocation: true

.agents/skills/strategic-compact/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: strategic-compact
 description: Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.
+origin: ECC
 ---
 
 # Strategic Compact Skill

.agents/skills/strategic-compact/agents/openai.yaml

@@ -2,6 +2,6 @@ interface:
   display_name: "Strategic Compact"
   short_description: "Context management via strategic compaction"
   brand_color: "#14B8A6"
-  default_prompt: "Use $strategic-compact to choose a useful context compaction boundary."
+  default_prompt: "Suggest task boundary compaction for context management"
 policy:
   allow_implicit_invocation: true

.agents/skills/tdd-workflow/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: tdd-workflow
 description: Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
+origin: ECC
 ---
 
 # Test-Driven Development Workflow

.agents/skills/tdd-workflow/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "TDD Workflow"
-  short_description: "Test-driven development with coverage gates"
+  short_description: "Test-driven development with 80%+ coverage"
   brand_color: "#22C55E"
-  default_prompt: "Use $tdd-workflow to drive the change with tests before implementation."
+  default_prompt: "Follow TDD: write tests first, implement, verify 80%+ coverage"
 policy:
   allow_implicit_invocation: true

.agents/skills/verification-loop/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: verification-loop
 description: "A comprehensive verification system for Claude Code sessions."
+origin: ECC
 ---
 
 # Verification Loop Skill

.agents/skills/verification-loop/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Verification Loop"
-  short_description: "Build, test, lint, and typecheck verification"
+  short_description: "Build, test, lint, typecheck verification"
   brand_color: "#10B981"
-  default_prompt: "Use $verification-loop to run build, test, lint, and typecheck verification."
+  default_prompt: "Run verification: build, test, lint, typecheck, security"
 policy:
   allow_implicit_invocation: true

.agents/skills/video-editing/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: video-editing
 description: AI-assisted video editing workflows for cutting, structuring, and augmenting real footage. Covers the full pipeline from raw capture through FFmpeg, Remotion, ElevenLabs, fal.ai, and final polish in Descript or CapCut. Use when the user wants to edit video, cut footage, create vlogs, or build video content.
+origin: ECC
 ---
 
 # Video Editing

.agents/skills/video-editing/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Video Editing"
-  short_description: "AI-assisted editing for real footage"
+  short_description: "AI-assisted video editing for real footage"
   brand_color: "#EF4444"
-  default_prompt: "Use $video-editing to plan an AI-assisted edit for real footage."
+  default_prompt: "Edit video using AI-assisted pipeline: organize, cut, compose, generate assets, polish"
 policy:
   allow_implicit_invocation: true

.agents/skills/x-api/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: x-api
 description: X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.
+origin: ECC
 ---
 
 # X API

.agents/skills/x-api/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "X API"
-  short_description: "X API posting, timelines, and analytics"
+  short_description: "X/Twitter API integration for posting, threads, and analytics"
   brand_color: "#000000"
-  default_prompt: "Use $x-api to build X API posting, timeline, or analytics workflows."
+  default_prompt: "Use X API to post tweets, threads, or retrieve timeline and search data"
 policy:
   allow_implicit_invocation: true

.claude-plugin/marketplace.json

@@ -11,8 +11,8 @@
     {
       "name": "everything-claude-code",
       "source": "./",
-      "description": "The most comprehensive Claude Code plugin — 48 agents, 184 skills, 79 legacy command shims, selective install profiles, and production-ready hooks for TDD, security scanning, code review, and continuous learning",
+      "description": "The most comprehensive Claude Code plugin — 38 agents, 156 skills, 72 legacy command shims, selective install profiles, and production-ready hooks for TDD, security scanning, code review, and continuous learning",
-      "version": "2.0.0-rc.1",
+      "version": "1.10.0",
       "author": {
         "name": "Affaan Mustafa",
         "email": "me@affaanmustafa.com"

.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "everything-claude-code",
-  "version": "2.0.0-rc.1",
+  "version": "1.10.0",
-  "description": "Battle-tested Claude Code plugin for engineering teams — 48 agents, 184 skills, 79 legacy command shims, production-ready hooks, and selective install workflows evolved through continuous real-world use",
+  "description": "Battle-tested Claude Code plugin for engineering teams — 38 agents, 156 skills, 72 legacy command shims, production-ready hooks, and selective install workflows evolved through continuous real-world use",
   "author": {
     "name": "Affaan Mustafa",
     "url": "https://x.com/affaanmustafa"

.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "ecc",
-  "version": "2.0.0-rc.1",
+  "version": "1.10.0",
   "description": "Battle-tested Codex workflows — 156 shared ECC skills, production-ready MCP configs, and selective-install-aligned conventions for TDD, security scanning, code review, and autonomous development.",
   "author": {
     "name": "Affaan Mustafa",

.github/workflows/ci.yml

@@ -2,8 +2,7 @@ name: CI
 
 on:
   push:
-    branches: [main, 'release/**']
+    branches: [main]
-    tags: ['v*']
   pull_request:
     branches: [main]
 

.github/workflows/release.yml

@@ -33,8 +33,8 @@ jobs:
 
       - name: Validate version tag
         run: |
-          if ! [[ "${REF_NAME}" =~ ^v[0-9]+\.[0-9]+\.[0-9]+(-[0-9A-Za-z.-]+)?$ ]]; then
+          if ! [[ "${REF_NAME}" =~ ^v[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
-            echo "Invalid version tag format. Expected vX.Y.Z or vX.Y.Z-prerelease"
+            echo "Invalid version tag format. Expected vX.Y.Z"
             exit 1
           fi
 
@@ -60,13 +60,17 @@ jobs:
         run: |
           PACKAGE_NAME=$(node -p "require('./package.json').name")
           PACKAGE_VERSION=$(node -p "require('./package.json').version")
-          NPM_DIST_TAG=$(node -p "require('./package.json').version.includes('-') ? 'next' : 'latest'")
           if npm view "${PACKAGE_NAME}@${PACKAGE_VERSION}" version >/dev/null 2>&1; then
             echo "already_published=true" >> "$GITHUB_OUTPUT"
           else
             echo "already_published=false" >> "$GITHUB_OUTPUT"
           fi
-          echo "dist_tag=${NPM_DIST_TAG}" >> "$GITHUB_OUTPUT"
+
+      - name: Publish npm package
+        if: steps.npm_publish_state.outputs.already_published != 'true'
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: npm publish --access public --provenance
 
       - name: Generate release highlights
         id: highlights
@@ -98,11 +102,3 @@ jobs:
         with:
           body_path: release_body.md
           generate_release_notes: true
-          prerelease: ${{ contains(github.ref_name, '-') }}
-          make_latest: ${{ contains(github.ref_name, '-') && 'false' || 'true' }}
-
-      - name: Publish npm package
-        if: steps.npm_publish_state.outputs.already_published != 'true'
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-        run: npm publish --access public --provenance --tag "${{ steps.npm_publish_state.outputs.dist_tag }}"

.github/workflows/reusable-release.yml

@@ -18,7 +18,7 @@ on:
   workflow_dispatch:
     inputs:
       tag:
-        description: 'Version tag to release or republish (e.g., v2.0.0-rc.1)'
+        description: 'Version tag to release or republish (e.g., v1.10.0)'
         required: true
         type: string
       generate-notes:
@@ -41,7 +41,6 @@ jobs:
         uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
         with:
           fetch-depth: 0
-          ref: ${{ inputs.tag }}
 
       - name: Setup Node.js
         uses: actions/setup-node@53b83947a5a98c8d113130e565377fae1a50d02f # v6.3.0
@@ -59,8 +58,8 @@ jobs:
         env:
           INPUT_TAG: ${{ inputs.tag }}
         run: |
-          if ! [[ "$INPUT_TAG" =~ ^v[0-9]+\.[0-9]+\.[0-9]+(-[0-9A-Za-z.-]+)?$ ]]; then
+          if ! [[ "$INPUT_TAG" =~ ^v[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
-            echo "Invalid version tag format. Expected vX.Y.Z or vX.Y.Z-prerelease"
+            echo "Invalid version tag format. Expected vX.Y.Z"
             exit 1
           fi
 
@@ -84,13 +83,17 @@ jobs:
         run: |
           PACKAGE_NAME=$(node -p "require('./package.json').name")
           PACKAGE_VERSION=$(node -p "require('./package.json').version")
-          NPM_DIST_TAG=$(node -p "require('./package.json').version.includes('-') ? 'next' : 'latest'")
           if npm view "${PACKAGE_NAME}@${PACKAGE_VERSION}" version >/dev/null 2>&1; then
             echo "already_published=true" >> "$GITHUB_OUTPUT"
           else
             echo "already_published=false" >> "$GITHUB_OUTPUT"
           fi
-          echo "dist_tag=${NPM_DIST_TAG}" >> "$GITHUB_OUTPUT"
+
+      - name: Publish npm package
+        if: steps.npm_publish_state.outputs.already_published != 'true'
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: npm publish --access public --provenance
 
       - name: Generate release highlights
         env:
@@ -116,11 +119,3 @@ jobs:
           tag_name: ${{ inputs.tag }}
           body_path: release_body.md
           generate_release_notes: ${{ inputs.generate-notes }}
-          prerelease: ${{ contains(inputs.tag, '-') }}
-          make_latest: ${{ contains(inputs.tag, '-') && 'false' || 'true' }}
-
-      - name: Publish npm package
-        if: steps.npm_publish_state.outputs.already_published != 'true'
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-        run: npm publish --access public --provenance --tag "${{ steps.npm_publish_state.outputs.dist_tag }}"

.opencode/.npmignore

@@ -1,2 +0,0 @@
-node_modules
-bun.lock

.opencode/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "ecc-universal",
-  "version": "2.0.0-rc.1",
+  "version": "1.10.0",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "ecc-universal",
-      "version": "2.0.0-rc.1",
+      "version": "1.10.0",
       "license": "MIT",
       "devDependencies": {
         "@opencode-ai/plugin": "^1.4.3",

.opencode/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ecc-universal",
-  "version": "2.0.0-rc.1",
+  "version": "1.10.0",
   "description": "Everything Claude Code (ECC) plugin for OpenCode - agents, commands, hooks, and skills",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

.opencode/plugins/ecc-hooks.ts

@@ -456,7 +456,7 @@ export const ECCHooksPlugin: ECCHooksPluginFn = async ({
       const contextBlock = [
         "# ECC Context (preserve across compaction)",
         "",
-        "## Active Plugin: Everything Claude Code v2.0.0-rc.1",
+        "## Active Plugin: Everything Claude Code v1.10.0",
         "- Hooks: file.edited, tool.execute.before/after, session.created/idle/deleted, shell.env, compacting, permission.ask",
         "- Tools: run-tests, check-coverage, security-audit, format-code, lint-check, git-summary, changed-files",
         "- Agents: 13 specialized (planner, architect, tdd-guide, code-reviewer, security-reviewer, build-error-resolver, e2e-runner, refactor-cleaner, doc-updater, go-reviewer, go-build-resolver, database-reviewer, python-reviewer)",

AGENTS.md

@@ -1,8 +1,8 @@
 # Everything Claude Code (ECC) — Agent Instructions
 
-This is a **production-ready AI coding plugin** providing 48 specialized agents, 184 skills, 79 commands, and automated hook workflows for software development.
+This is a **production-ready AI coding plugin** providing 48 specialized agents, 183 skills, 79 commands, and automated hook workflows for software development.
 
-**Version:** 2.0.0-rc.1
+**Version:** 1.10.0
 
 ## Core Principles
 
@@ -146,7 +146,7 @@ Troubleshoot failures: check test isolation → verify mocks → fix implementat
 
 ```
 agents/          — 48 specialized subagents
-skills/          — 184 workflow skills and domain knowledge
+skills/          — 183 workflow skills and domain knowledge
 commands/        — 79 slash commands
 hooks/           — Trigger-based automations
 rules/           — Always-follow guidelines (common + per-language)

CHANGELOG.md

@@ -1,25 +1,5 @@
 # Changelog
 
-## 2.0.0-rc.1 - 2026-04-28
-
-### Highlights
-
-- Adds the public ECC 2.0 release-candidate surface for the Hermes operator story.
-- Documents ECC as the reusable cross-harness substrate across Claude Code, Codex, Cursor, OpenCode, and Gemini.
-- Adds a sanitized Hermes import skill surface instead of publishing private operator state.
-
-### Release Surface
-
-- Updated package, plugin, marketplace, OpenCode, agent, and README metadata to `2.0.0-rc.1`.
-- Added `docs/releases/2.0.0-rc.1/` with release notes, social drafts, launch checklist, handoff notes, and demo prompts.
-- Added `docs/architecture/cross-harness.md` and regression coverage for the ECC/Hermes boundary.
-- Kept `ecc2/` versioning independent for now; it remains an alpha control-plane scaffold unless release engineering decides otherwise.
-
-### Notes
-
-- This is a release candidate, not a GA claim for the full ECC 2.0 control-plane roadmap.
-- Prerelease npm publishing should use the `next` dist-tag unless release engineering explicitly chooses otherwise.
-
 ## 1.10.0 - 2026-04-05
 
 ### Highlights

README.md

@@ -40,8 +40,6 @@ Not just configs. A complete system: skills, instincts, memory optimization, con
 
 Works across **Claude Code**, **Codex**, **Cursor**, **OpenCode**, **Gemini**, and other AI agent harnesses.
 
-ECC v2.0.0-rc.1 adds the public Hermes operator story on top of that reusable layer: start with the [Hermes setup guide](docs/HERMES-SETUP.md), then review the [rc.1 release notes](docs/releases/2.0.0-rc.1/release-notes.md) and [cross-harness architecture](docs/architecture/cross-harness.md).
-
 ---
 
 ## The Guides
@@ -86,7 +84,7 @@ This repo is the raw code only. The guides explain everything.
 
 ## What's New
 
-### v2.0.0-rc.1 — Surface Refresh, Operator Workflows, and ECC 2.0 Alpha (Apr 2026)
+### v1.10.0 — Surface Refresh, Operator Workflows, and ECC 2.0 Alpha (Apr 2026)
 
 - **Dashboard GUI** — New Tkinter-based desktop application (`ecc_dashboard.py` or `npm run dashboard`) with dark/light theme toggle, font customization, and project logo in header and taskbar.
 - **Public surface synced to the live repo** — metadata, catalog counts, plugin manifests, and install-facing docs now match the actual OSS surface: 38 agents, 156 skills, and 72 legacy command shims.
@@ -169,17 +167,7 @@ See the full changelog in [Releases](https://github.com/affaan-m/everything-clau
 
 Get up and running in under 2 minutes:
 
-### Pick one path only
+### Step 1: Install the Plugin
-
-Most Claude Code users should use exactly one install path:
-
-- **Recommended default:** install the Claude Code plugin, then copy only the rule folders you actually want.
-- **Use the manual installer only if** you want finer-grained control, want to avoid the plugin path entirely, or your Claude Code build has trouble resolving the self-hosted marketplace entry.
-- **Do not stack install methods.** The most common broken setup is: `/plugin install` first, then `install.sh --profile full` or `npx ecc-install --profile full` afterward.
-
-If you already layered multiple installs and things look duplicated, skip straight to [Reset / Uninstall ECC](#reset--uninstall-ecc).
-
-### Step 1: Install the Plugin (Recommended)
 
 > NOTE: The plugin is convenient, but the OSS installer below is still the most reliable path if your Claude Code build has trouble resolving self-hosted marketplace entries.
 
@@ -207,11 +195,9 @@ This is intentional. Anthropic marketplace/plugin installs are keyed by a canoni
 >
 > If you already installed ECC via `/plugin install`, **do not run `./install.sh --profile full`, `.\install.ps1 --profile full`, or `npx ecc-install --profile full` afterward**. The plugin already loads ECC skills, commands, and hooks. Running the full installer after a plugin install copies those same surfaces into your user directories and can create duplicate skills plus duplicate runtime behavior.
 >
-> For plugin installs, manually copy only the `rules/` directories you want. Start with `rules/common` plus one language or framework pack you actually use. Do not copy every rules directory unless you explicitly want all of that context in Claude.
+> For plugin installs, manually copy only the `rules/` directories you want. Use the full installer only when you are doing a fully manual ECC install instead of the plugin path.
 >
-> Use the full installer only when you are doing a fully manual ECC install instead of the plugin path.
+> If your local Claude setup was wiped or reset, that does not mean you need to repurchase ECC. Start with `ecc list-installed`, then run `ecc doctor` and `ecc repair` before reinstalling anything. That usually restores ECC-managed files without rebuilding your setup. If the problem is account or marketplace access for ECC Tools, handle billing/account recovery separately.
->
-> If your local Claude setup was wiped or reset, that does not mean you need to repurchase ECC. Start with `node scripts/ecc.js list-installed`, then run `node scripts/ecc.js doctor` and `node scripts/ecc.js repair` before reinstalling anything. That usually restores ECC-managed files without rebuilding your setup. If the problem is account or marketplace access for ECC Tools, handle billing/account recovery separately.
 
 ```bash
 # Clone the repo first
@@ -245,57 +231,6 @@ Copy-Item -Recurse rules/typescript "$HOME/.claude/rules/"
 
 For manual install instructions see the README in the `rules/` folder. When copying rules manually, copy the whole language directory (for example `rules/common` or `rules/golang`), not the files inside it, so relative references keep working and filenames do not collide.
 
-### Fully manual install (Fallback)
-
-Use this only if you are intentionally skipping the plugin path:
-
-```bash
-./install.sh --profile full
-```
-
-```powershell
-.\install.ps1 --profile full
-# or
-npx ecc-install --profile full
-```
-
-If you choose this path, stop there. Do not also run `/plugin install`.
-
-### Reset / Uninstall ECC
-
-If ECC feels duplicated, intrusive, or broken, do not keep reinstalling it on top of itself.
-
-- **Plugin path:** remove the plugin from Claude Code, then delete the specific rule folders you manually copied under `~/.claude/rules/`.
-- **Manual installer / CLI path:** from the repo root, preview removal first:
-
-```bash
-node scripts/uninstall.js --dry-run
-```
-
-Then remove ECC-managed files:
-
-```bash
-node scripts/uninstall.js
-```
-
-You can also use the lifecycle wrapper:
-
-```bash
-node scripts/ecc.js list-installed
-node scripts/ecc.js doctor
-node scripts/ecc.js repair
-node scripts/ecc.js uninstall --dry-run
-```
-
-ECC only removes files recorded in its install-state. It will not delete unrelated files it did not install.
-
-If you stacked methods, clean up in this order:
-
-1. Remove the Claude Code plugin install.
-2. Run the ECC uninstall command from the repo root to remove install-state-managed files.
-3. Delete any extra rule folders you copied manually and no longer want.
-4. Reinstall once, using a single path.
-
 ### Step 3: Start Using
 
 ```bash
@@ -312,7 +247,7 @@ If you stacked methods, clean up in this order:
 /plugin list everything-claude-code@everything-claude-code
 ```
 
-**That's it!** You now have access to 48 agents, 184 skills, and 79 legacy command shims.
+**That's it!** You now have access to 48 agents, 183 skills, and 79 legacy command shims.
 
 ### Dashboard GUI
 
@@ -1280,7 +1215,7 @@ The configuration is automatically detected from `.opencode/opencode.json`.
 |---------|-------------|----------|--------|
 | Agents | PASS: 48 agents | PASS: 12 agents | **Claude Code leads** |
 | Commands | PASS: 79 commands | PASS: 31 commands | **Claude Code leads** |
-| Skills | PASS: 184 skills | PASS: 37 skills | **Claude Code leads** |
+| Skills | PASS: 183 skills | PASS: 37 skills | **Claude Code leads** |
 | Hooks | PASS: 8 event types | PASS: 11 events | **OpenCode has more!** |
 | Rules | PASS: 29 rules | PASS: 13 instructions | **Claude Code leads** |
 | MCP Servers | PASS: 14 servers | PASS: Full | **Full parity** |
@@ -1389,7 +1324,7 @@ ECC is the **first plugin to maximize every major AI coding tool**. Here's how e
 |---------|------------|------------|-----------|----------|
 | **Agents** | 48 | Shared (AGENTS.md) | Shared (AGENTS.md) | 12 |
 | **Commands** | 79 | Shared | Instruction-based | 31 |
-| **Skills** | 184 | Shared | 10 (native format) | 37 |
+| **Skills** | 183 | Shared | 10 (native format) | 37 |
 | **Hook Events** | 8 types | 15 types | None yet | 11 types |
 | **Hook Scripts** | 20+ scripts | 16 scripts (DRY adapter) | N/A | Plugin hooks |
 | **Rules** | 34 (common + lang) | 34 (YAML frontmatter) | Instruction-based | 13 instructions |
@@ -1399,7 +1334,7 @@ ECC is the **first plugin to maximize every major AI coding tool**. Here's how e
 | **Context File** | CLAUDE.md + AGENTS.md | AGENTS.md | AGENTS.md | AGENTS.md |
 | **Secret Detection** | Hook-based | beforeSubmitPrompt hook | Sandbox-based | Hook-based |
 | **Auto-Format** | PostToolUse hook | afterFileEdit hook | N/A | file.edited hook |
-| **Version** | Plugin | Plugin | Reference config | 2.0.0-rc.1 |
+| **Version** | Plugin | Plugin | Reference config | 1.10.0 |
 
 **Key architectural decisions:**
 - **AGENTS.md** at root is the universal cross-tool file (read by all 4 tools)

README.zh-CN.md

@@ -80,7 +80,7 @@
 
 ## 最新动态
 
-### v2.0.0-rc.1 — 表面同步、运营工作流与 ECC 2.0 Alpha（2026年4月）
+### v1.10.0 — 表面同步、运营工作流与 ECC 2.0 Alpha（2026年4月）
 
 - **公共表面已与真实仓库同步** —— 元数据、目录数量、插件清单以及安装文档现在都与实际开源表面保持一致。
 - **运营与外向型工作流扩展** —— `brand-voice`、`social-graph-ranker`、`customer-billing-ops`、`google-workspace-ops` 等运营型 skill 已纳入同一系统。
@@ -160,7 +160,7 @@ Copy-Item -Recurse rules/typescript "$HOME/.claude/rules/"
 /plugin list everything-claude-code@everything-claude-code
 ```
 
-**完成！** 你现在可以使用 48 个代理、184 个技能和 79 个命令。
+**完成！** 你现在可以使用 48 个代理、183 个技能和 79 个命令。
 
 ### multi-* 命令需要额外配置
 

VERSION

@@ -1 +1 @@
-2.0.0-rc.1
+1.10.0

agent.yaml

@@ -1,6 +1,6 @@
 spec_version: "0.1.0"
 name: everything-claude-code
-version: 2.0.0-rc.1
+version: 1.10.0
 description: "Initial gitagent export surface for ECC's shared skill catalog, governance, and identity. Native agents, commands, and hooks remain authoritative in the repository while manifest coverage expands."
 author: affaan-m
 license: MIT

docs/HERMES-SETUP.md

@@ -100,9 +100,9 @@ This stack is useful when you want:
 - automation that can nudge, audit, and escalate
 - a public repo that shows the system shape without exposing your private operator state
 
-## Public Release Candidate Scope
+## Public Preview Scope
 
-ECC v2.0.0-rc.1 documents the Hermes surface and ships launch collateral now.
+ECC 2.0 preview documents the Hermes surface and ships launch collateral now.
 
 The remaining private pieces can be layered later:
 

docs/SELECTIVE-INSTALL-ARCHITECTURE.md

@@ -703,7 +703,7 @@ Suggested payload:
     "skippedModules": []
   },
   "source": {
-    "repoVersion": "2.0.0-rc.1",
+    "repoVersion": "1.10.0",
     "repoCommit": "git-sha",
     "manifestVersion": 1
   },

docs/architecture/cross-harness.md

@@ -1,111 +0,0 @@
-# Cross-Harness Architecture
-
-ECC is the reusable workflow layer. Harnesses are execution surfaces.
-
-The goal is to keep the durable parts of agentic work in one repo:
-
-- skills
-- rules and instructions
-- hooks where the harness supports them
-- MCP configuration
-- install manifests
-- session and orchestration patterns
-
-Claude Code, Codex, OpenCode, Cursor, Gemini, and future harnesses should adapt those assets at the edge instead of requiring a new workflow model for every tool.
-
-## Portability Model
-
-| Surface | Shared Source | Harness Adapter | Current Status |
-|---------|---------------|-----------------|----------------|
-| Skills | `skills/*/SKILL.md` | Claude plugin, Codex plugin, `.agents/skills`, Cursor skill copies, OpenCode plugin/config | Supported with harness-specific packaging |
-| Rules and instructions | `rules/`, `AGENTS.md`, translated docs | Claude rules install, Codex `AGENTS.md`, Cursor rules, OpenCode instructions | Supported, but not identical across harnesses |
-| Hooks | `hooks/hooks.json`, `scripts/hooks/` | Claude native hooks, OpenCode plugin events, Cursor hook adapter | Hook-backed in Claude/OpenCode/Cursor; instruction-backed in Codex |
-| MCPs | `.mcp.json`, `mcp-configs/` | Native MCP config import per harness | Supported where the harness exposes MCP |
-| Commands | `commands/`, CLI scripts | Claude slash commands, compatibility shims, CLI entrypoints | Supported, but command semantics vary |
-| Sessions | `ecc2/`, session adapters, orchestration scripts | TUI/daemon, tmux/worktree orchestration, harness-specific runners | Alpha |
-
-## What Travels Unchanged
-
-`SKILL.md` is the most portable unit.
-
-A good ECC skill should:
-
-- use YAML frontmatter with `name`, `description`, and `origin`
-- describe when to use the skill
-- state required tools or connectors without embedding secrets
-- keep examples repo-relative or generic
-- avoid harness-only command assumptions unless the section is clearly labeled
-
-The same source skill can be installed into multiple harnesses because it is mostly instructions, constraints, and workflow shape.
-
-## What Gets Adapted
-
-Each harness has different loading and enforcement behavior:
-
-- Claude Code loads plugin assets and has native hook execution.
-- Codex reads `AGENTS.md`, plugin metadata, skills, and MCP config, but hook parity is instruction-driven.
-- OpenCode has a plugin/event system that can reuse ECC hook logic through an adapter layer.
-- Cursor uses its own rule and hook layout, so ECC maintains translated surfaces under `.cursor/`.
-- Gemini support is install/instruction oriented and should be treated as a compatibility surface, not as full hook parity.
-
-Adapters should stay thin. The shared behavior belongs in `skills/`, `rules/`, `hooks/`, `scripts/`, and `mcp-configs/`.
-
-## Hermes Boundary
-
-Hermes is not the public ECC runtime.
-
-Hermes is an operator shell that can consume ECC assets:
-
-- import selected ECC skills into a Hermes skills directory
-- use ECC MCP conventions for tool access
-- route chat, CLI, cron, and handoff workflows through reusable ECC patterns
-- distill repeated local operator work back into sanitized ECC skills
-
-The public repo should ship reusable patterns, not local Hermes state.
-
-Do ship:
-
-- sanitized setup docs
-- repo-relative demo prompts
-- general operator skills
-- examples that do not depend on private credentials
-
-Do not ship:
-
-- OAuth tokens or API keys
-- raw `~/.hermes` exports
-- personal workspace memory
-- private datasets
-- local-only automation packs that have not been reviewed
-
-## Today vs Later
-
-Supported today:
-
-- shared skill source in `skills/`
-- Claude Code plugin packaging
-- Codex plugin metadata and MCP reference config
-- OpenCode package/plugin surface
-- Cursor-adapted rules, hooks, and skills
-- `ecc2/` as an alpha Rust control plane
-
-Still maturing:
-
-- exact hook parity across all harnesses
-- automated skill sync into Hermes
-- release packaging for `ecc2/`
-- cross-harness session resume semantics
-- deeper memory and operator planning layers
-
-## Rule For New Work
-
-When adding a workflow, put the durable behavior in ECC first.
-
-Use harness-specific files only for:
-
-- loading the shared asset
-- adapting event shapes
-- mapping command names
-- handling platform limits
-
-If a workflow only works in one harness, document that boundary directly.

docs/fixes/HOOK-FIX-20260421-ADDENDUM.md

@@ -87,9 +87,9 @@ hook command が `"C:\Program Files\Git\bin\bash.exe" "C:\Users\...\wrapper.sh"`
 ### 回避策
 
 第1トークンを bash.exe のフルパス＋スペース付きパスにしないこと：
-1. `OK:` `bash` （PATH 解決の単一トークン）— 夜fix / hooks.json パターン
+1. ✅ `bash` （PATH 解決の単一トークン）— 夜fix / hooks.json パターン
-2. `OK:` `.sh` 直接パス（Claude Code の .sh ハンドリングに依存）— 朝fix
+2. ✅ `.sh` 直接パス（Claude Code の .sh ハンドリングに依存）— 朝fix
-3. `BAD:` `"C:\Program Files\Git\bin\bash.exe" "<path>"` — 1トークン目が quoted で空白込み
+3. ❌ `"C:\Program Files\Git\bin\bash.exe" "<path>"` — 1トークン目が quoted で空白込み
 
 ## 結論
 

docs/pt-BR/README.md

@@ -80,7 +80,7 @@ Este repositório contém apenas o código. Os guias explicam tudo.
 
 ## O Que Há de Novo
 
-### v2.0.0-rc.1 — Sincronização de Superfície, Fluxos Operacionais e ECC 2.0 Alpha (Abr 2026)
+### v1.10.0 — Sincronização de Superfície, Fluxos Operacionais e ECC 2.0 Alpha (Abr 2026)
 
 - **Superfície pública sincronizada com o repositório real** — metadados, contagens de catálogo, manifests de plugin e documentação de instalação agora refletem a superfície OSS que realmente é entregue.
 - **Expansão dos fluxos operacionais e externos** — `brand-voice`, `social-graph-ranker`, `customer-billing-ops`, `google-workspace-ops` e skills relacionadas fortalecem a trilha operacional dentro do mesmo sistema.

docs/releases/2.0.0-rc.1/article-outline.md

@@ -1,61 +0,0 @@
-# Article Outline - ECC v2.0.0-rc.1
-
-## Working Title
-
-Turning ECC Into a Cross-Harness Operator System
-
-## Core Argument
-
-Most agentic work breaks down because the tools stay isolated.
-
-The leverage comes from treating the harness, reusable workflow layer, and operator shell as one system:
-
-- skills for repeatable work
-- hooks and tests for enforcement
-- MCPs for tool access
-- memory and handoffs for continuity
-- one operator shell that can route daily execution
-
-## Structure
-
-### 1. The Problem
-
-- too many chat windows
-- too many tool-specific workflows
-- too much context living in personal habit instead of reusable system shape
-
-### 2. What ECC Already Solved
-
-- reusable skill format
-- cross-harness install surfaces
-- hooks and verification discipline
-- security and review patterns
-- operator workflow skills around content, research, and business ops
-
-### 3. Why Hermes Is the Operator Layer
-
-- chat, CLI, TUI, cron, and handoffs can sit above the reusable ECC layer
-- business and content work can run next to engineering work
-- the daily loop becomes easier to inspect and improve
-
-### 4. What Ships in rc.1
-
-- sanitized Hermes setup guide
-- release and distribution collateral
-- cross-harness architecture doc
-- Hermes import guidance
-- clearer 2.0 positioning in the repo
-
-### 5. What Stays Local
-
-- secrets and auth
-- raw workspace exports
-- personal datasets
-- operator-specific automations that have not been sanitized
-- deeper CRM, finance, and Google Workspace playbooks
-
-### 6. Closing Point
-
-The goal is not to copy one exact stack.
-
-The goal is to build an operator system that turns repeated work into reusable, measurable surfaces.

docs/releases/2.0.0-rc.1/demo-prompts.md

@@ -1,42 +0,0 @@
-# Hermes x ECC Demo Prompts
-
-## Prompt 1: ECC Builds ECC
-
-Use the current ECC repo and the public release pack at `docs/releases/2.0.0-rc.1/`.
-
-Do 4 things in order:
-
-1. Inspect git status and the current repo diff, then give me a concise ECC v2.0.0-rc.1 PR or release summary that proves ECC is being used to build ECC itself.
-2. Finalize one strong X thread.
-3. Finalize one strong LinkedIn post.
-4. Tell me the exact 3 recordings I should do next plus what Hermes can generate automatically after I record.
-
-Keep it decisive and practical.
-
-## Prompt 2: Turn Recording Into Assets
-
-Assume I just recorded:
-
-- one face-camera hook
-- one screen capture of Hermes using ECC to ship ECC v2.0.0-rc.1
-- one setup walkthrough of the Hermes x ECC workspace
-
-Give me:
-
-1. a short-form edit plan for X, LinkedIn, TikTok, and YouTube Shorts
-2. a voiceover script if I want to re-record clean audio
-3. the exact repo-relative filenames and folders I should use for raw footage
-4. the assets Hermes can generate automatically after I drop the files in place
-
-Keep it operational.
-
-## Prompt 3: Public Launch Push
-
-Using the ECC v2.0.0-rc.1 release pack, give me:
-
-1. one release tweet
-2. one follow-up tweet
-3. one LinkedIn comment I can paste under the post
-4. one short Telegram handoff I can send to Hermes later to keep distributing this launch across channels
-
-Make it sound like an operator shipping real work, not a launch thread cliche.

docs/releases/2.0.0-rc.1/launch-checklist.md

@@ -1,41 +0,0 @@
-# ECC v2.0.0-rc.1 Launch Checklist
-
-## Repo
-
-- verify local `main` is synced to `origin/main`
-- verify `docs/HERMES-SETUP.md` is present
-- verify `docs/architecture/cross-harness.md` is present
-- verify this release directory is committed
-- keep private tokens, personal docs, and raw workspace exports out of the repo
-
-## Release Surface
-
-- confirm package and plugin version policy for `2.0.0-rc.1` (drafted in manifest bump prep)
-- confirm whether `ecc2/Cargo.toml` moves from `0.1.0` to `2.0.0-rc.1`
-- update release metadata in one dedicated release-version PR
-- run the root test suite
-- run `cd ecc2 && cargo test`
-
-## Content
-
-- publish the X thread from `x-thread.md`
-- publish the LinkedIn draft from `linkedin-post.md`
-- use `article-outline.md` for the longer writeup
-- record one 30-60 second proof-of-work clip
-
-## Demo Asset Suggestions
-
-- Hermes plus ECC side by side
-- release docs being generated or reviewed from the repo
-- a workflow moving from brief to post to checklist
-- `ecc2/` dashboard or session surface with alpha framing
-
-## Messaging
-
-Use language like:
-
-- "release candidate"
-- "sanitized operator stack"
-- "cross-harness operating system for agentic work"
-- "ECC is the reusable substrate; Hermes is the operator shell"
-- "private/local integrations land after sanitization"

docs/releases/2.0.0-rc.1/linkedin-post.md

@@ -1,28 +0,0 @@
-# LinkedIn Draft - ECC v2.0.0-rc.1
-
-ECC v2.0.0-rc.1 is live as the first release-candidate pass at the 2.0 direction.
-
-The practical shift is simple: ECC is no longer framed as only a Claude Code plugin or config bundle.
-
-It is becoming a cross-harness operating system for agentic work:
-
-- reusable skills instead of one-off prompts
-- hooks and tests instead of manual discipline
-- MCP-backed access to docs, code, browser automation, and research
-- Codex, OpenCode, Cursor, Gemini, and Claude Code surfaces that share the same core workflow layer
-- Hermes as the operator shell for chat, cron, handoffs, and daily work routing
-
-For this release-candidate surface, I kept the repo honest.
-
-I did not publish private workspace state. I shipped the reusable layer:
-
-- sanitized Hermes setup documentation
-- release notes and launch collateral
-- cross-harness architecture notes
-- Hermes import guidance for turning local operator patterns into public ECC skills
-
-The leverage is not just better prompting.
-
-It is reducing the number of isolated surfaces, turning repeated workflows into reusable skills, and making the operating system around the agent measurable.
-
-There is still more to harden before GA, especially around packaging, installers, and the `ecc2/` control plane. But rc.1 is enough to show the shape clearly.

docs/releases/2.0.0-rc.1/release-notes.md

@@ -1,54 +0,0 @@
-# ECC v2.0.0-rc.1 Release Notes
-
-## Positioning
-
-ECC v2.0.0-rc.1 is the first release-candidate surface for ECC as a cross-harness operating system for agentic work.
-
-Claude Code remains a core target. Codex, OpenCode, Cursor, Gemini, and other harnesses are treated as execution surfaces that can share the same skills, rules, MCP conventions, and operator workflows. ECC is the reusable substrate; Hermes is documented as the operator shell that can sit on top of that layer.
-
-## What Changed
-
-- Added the sanitized Hermes setup guide to the public release story.
-- Added launch collateral in-repo so the release can ship from one reviewed surface.
-- Clarified the split between ECC as the reusable substrate and Hermes as the operator shell.
-- Documented the cross-harness portability model for skills, hooks, MCPs, rules, and instructions.
-- Added a Hermes import playbook for turning local operator patterns into publishable ECC skills.
-
-## Why This Matters
-
-ECC is no longer only a Claude Code plugin or config bundle.
-
-The system now has a clearer shape:
-
-- reusable skills instead of one-off prompts
-- hooks and tests for workflow discipline
-- MCP-backed access to docs, code, browser automation, and research
-- cross-harness install surfaces for Claude Code, Codex, OpenCode, Cursor, and related tools
-- Hermes as an optional operator shell for chat, cron, handoffs, and daily work routing
-
-## Preview Boundaries
-
-This is a release candidate, not the final GA claim.
-
-What ships in this surface:
-
-- public Hermes setup documentation
-- release notes and launch collateral
-- cross-harness architecture documentation
-- Hermes import guidance for sanitized operator workflows
-
-What stays local:
-
-- secrets, OAuth tokens, and API keys
-- private workspace exports
-- personal datasets
-- operator-specific automations that have not been sanitized
-- deeper CRM, finance, and Google Workspace playbooks
-
-## Upgrade Motion
-
-1. Read the [Hermes setup guide](../../HERMES-SETUP.md).
-2. Review the [cross-harness architecture](../../architecture/cross-harness.md).
-3. Start with one workflow lane: engineering, research, content, or outreach.
-4. Import only sanitized operator patterns into ECC skills.
-5. Treat `ecc2/` as an alpha control plane until release packaging and installer behavior are finalized.

docs/releases/2.0.0-rc.1/telegram-handoff.md

@@ -1,26 +0,0 @@
-# Telegram Handoff For Hermes
-
-Send this to Hermes when you want it to help package the launch workflow.
-
-```text
-Use the public ECC release pack in the repo:
-
-- docs/releases/2.0.0-rc.1/release-notes.md
-- docs/releases/2.0.0-rc.1/x-thread.md
-- docs/releases/2.0.0-rc.1/linkedin-post.md
-- docs/releases/2.0.0-rc.1/article-outline.md
-- docs/releases/2.0.0-rc.1/launch-checklist.md
-- docs/HERMES-SETUP.md
-- docs/architecture/cross-harness.md
-
-Task:
-
-1. Finalize one strong X thread for ECC v2.0.0-rc.1.
-2. Finalize one strong LinkedIn post for ECC v2.0.0-rc.1.
-3. Give me one 30-60 second Hermes x ECC video script and one 15-30 second variant.
-4. Tell me exactly what to record now with screen capture, face camera, and voice lines.
-5. Tell me what Hermes can generate automatically after I record.
-6. End with a minimal checklist of the assets or logins still needed.
-
-Be decisive. Return final drafts plus a practical recording checklist.
-```

docs/releases/2.0.0-rc.1/x-thread.md

@@ -1,65 +0,0 @@
-# X Thread Draft - ECC v2.0.0-rc.1
-
-1/ ECC v2.0.0-rc.1 is the first release-candidate pass at the 2.0 direction.
-
-The repo is moving from a Claude Code config pack into a cross-harness operating system for agentic work.
-
-2/ The important split:
-
-ECC is the reusable substrate.
-Hermes is the operator shell that can run on top.
-
-Skills, hooks, MCP configs, rules, and workflow packs live in ECC.
-
-3/ Claude Code is still a core target.
-
-Codex, OpenCode, Cursor, Gemini, and other harnesses are part of the same story now.
-
-The goal is fewer one-off harness tricks and more reusable workflow surface.
-
-4/ The rc.1 surface ships the public pieces:
-
-- Hermes setup guide
-- release notes
-- launch checklist
-- X and LinkedIn drafts
-- cross-harness architecture doc
-- Hermes import guidance
-
-5/ It does not ship private workspace state.
-
-No secrets.
-No OAuth tokens.
-No raw local exports.
-No personal datasets.
-
-The point is to publish the reusable system shape.
-
-6/ Why Hermes matters:
-
-Most agent systems fail in the daily operating loop.
-
-They can code, but they do not keep research, content, handoffs, reminders, and execution in one measurable surface.
-
-7/ ECC gives the reusable layer.
-
-Hermes gives the operator shell.
-
-Together they make the work feel less like scattered chat windows and more like a system you can run.
-
-8/ This is still a release candidate.
-
-The public docs and reusable surfaces are ready for review.
-
-The deeper local integrations stay local until they are sanitized.
-
-9/ Start here:
-
-Repo:
-<https://github.com/affaan-m/everything-claude-code>
-
-Hermes x ECC setup:
-<https://github.com/affaan-m/everything-claude-code/blob/main/docs/HERMES-SETUP.md>
-
-Release notes:
-<https://github.com/affaan-m/everything-claude-code/blob/main/docs/releases/2.0.0-rc.1/release-notes.md>

docs/tr/AGENTS.md

@@ -2,7 +2,7 @@
 
 Bu, yazılım geliştirme için 28 özel agent, 116 skill, 59 command ve otomatik hook iş akışları sağlayan **üretime hazır bir AI kodlama eklentisidir**.
 
-**Sürüm:** 2.0.0-rc.1
+**Sürüm:** 1.10.0
 
 ## Temel İlkeler
 

docs/tr/README.md

@@ -79,7 +79,7 @@ Bu repository yalnızca ham kodu içerir. Rehberler her şeyi açıklıyor.
 
 ## Yenilikler
 
-### v2.0.0-rc.1 — Surface Sync, Operatör İş Akışları ve ECC 2.0 Alpha (Nis 2026)
+### v1.10.0 — Surface Sync, Operatör İş Akışları ve ECC 2.0 Alpha (Nis 2026)
 
 - **Public surface canlı repo ile senkronlandı** — metadata, katalog sayıları, plugin manifest'leri ve kurulum odaklı dokümanlar artık gerçek OSS yüzeyiyle eşleşiyor.
 - **Operatör ve dışa dönük iş akışları büyüdü** — `brand-voice`, `social-graph-ranker`, `customer-billing-ops`, `google-workspace-ops` ve ilgili operatör skill'leri aynı sistem içinde tamamlandı.

docs/zh-CN/AGENTS.md

@@ -1,8 +1,8 @@
 # Everything Claude Code (ECC) — 智能体指令
 
-这是一个**生产就绪的 AI 编码插件**，提供 48 个专业代理、184 项技能、79 条命令以及自动化钩子工作流，用于软件开发。
+这是一个**生产就绪的 AI 编码插件**，提供 48 个专业代理、183 项技能、79 条命令以及自动化钩子工作流，用于软件开发。
 
-**版本:** 2.0.0-rc.1
+**版本:** 1.10.0
 
 ## 核心原则
 
@@ -147,7 +147,7 @@
 
 ```
 agents/          — 48 个专业子代理
-skills/          — 184 个工作流技能和领域知识
+skills/          — 183 个工作流技能和领域知识
 commands/        — 79 个斜杠命令
 hooks/           — 基于触发的自动化
 rules/           — 始终遵循的指导方针（通用 + 每种语言）