kodelyth-ecc 2.19.0 → 2.20.0

package/.aider-ecc/skills/enterprise-agent-ops/SKILL.md

@@ -1,50 +0,0 @@
----
-name: enterprise-agent-ops
-description: Operate long-lived agent workloads with observability, security boundaries, and lifecycle management.
-origin: ECC
----
-
-# Enterprise Agent Ops
-
-Use this skill for cloud-hosted or continuously running agent systems that need operational controls beyond single CLI sessions.
-
-## Operational Domains
-
-1. runtime lifecycle (start, pause, stop, restart)
-2. observability (logs, metrics, traces)
-3. safety controls (scopes, permissions, kill switches)
-4. change management (rollout, rollback, audit)
-
-## Baseline Controls
-
-- immutable deployment artifacts
-- least-privilege credentials
-- environment-level secret injection
-- hard timeout and retry budgets
-- audit log for high-risk actions
-
-## Metrics to Track
-
-- success rate
-- mean retries per task
-- time to recovery
-- cost per successful task
-- failure class distribution
-
-## Incident Pattern
-
-When failure spikes:
-1. freeze new rollout
-2. capture representative traces
-3. isolate failing route
-4. patch with smallest safe change
-5. run regression + security checks
-6. resume gradually
-
-## Deployment Integrations
-
-This skill pairs with:
-- PM2 workflows
-- systemd services
-- container orchestrators
-- CI/CD gates

package/.aider-ecc/skills/eval-harness/SKILL.md

