setuplisted

# /forged:setup Configure the operator environment shared by lead agents and Forged. Setup is non-invasive: all durable state lives under `ANVIL_HOME` and `BEADS_DIR`, while target repositories are identified by native `metadata.repository`. Pi package installation provides only skills, extensions, and tools; it never installs the Forged binary. ## Boundaries - Default `ANVIL_HOME` is `$HOME/.anvil`. - Default `BEADS_DIR` is `$ANVIL_HOME/beads`; an existing override wins. - Beads must report semver `>=1.2.1` and expose the required epic and lease commands; behavioral and schema probes remain the compatibility authority. - Setup and the bundled bootstrap never install or upgrade `bd`. - Never initialize Beads from a target checkout or add `.beads`, hooks, agent files, settings, or workflow files there. - Never install or modify shell profiles without explicit operator consent. - Setup validates local tools and configuration only. It does not install the Forged binary, create work, route work, start a run, or contact a separate issue tracker. - Rolling execution requires a dedicated read-only `assessment` roster role; its selected provider/model must be independent of every critique candidate. ## Locate this plugin portably Resolve the current skill's plugin root through the host's skill-relative resource mechanism. Do not hard-code a Claude cache, Codex cache, marketplace checkout, or Smithy path. The shared bootstrap is: ```text ../../bootstrap/install-beads.s