slipway-worktree-preflightlisted

# Worktree Preflight ``` IRON LAW: NO DISCOVERY-REQUIRED GOVERNED EXECUTION WITHOUT A DEDICATED WORKTREE AND A VERIFIED BASELINE ``` ## Purpose Verify or repair the dedicated worktree binding required before governed execution begins. `slipway new` creates the default `.worktrees/<slug>` binding early when Git has a usable HEAD; this standalone governance preflight handles the remaining cases where binding is missing, invalid, or operator-supplied. Mitigates: worktree isolation and baseline drift before governed execution. ## Workflow Outline 1. Verify the dedicated worktree and intended branch, creating it only if the runtime did not already bind the default worktree. 2. Run a fresh, bounded baseline verification command in that worktree. 3. Write verification references, return to the source workspace, and advance. ## When This Runs For discovery-required governed changes, the normal path is early automatic binding during `slipway new`. If `slipway next --json` later returns `next_skill: worktree-preflight`, treat that as a repair/preflight path for a missing or invalid binding before wave execution. ## Process ### 1. Establish a Dedicated Worktree Verify the dedicated git worktree for this change. If the runtime did not create one, create it using the repo-local default unless project policy or the operator explicitly chooses another path. Requirements: - the worktree path MUST differ from the current repository root - the worktree MUST be registered in `git work