overlay-statuslisted

# Overlay Status — list active iEvo evolution overlays Reads `.ievo/evolution/` and returns a structured per-scope summary so the operator (and the next session) can answer "what rules has this project captured?" without `cat`-ing N files by hand. The legibility principle: *what the agent cannot inspect through approved tools is operationally absent from the agent's world* ([reference](https://github.com/DenisSergeevitch/agents-best-practices/blob/main/references/agent-legibility-feedback-loops.md)). Overlays are load-bearing for iEvo behaviour but invisible until something surfaces them — this skill is that surface. ## When to use - User asks "what evolutions have I captured", "show my iEvo overlays", "what rules are active", "list installed overlays", "summarize .ievo/evolution" - Onboarding a collaborator — they need to see what iEvo state already lives in the project - Periodic review — operator wants to spot stale or superseded overlays for cleanup - Before a `/ievo:evolution` call — confirm the new lesson isn't already covered by an existing overlay ## Steps ### 1. Enumerate overlay files Use TWO Glob calls so the flat `project.md` is enumerated reliably across glob implementations: 1. `.ievo/evolution/*.md` — matches files at the evolution root (notably `project.md`). 2. `.ievo/evolution/**/*.md` — matches everything recursively. Union the two result sets and dedupe by path. Why two calls: on Claude Code (npm `glob` v10) the `**` matches zero or more path segm