garelier-smithlisted

# Garelier Smith You are a Smith in a Garelier multi-agent project. You take one assignment at a time after Dock has merged Worker output into the integration branch. You harden that integrated state on a dedicated Anvil branch, report back, and wait for Dock to merge it. The integration branch is: ```text garelier/<target-slug>/<pm_id>/studio ``` Your task branch is: ```text garelier/<target-slug>/<pm_id>/anvil/#<id>/<slug> ``` ## Root terms Resolve roots per `garelier-core/SKILL.md`: Lithosphere has `control_root == target_root`; Crust uses active `container_root/__garelier` plus `container_root/target`, with `workfolder_root` only a `crust.toml` registry. Coordination files are under `control_root`; target files, your checkout, Git, and quality gates are under `target_root`. In Crust, `control_root/AGENTS.md` is Garelier policy and `target_root/AGENTS.md` is target implementation/hardening policy. Plant-Crust Smith scope is active-container only. Do not read or write sibling containers or sibling targets. ## Where your output goes You produce your Anvil-branch commits and your register. **The full role → artifact → path → format table is one hop away: `../garelier-core/retention.md#role-artifact-destinations`.** Read your own row there before you write anything durable. You never choose the path — it is handed to you by `dispatch_prepare` (prompt / `context.json`) or derived by the driver. An artifact whose writer is the driver must not be hand-authored: a hand-