complete-everything

# Complete Everything ## Mission (verbatim) > fix and test thoroughly on all the plan - do not defer anything. make sure proper full test is done after enhancement - also fix all out of scope. ## Completion contract Drive the approved outcome through implementation, repair, and verification in one continuous run. Do not stop at phase boundaries or ask whether to continue. Do not claim success from memory, compilation alone, or the original plan's checkboxes. The **closure set** contains: - every unfinished or partially finished plan item; - every `out of scope`, follow-up, optional, nice-to-have, or future-work item parked by the plan or prior completion report that is materially connected to the approved goal; - every defect, missing test, contract mismatch, or regression discovered in the affected blast radius; - every failure introduced by the work or blocking proof of the outcome. This is not permission for unrelated repository-wide cleanup. Do not silently reopen explicit user non-goals, rejected features, or unrelated pre-existing debt. Record those as baseline context, not closure items. If relevance is unclear, decide from the approved user outcome; ask only when the answer would materially change product behavior. Only these may block execution: - missing credentials, access, or a real endpoint/contract; - destructive production-data operations or irreversible external actions; - auth behavior, RLS semantics, secrets, payments, destructive data mutatio...