vaultspec-executelisted

# Execute (vaultspec-execute) Works an approved plan from its next open Step, leaving a checkpoint after every Step so any later session resumes without re-reading the cluster. Precondition: the plan has scoped authorization from the user, recorded per the vaultspec system section. ## Resume - `vaultspec-core status <feature>` (or the `status` tool) names the next open Step. A plan whose Description lacks an `Approved` line needs its authorization established: persist existing authorization or present it and ask when none exists. - On the plan's first entry read it whole; on resume, read the next Step's row and the ADR sections it depends on, if any. Confirm the decisions needed by the next Step are accepted; reassess coverage when reopening historical work. - Ground the Step per the `vaultspec-discovery` rule before editing. - A dispatched worker skips orientation (the orchestrator did it) and works its assigned container from the named Step onward. ## Per Step - Implement exactly the Step's action in the files it names. Run the project's tests, lint, and type checks. - Apply the system's blocker and approval contract. Expected new files, routine path corrections, and implementation choices within approved constraints can proceed; record row corrections through `plan_edit`. Raise missing prerequisites or uncovered choices to the user only when existing authority cannot resolve them. Workers report these to the orchestrator. Record the answer and cont