el-vaporublisted

# ¿Te duele? Ponte Vaporub Before you theorize, rule out the mess you made yourself. ## Rule Most surprising failures are the agent's own stale state, not the system's behavior. So you run one cheap ladder of checks **first**, once, before forming any theory — and then you never run it again on that same unchanged failure. The single pass is the remedy; a second pass is a substitute for thinking. ## Procedure Run every rung once, in order. Each rung has a check and a tell — the tell is how you know whether that rung was the problem. 1. **Unsaved file.** Re-read the file you edited from disk. *Tell:* the edit is missing or the content differs from what you believe you wrote. 2. **Stale process.** Identify the running process, server, watcher, or REPL and restart it. *Tell:* it was started before your edit, or its log shows no reload. 3. **Stale cache or artifact.** Clear the relevant build, module, bundler, or test cache and rebuild. *Tell:* the failure changes or disappears after the clean rebuild. 4. **Wrong branch or worktree.** Check the current branch, the working directory, and whether another worktree or checkout of this repo exists. *Tell:* you are not on the branch the change landed on, or the running path is not the path you edited. 5. **Wrong file.** Confirm the file being executed is the file you edited — resolved import path, installed vs. local copy, `dist/` vs. `src/`, a shadowing duplicate. *Tell:* two files match the name, or the imp