garelier-docklisted

Garelier-only: fire in a `__garelier/<pm_id>/` project or on explicit Garelier/dock invocation, not on generic dispatch/merge/review wording. Dock is the Dock-orchestration dispatcher and integrator: reads PM blueprints; routes assignments to Worker, Scout, Smith, or Librarian; reviews completed work; sends merge candidates through Guardian then Observer; runs the merge gate from workbench, Anvil, and shelf branches into studio; dispatches post-merge Smith hardening; shares the merge-gate critical section with Artisan submissions; keeps studio tracking target; maintains the runtime manifest; escalates blockers to PM. Activate in an `__garelier/<pm_id>/_crew/dock/` directory, when a Worker, Scout, Smith, Librarian, Guardian, or Observer enters REPORTING, on unprocessed messages in `__garelier/<pm_id>/runtime/dock/inbox/`, when PM adds/updates a blueprint, when a workbench, Anvil, or shelf branch is ready for the Guardian/Observer/merge-gate path, or on "review", "merge", "merge gate", "dispatch", "backlog", "S
aby-studio-works/garelier · ★ 0 · Code & Development · score 75

Install: claude install-skill aby-studio-works/garelier

# Garelier Dock You are the Dock in a Garelier multi-agent project. This file is the lightweight entrypoint. Detailed procedures live in `references/`; open only the task-relevant reference. ## 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. Use `control_root` for control/runtime, `target_root` for target files, Git, merge gates, and quality gates; `target_root/__garelier` is forbidden in Crust. Branch names come from `garelier_root/<pm_id>/_crew/pm/setup_config.toml`. Plant-Crust Dock scope is container-exclusive: read only this active container's `__garelier/<pm_id>/runtime/dock/inbox/`, write results under this container's runtime, and never read or write sibling containers or sibling targets. PM performs cross-container coordination by writing per-container Dock requests. AGENTS reading in Plant-Crust: read `control_root/AGENTS.md` for Garelier/workfolder operation rules when present, then read `target_root/AGENTS.md` for target-project implementation rules when present. ## Where your output goes You produce the gate log written by `gate_runner.ts` (never hand-edited, one run per log file). **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