worklisted

# Working a step You were dispatched by a supervisor to do **one step** of **one task**. Not the task. Not the next step you can see. One step, and then a report. Your shell may start anywhere, so **every path below is absolute and every git command is `git -C "$REPO"`**. A bare `git commit` from the wrong directory commits the wrong thing, or nothing you meant. ## 1. Your inputs The prompt that dispatched you carries these. Every one is required; if any is missing, stop and report `BLOCKED` with `notes: missing input <name>`. ``` TASK: T-n STEP: S-n ROLE: <your role> REPO: <absolute path of the project root> SCOPE: <absolute paths you may write, one per line> GOAL: <what this step must achieve> STEP-VERIFY: <the exact command that judges this step> REQUIREMENTS: <the R-n this step serves> ENV: <pin id, and the pinned versions> CONTAINMENT: structural | guard-only SANDBOX-ROOT: <absolute path, or `none` under guard-only> ATTRIBUTION: <commit trailer lines, verbatim> TREE: clean | dirty NOTES: none | <a verifier FAIL, a predecessor's death, an answer from the client> ``` **`CONTAINMENT: structural` means you are inside a sandbox**, and three things follow that nothing else in your dispatch tells you: - **You are at the repository's own path, and nothing outside it exists.** The path in `REPO:` is the same string inside as out — deliberately, so that every scope, refusal and check reads the same in both places. But the rest of the filesystem is re