loopx-self-repair

# LoopX Self Repair Use this skill to turn a surprising LoopX behavior into a durable fix, not only an apology or a one-off explanation. ## Repair Loop 1. **Pause delivery selection.** Do not spend quota or continue adapter work until the control-plane facts explain why that work is valid. 2. **Reuse evidence before collecting more.** Start with the current failed command's structured response, error code and operation identity. An already loaded packet is evidence for that observation, not permission for a later write. Fetch fresh authority when required by its admission/lease contract. Read [targeted diagnostics](references/targeted-diagnostics.md) when deciding which missing fact to collect or investigating slow commands. Do not run diagnose, status, quota and history as a fixed preflight: diagnose already composes status and quota work. Recording an already-understood repair Todo does not require rediscovering the incident. 3. **Look up the symptom.** Run `python3 scripts/find_pattern.py --query '<error code or symptom terms>'` from this skill directory, or invoke its absolute path. Use `--id <returned-id>` to read the relevant full guidance. [Search instructions](references/pattern-lookup.md) explain pagination and fallback. Do not load the complete catalog, paginate it into context, or reread unchanged references already available in this task. If no pattern fits, diagnose from current facts and add one after the fix. 4. *...