docs: require cleanup before completion

.config/opencode/AGENTS.md

@@ -40,6 +40,7 @@
 - A "meaningful checkpoint" is a completed implementation chunk from the approved plan, not every file save.
 - Skip commit creation when there are no new changes since the prior checkpoint.
 - Commit messages should reflect the intent of the completed task from the plan.
+- Before creating the final completion commit, clean up temporary artifacts generated during the build (e.g., scratch files, screenshots, logs, transient reports, caches). Intended committed deliverables are not cleanup targets.
 - Standard git safety rules apply: review staged content, respect hooks, no force-push or destructive operations.
 - Push automation is out of scope; the user decides when to push.
 

.config/opencode/agents/builder.md

@@ -40,5 +40,6 @@ You are the execution authority.
 - If you hit a contradiction, hidden dependency, or two failed verification attempts, record the root cause and evidence, then stop and send the work back to `planner`.
 - Builder owns commit creation during `/build`; do not delegate commit authorship decisions to other agents.
 - Create commits automatically at meaningful completed implementation checkpoints, and create a final completion commit when changes remain.
+- Before creating the final completion commit, clean up temporary artifacts generated during the build (e.g., scratch files, screenshots, logs, transient reports, caches). Intended committed deliverables are not cleanup targets.
 - Reuse existing git safety constraints: avoid destructive git behavior, do not force push, and do not add push automation.
 - If there are no new changes at a checkpoint, skip commit creation instead of creating empty or duplicate commits.

.config/opencode/agents/coder.md

@@ -23,4 +23,5 @@ Implement only the assigned lane.
 - Follow the provided spec and stay inside the requested scope.
 - Reuse existing project patterns before introducing new ones.
 - Report notable assumptions, touched files, and any follow-up needed.
+- Clean up temporary artifacts from the assigned lane (e.g., scratch files, screenshots, logs, transient reports, caches) before signaling done. Intended committed deliverables are not cleanup targets.
 - Do not claim work is complete without pointing to verification evidence.

.config/opencode/agents/tester.md

@@ -26,4 +26,5 @@ Own verification and failure evidence.
 - Run the smallest reliable command that proves or disproves the expected behavior.
 - Capture failing commands, key output, and suspected root causes.
 - Retry only when there is a concrete reason to believe the result will change.
+- Flag any temporary artifacts observed during verification (e.g., scratch files, screenshots, logs, transient reports, caches) so builder or coder can clean them up before completion.
 - Do not make code edits.

.config/opencode/commands/build.md

@@ -13,6 +13,7 @@ Execute the latest approved plan for: $ARGUMENTS
 5. Reuse existing git safety rules and avoid destructive git behavior; do not add push automation.
 6. If no new changes exist at a checkpoint, skip commit creation rather than creating empty or duplicate commits.
 7. Follow the plan exactly. If the plan is contradictory, missing a dependency, or fails verification twice, stop, capture evidence, set the execution note to blocked, and send the work back to `planner`.
-8. Finish by creating a final completion commit when changes remain, then update the execution note to `Status: done` or `Status: blocked` and summarize what changed.
+8. Before creating the final completion commit, clean up temporary artifacts generated during the build (e.g., scratch files, screenshots, logs, transient reports, caches). Intended committed deliverables are not cleanup targets.
+9. Finish by creating a final completion commit when changes remain, then update the execution note to `Status: done` or `Status: blocked` and summarize what changed.
 
 Automatic commits are required during `/build` as defined above.

.config/opencode/skills/verification-before-completion/SKILL.md

@@ -14,7 +14,8 @@ Use this skill before declaring work done, handing off, or approving readiness.
 2. Run the smallest reliable checks that prove requirements are met.
 3. Run broader regression checks required by project workflow.
 4. Confirm no known failures are being ignored.
-5. Report residual risk, if any, explicitly.
+5. Clean up temporary artifacts generated during work (e.g., scratch files, screenshots, logs, transient reports, caches). Intended committed deliverables are not cleanup targets.
+6. Report residual risk, if any, explicitly.
 
 ## Evidence Standard