harness-finish

To finalize git workflow tasks, you must run verification checks to gate completion, archive project plans, update docs/PLANS.md, and select from four explicit finish options including local merge or push branch.

Archiving completed plans involves moving them to an archive directory and refreshing docs/PLANS.md with the current status and archived file path, ensuring documented evidence for software project handoffs.

Yes, you can discard work safely because the system enforces explicit discard confirmation for destructive actions and performs contextual branch checks to avoid disrupting unrelated changes.

After completing a software project handoff, four finish options are available: local merge, push branch and PR, keep the branch or worktree, or discard the work with enforced safeguards and prompts.

Yes, a pre-condition harness-verify is required before presenting finish options, enforcing evidence-based completion claims to ensure all implementation work is fully validated.

The finish workflow requires explicit discard confirmation to prevent accidental data loss during cleanup, ensuring destructive actions only proceed after user validation and contextual safety checks pass.