solid-looplisted

# Solid Loop Correct the agent system from friction notes while keeping every skill as small as the fix allows. The root virtue is **predictability**: each instruction sends the next run straight to the work, with no detour and no unneeded read. ## Apply Friction Notes Friction notes arrive classified as `misdirection` or `gap` by the `aaaav-do` reflexive pass. 1. **Correct each misdirection.** Open the line named in `Led by`. Rewrite it to state what `Found` established, or delete it when the line has no correct form. 2. **Place each gap.** Search the agent system for a statement of the `Found` fact. - When one exists, the run could not reach it: sharpen the context pointer or description that should have led there. - When none exists, write the fact as one direct sentence in its owning location: project facts in `AGENTS.md` or `CLAUDE.md`, procedure in the skill that ran the step. - Scaffold a new skill from [references/template-skill.md](references/template-skill.md) only when the gap is a multi-step procedure that no skill owns. - A fact the change itself resolved, or a general tool-use slip that no project or skill owns, needs no placement. 3. **Hold the size.** Run the no-op test on every section you edited and delete each sentence that fails. Keep each `SKILL.md` under 300 lines; disclose reference into `references/` when it grows past that. **Complete when:** every note has an action or is marked resolved by the change, and every edited section has p