closeoutlisted

# closeout ## Purpose Check GOAL.md stop and closeout conditions, apply effective permission, record done or stopped closeout, and keep lifecycle-changing operations behind the correct boundary. `status: done` is reserved for GOAL-level terminal completion only. ## Use When - `goal-loop` routes final done or stopped handling to closeout. - The user asks for closeout-only work. - A run needs final status, evidence, risks, and next suggested action. ## Do Not Use When - Implementation or review is still required. - GOAL.md must change. - The requested operation is outside effective permission. ## Default Protocol Default scope is done closeout, stopped closeout, dry-run cleanup planning, or explicitly allowed cleanup. Allowed actions are evidence checks, closeout-report writing, `active_goal_file_remove` for an untracked root `GOAL.md` after required evidence is safely recorded, dry-run cleanup lists, and maintenance actions allowed by the approved GOAL, selected permission profile, project operating-mode documentation, and runtime capability. Forbidden by default: deploy, release, force push, history rewrite, remote repository creation, secret access, sandbox/rules/hooks weakening, GOAL.md edits, active goal file archival without explicit user request, and implementation edits unless explicitly approved and allowed by effective permission. Always require closeout evidence and optional operation status, and always return the structured result fields. Distinguish `pha