@@ -1,270 +0,0 @@
----
-name: eval-harness
-description: Formal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles
-origin: ECC
-tools: Read, Write, Edit, Bash, Grep, Glob
----
-
-# Eval Harness Skill
-
-A formal evaluation framework for Claude Code sessions, implementing eval-driven development (EDD) principles.
-
-## When to Activate
-
-- Setting up eval-driven development (EDD) for AI-assisted workflows
-- Defining pass/fail criteria for Claude Code task completion
-- Measuring agent reliability with pass@k metrics
-- Creating regression test suites for prompt or agent changes
-- Benchmarking agent performance across model versions
-
-## Philosophy
-
-Eval-Driven Development treats evals as the "unit tests of AI development":
-- Define expected behavior BEFORE implementation
-- Run evals continuously during development
-- Track regressions with each change
-- Use pass@k metrics for reliability measurement
-
-## Eval Types
-
-### Capability Evals
-Test if Claude can do something it couldn't before:
-```markdown
-[CAPABILITY EVAL: feature-name]
-Task: Description of what Claude should accomplish
-Success Criteria:
-  - [ ] Criterion 1
-  - [ ] Criterion 2
-  - [ ] Criterion 3
-Expected Output: Description of expected result
-```
-
-### Regression Evals
-Ensure changes don't break existing functionality:
-```markdown
-[REGRESSION EVAL: feature-name]
-Baseline: SHA or checkpoint name
-Tests:
-  - existing-test-1: PASS/FAIL
-  - existing-test-2: PASS/FAIL
-  - existing-test-3: PASS/FAIL
-Result: X/Y passed (previously Y/Y)
-```
-
-## Grader Types
-
-### 1. Code-Based Grader
-Deterministic checks using code:
-```bash
-# Check if file contains expected pattern
-grep -q "export function handleAuth" src/auth.ts && echo "PASS" || echo "FAIL"
-
-# Check if tests pass
-npm test -- --testPathPattern="auth" && echo "PASS" || echo "FAIL"
-
-# Check if build succeeds
-npm run build && echo "PASS" || echo "FAIL"
-```
-
-### 2. Model-Based Grader
-Use Claude to evaluate open-ended outputs:
-```markdown
-[MODEL GRADER PROMPT]
-Evaluate the following code change:
-1. Does it solve the stated problem?
-2. Is it well-structured?
-3. Are edge cases handled?
-4. Is error handling appropriate?
-
-Score: 1-5 (1=poor, 5=excellent)
-Reasoning: [explanation]
-```
-
-### 3. Human Grader
-Flag for manual review:
-```markdown
-[HUMAN REVIEW REQUIRED]
-Change: Description of what changed
-Reason: Why human review is needed
-Risk Level: LOW/MEDIUM/HIGH
-```
-
-## Metrics
-
-### pass@k
-"At least one success in k attempts"
-- pass@1: First attempt success rate
-- pass@3: Success within 3 attempts
-- Typical target: pass@3 > 90%
-
-### pass^k
-"All k trials succeed"
-- Higher bar for reliability
-- pass^3: 3 consecutive successes
-- Use for critical paths
-
-## Eval Workflow
-
-### 1. Define (Before Coding)
-```markdown
-## EVAL DEFINITION: feature-xyz
-
-### Capability Evals
-1. Can create new user account
-2. Can validate email format
-3. Can hash password securely
-
-### Regression Evals
-1. Existing login still works
-2. Session management unchanged
-3. Logout flow intact
-
-### Success Metrics
-- pass@3 > 90% for capability evals
-- pass^3 = 100% for regression evals
-```
-
-### 2. Implement
-Write code to pass the defined evals.
-
-### 3. Evaluate
-```bash
-# Run capability evals
-[Run each capability eval, record PASS/FAIL]
-
-# Run regression evals
-npm test -- --testPathPattern="existing"
-
-# Generate report
-```
-
-### 4. Report
-```markdown
-EVAL REPORT: feature-xyz
-========================
-
-Capability Evals:
-  create-user:     PASS (pass@1)
-  validate-email:  PASS (pass@2)
-  hash-password:   PASS (pass@1)
-  Overall:         3/3 passed
-
-Regression Evals:
-  login-flow:      PASS
-  session-mgmt:    PASS
-  logout-flow:     PASS
-  Overall:         3/3 passed
-
-Metrics:
-  pass@1: 67% (2/3)
-  pass@3: 100% (3/3)
-
-Status: READY FOR REVIEW
-```
-
-## Integration Patterns
-
-### Pre-Implementation
-```
-/eval define feature-name
-```
-Creates eval definition file at `.claude/evals/feature-name.md`
-
-### During Implementation
-```
-/eval check feature-name
-```
-Runs current evals and reports status
-
-### Post-Implementation
-```
-/eval report feature-name
-```
-Generates full eval report
-
-## Eval Storage
-
-Store evals in project:
-```
-.claude/
-  evals/
-    feature-xyz.md      # Eval definition
-    feature-xyz.log     # Eval run history
-    baseline.json       # Regression baselines
-```
-
-## Best Practices
-
-1. **Define evals BEFORE coding** - Forces clear thinking about success criteria
-2. **Run evals frequently** - Catch regressions early
-3. **Track pass@k over time** - Monitor reliability trends
-4. **Use code graders when possible** - Deterministic > probabilistic
-5. **Human review for security** - Never fully automate security checks
-6. **Keep evals fast** - Slow evals don't get run
-7. **Version evals with code** - Evals are first-class artifacts
-
-## Example: Adding Authentication
-
-```markdown
-## EVAL: add-authentication
-
-### Phase 1: Define (10 min)
-Capability Evals:
-- [ ] User can register with email/password
-- [ ] User can login with valid credentials
-- [ ] Invalid credentials rejected with proper error
-- [ ] Sessions persist across page reloads
-- [ ] Logout clears session
-
-Regression Evals:
-- [ ] Public routes still accessible
-- [ ] API responses unchanged
-- [ ] Database schema compatible
-
-### Phase 2: Implement (varies)
-[Write code]
-
-### Phase 3: Evaluate
-Run: /eval check add-authentication
-
-### Phase 4: Report
-EVAL REPORT: add-authentication
-==============================
-Capability: 5/5 passed (pass@3: 100%)
-Regression: 3/3 passed (pass^3: 100%)
-Status: SHIP IT
-```
-
-## Product Evals (v1.8)
-
-Use product evals when behavior quality cannot be captured by unit tests alone.
-
-### Grader Types
-
-1. Code grader (deterministic assertions)
-2. Rule grader (regex/schema constraints)
-3. Model grader (LLM-as-judge rubric)
-4. Human grader (manual adjudication for ambiguous outputs)
-
-### pass@k Guidance
-
-- `pass@1`: direct reliability
-- `pass@3`: practical reliability under controlled retries
-- `pass^3`: stability test (all 3 runs must pass)
-
-Recommended thresholds:
-- Capability evals: pass@3 >= 0.90
-- Regression evals: pass^3 = 1.00 for release-critical paths
-
-### Eval Anti-Patterns
-
-- Overfitting prompts to known eval examples
-- Measuring only happy-path outputs
-- Ignoring cost and latency drift while chasing pass rates
-- Allowing flaky graders in release gates
-
-### Minimal Eval Artifact Layout
-
-- `.claude/evals/<feature>.md` definition
-- `.claude/evals/<feature>.log` run history
-- `docs/releases/<version>/eval-summary.md` release snapshot

