hermit-evolutionlisted

# Hermit Evolution Synthesize a compact analytical snapshot of the hermit's trajectory over recent weeks: cost trend, autonomy rate, and how fast proposals move through the pipeline. ## Step 0 — Channel reply If this skill was invoked from a channel-arrived message (the inbound prompt contains a `<channel source="...">` tag), reply via that channel's reply tool. Otherwise emit to conversation. ## Scope Read the following (gracefully skip any file that doesn't exist): 1. `.claude-code-hermit/compiled/review-weekly-*.md` — glob all, sort by `week` frontmatter descending, read the 8 most recent. Extract per-file: `week`, `total_cost_usd`, `self_directed_rate`, `proposals_created`, `proposals_resolved`. 2. `.claude-code-hermit/cost-summary.md` — frontmatter `total_cost_usd` and `total_tokens` for the current (partial) week's running total if the review file for the current week doesn't exist yet. 3. `.claude-code-hermit/state/proposal-metrics.jsonl` — if present, scan from the end (most recent entries first); stop once entries are older than 30 days. Use `resolved_at` and `created_at` to compute resolution days for recently resolved proposals. ## Analysis **Cost:** From review files, extract `total_cost_usd` per week. Show the 4 most recent weeks as a trend. Compute Δ% between the most recent and the preceding week. If fewer than 2 reviews exist, show "not enough data". **Autonomy:** From review files, extract `self_directed_rate` (fraction of sessions with no operator t