Setup

Establish a delivery baseline by observing the machine first, proposing the exact delta, and applying one consented configuration path. Repeatable setup preserves operator choices and makes readiness a verified result.

What it adds

Setup inspects installed plugins, marketplaces, relevant tools, and user configuration, then applies the authorized missing pieces through their supported owners. CE capability is resolved when a selected workflow needs it. Ponytail and Superpowers are not prerequisites, and session startup performs no dependency bootstrap.

How it works

Setup keeps local installation, optional fleet enrollment, model policy, auth artifact custody, and privileged lanes distinct. A repeat run reads the current state and proposes only the delta.

> Inspect this machine, install the delivery surface, and show the proposed delta before any optional enrollment.
plugins=railyard:missing roundhouse:present
model_policy=default  signing=ready  auth_presence=checked
fleet_enrollment=not-requested
plan=install-railyard

Scope

Setup handles initial presence and configuration. Doctor handles an installed surface whose observed state needs diagnosis.

Source

Ships in the railyard plugin.

Proof point

step=inventory result=complete
step=install action=railyard result=ready
step=readiness host=ready task=ready transport=ready
result=setup-complete

Troubleshooting

• The marketplace is missing: return to Install and add the shared marketplace before asking Setup to inspect plugin state.
• A plugin is present at the wrong version: compare the marketplace identity and version, then update through the harness that owns the install.
• A required tool or credential is absent: keep the proposed delta visible, install or authenticate through the native owner, and rerun Setup.
• A host is not ready: use Fleet readiness to separate project, agent, auth, and transport evidence before enrolling it.