package/.aider-ecc/skills/evm-token-decimals/SKILL.md

@@ -1,130 +0,0 @@
----
-name: evm-token-decimals
-description: Prevent silent decimal mismatch bugs across EVM chains. Covers runtime decimal lookup, chain-aware caching, bridged-token precision drift, and safe normalization for bots, dashboards, and DeFi tools.
-origin: ECC direct-port adaptation
-version: "1.0.0"
----
-
-# EVM Token Decimals
-
-Silent decimal mismatches are one of the easiest ways to ship balances or USD values that are off by orders of magnitude without throwing an error.
-
-## When to Use
-
-- Reading ERC-20 balances in Python, TypeScript, or Solidity
-- Calculating fiat values from on-chain balances
-- Comparing token amounts across multiple EVM chains
-- Handling bridged assets
-- Building portfolio trackers, bots, or aggregators
-
-## How It Works
-
-Never assume stablecoins use the same decimals everywhere. Query `decimals()` at runtime, cache by `(chain_id, token_address)`, and use decimal-safe math for value calculations.
-
-## Examples
-
-### Query decimals at runtime
-
-```python
-from decimal import Decimal
-from web3 import Web3
-
-ERC20_ABI = [
-    {"name": "decimals", "type": "function", "inputs": [],
-     "outputs": [{"type": "uint8"}], "stateMutability": "view"},
-    {"name": "balanceOf", "type": "function",
-     "inputs": [{"name": "account", "type": "address"}],
-     "outputs": [{"type": "uint256"}], "stateMutability": "view"},
-]
-
-def get_token_balance(w3: Web3, token_address: str, wallet: str) -> Decimal:
-    contract = w3.eth.contract(
-        address=Web3.to_checksum_address(token_address),
-        abi=ERC20_ABI,
-    )
-    decimals = contract.functions.decimals().call()
-    raw = contract.functions.balanceOf(Web3.to_checksum_address(wallet)).call()
-    return Decimal(raw) / Decimal(10 ** decimals)
-```
-
-Do not hardcode `1_000_000` because a symbol usually has 6 decimals somewhere else.
-
-### Cache by chain and token
-
-```python
-from functools import lru_cache
-
-@lru_cache(maxsize=512)
-def get_decimals(chain_id: int, token_address: str) -> int:
-    w3 = get_web3_for_chain(chain_id)
-    contract = w3.eth.contract(
-        address=Web3.to_checksum_address(token_address),
-        abi=ERC20_ABI,
-    )
-    return contract.functions.decimals().call()
-```
-
-### Handle odd tokens defensively
-
-```python
-try:
-    decimals = contract.functions.decimals().call()
-except Exception:
-    logging.warning(
-        "decimals() reverted on %s (chain %s), defaulting to 18",
-        token_address,
-        chain_id,
-    )
-    decimals = 18
-```
-
-Log the fallback and keep it visible. Old or non-standard tokens still exist.
-
-### Normalize to 18-decimal WAD in Solidity
-
-```solidity
-interface IERC20Metadata {
-    function decimals() external view returns (uint8);
-}
-
-function normalizeToWad(address token, uint256 amount) internal view returns (uint256) {
-    uint8 d = IERC20Metadata(token).decimals();
-    if (d == 18) return amount;
-    if (d < 18) return amount * 10 ** (18 - d);
-    return amount / 10 ** (d - 18);
-}
-```
-
-### TypeScript with ethers
-
-```typescript
-import { Contract, formatUnits } from 'ethers';
-
-const ERC20_ABI = [
-  'function decimals() view returns (uint8)',
-  'function balanceOf(address) view returns (uint256)',
-];
-
-async function getBalance(provider: any, tokenAddress: string, wallet: string): Promise<string> {
-  const token = new Contract(tokenAddress, ERC20_ABI, provider);
-  const [decimals, raw] = await Promise.all([
-    token.decimals(),
-    token.balanceOf(wallet),
-  ]);
-  return formatUnits(raw, decimals);
-}
-```
-
-### Quick on-chain check
-
-```bash
-cast call <token_address> "decimals()(uint8)" --rpc-url <rpc>
-```
-
-## Rules
-
-- Always query `decimals()` at runtime
-- Cache by chain plus token address, not symbol
-- Use `Decimal`, `BigInt`, or equivalent exact math, not float
-- Re-query decimals after bridging or wrapper changes
-- Normalize internal accounting consistently before comparison or pricing

