anchored 0.3.0

Added

• /setup skill — a conversational anchored.yml configuration
  assistant. Auto-triggers whenever the user wants to create, change, or
  extend their anchored.yml (add a step, wire an agent/skill into a
  stage, tune a gate, set up commit/PR/TDD automation) — even without
  naming the file. It translates the user's stated requirements into
  correct, schema-valid config, writes name + instructions on every
  custom step, and validates before finishing. It clarifies genuine
  ambiguities with the user and advises on request (backed by
  plugin/references/power-user-setups.md), but never pushes a setup the
  user didn't ask for — no power-user onboarding funnel.
• Custom steps gain instructions (any step) + type (use steps), and
  use: dispatch is now real. A lifecycle step
  (plan/refine/build/wrap.steps) can now declare:
  • instructions: — free-prose documentation of what the step does and
    why, allowed on any step. The recommended base for every custom
    step is name + instructions. On a run: step it self-documents
    the shell (rationale + audit trail); on a use: step it is
    additionally threaded into the invoked worker, the step-level analogue
    of the reserved slots' instructions (build.implement.instructions,
    …).
  • type: agent | skill — on a use: step, picks the invocation
    mechanism. agent (the default when omitted; back-compatible with
    existing use: anchored/implement steps) spawns an isolated
    subagent via the Agent tool; skill invokes the worker via the
    Skill tool in the orchestrator's own session. Rejected on a run:
    step (no worker to type).
  • A single canonical dispatch contract
    (plugin/references/step-dispatch.md) replaces the previously
    unspecified "invoke the named tool … depending on how the user has
    wired it" hand-wave; all four lifecycle skills now point at it.
  • See plugin/EXTENDING.md → "Add a custom step to any stage".

Changed

• Decluttered the shipped default-config.yml — dropped the decorative
  # ─── stage ─── divider headers and the redundant schema line; the
  inline per-slot explanations stay. Cosmetic; no shape change.