Complete all executable mandatory implementation, investigation, and verification before reporting the results.

- At the start, reconcile the original requirements, current plan, explicitly supplied artifacts, and quality gates to identify the obligations to fulfill. A report declaring completion is not sufficient evidence.
- General verification rules conditional on the changed area do not waive checks explicitly required by the original request or accepted plan. Distinguish a real prohibition on execution or incompatible requirements, and identify evidence of that conflict.

{{include:instructions/preserve-acceptance-conditions}}

- Mandatory quality gates may reuse successful evidence when the covered code, tests, configuration, dependencies, and execution environment are unchanged and the command, normal termination, and observations are traceable. Follow any explicit requirement to rerun checks on every execution. Run the affected checks when evidence is missing, identity is uncertain, the check failed or was not run, or changes affect its result.
- Record the original execution reference and target identity for reused results, distinguishing them from newly executed checks. Do not infer success from unavailable results.
- When verification or cause investigation remains failed or unverified, record the attempted method, execution conditions that affect its result, observations, evidence, and confirmed constraints. For a proposed next method, show how it differs from prior attempts and why it can remove or bypass the constraint. Do not treat a changed name, output path, or execution count with no result-affecting change as new work.
- Preserve each attempted method from earlier reports with its execution conditions, result, and shared constraint in the results you pass to planning. Even if its original artifact is unavailable, distinguish reported history from what you verified directly and mark the missing evidence unconfirmed. Explain why a proposed change that leaves the constraint intact cannot create a new effective method. Carry forward every previously recorded explanation of why a difference in conditions cannot affect the result as part of that method's attempt history; do not omit it.
- Before reporting the results, reconcile each obligation with implementation evidence and normally terminated verification. When an unexecuted, running, failed, or unverified obligation has an action executable now, perform that action and confirm its result. Starting a command is not completion.
- Complete executable mandatory work instead of merely listing it under unverified scope in a report.
- When no mandatory action can be executed now and a plan change, external action, or user answer is needed, or there is evidence that the conditions are incompatible, report the invalid premise, observed evidence, and unmet obligations. Do not waive a requirement or conclude from the implementation side that work cannot continue or should stop; record the facts for the planning step to decide. Request an answer only when an input candidate is available and its answer would unblock the work.
- When only verification that cannot be demonstrated because of an environmental constraint remains, separately report the evidence for the current implementation and available project-scoped verification, whether any real defect, untouched mandatory work, or executable new work remains, and the unverified check and external verification obligation. Do not call it successful or finally complete from implementation.