package/.aider-ecc/skills/exa-search/SKILL.md

@@ -1,103 +0,0 @@
----
-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
-
-Neural search for web content, code, companies, and people via the Exa MCP server.
-
-## When to Activate
-
-- User needs current web information or news
-- Searching for code examples, API docs, or technical references
-- Researching companies, competitors, or market players
-- Finding professional profiles or people in a domain
-- Running background research for any development task
-- User says "search for", "look up", "find", or "what's the latest on"
-
-## MCP Requirement
-
-Exa MCP server must be configured. Add to `~/.claude.json`:
-
-```json
-"exa-web-search": {
-  "command": "npx",
-  "args": ["-y", "exa-mcp-server"],
-  "env": { "EXA_API_KEY": "YOUR_EXA_API_KEY_HERE" }
-}
-```
-
-Get an API key at [exa.ai](https://exa.ai).
-This repo's current Exa setup documents the tool surface exposed here: `web_search_exa` and `get_code_context_exa`.
-If your Exa server exposes additional tools, verify their exact names before depending on them in docs or prompts.
-
-## Core Tools
-
-### web_search_exa
-General web search for current information, news, or facts.
-
-```
-web_search_exa(query: "latest AI developments 2026", numResults: 5)
-```
-
-**Parameters:**
-
-| Param | Type | Default | Notes |
-|-------|------|---------|-------|
-| `query` | string | required | Search query |
-| `numResults` | number | 8 | Number of results |
-| `type` | string | `auto` | Search mode |
-| `livecrawl` | string | `fallback` | Prefer live crawling when needed |
-| `category` | string | none | Optional focus such as `company` or `research paper` |
-
-### get_code_context_exa
-Find code examples and documentation from GitHub, Stack Overflow, and docs sites.
-
-```
-get_code_context_exa(query: "Python asyncio patterns", tokensNum: 3000)
-```
-
-**Parameters:**
-
-| Param | Type | Default | Notes |
-|-------|------|---------|-------|
-| `query` | string | required | Code or API search query |
-| `tokensNum` | number | 5000 | Content tokens (1000-50000) |
-
-## Usage Patterns
-
-### Quick Lookup
-```
-web_search_exa(query: "Node.js 22 new features", numResults: 3)
-```
-
-### Code Research
-```
-get_code_context_exa(query: "Rust error handling patterns Result type", tokensNum: 3000)
-```
-
-### Company or People Research
-```
-web_search_exa(query: "Vercel funding valuation 2026", numResults: 3, category: "company")
-web_search_exa(query: "site:linkedin.com/in AI safety researchers Anthropic", numResults: 5)
-```
-
-### Technical Deep Dive
-```
-web_search_exa(query: "WebAssembly component model status and adoption", numResults: 5)
-get_code_context_exa(query: "WebAssembly component model examples", tokensNum: 4000)
-```
-
-## Tips
-
-- Use `web_search_exa` for current information, company lookups, and broad discovery
-- Use search operators like `site:`, quoted phrases, and `intitle:` to narrow results
-- Lower `tokensNum` (1000-2000) for focused code snippets, higher (5000+) for comprehensive context
-- Use `get_code_context_exa` when you need API usage or code examples rather than general web pages
-
-## Related Skills
-
-- `deep-research` — Full research workflow using firecrawl + exa together
-- `market-research` — Business-oriented research with decision frameworks