Document continuous execution prompt

nextTask.md

@@ -11,42 +11,62 @@ message. The loop stops only at an explicit stop condition described below.
 
 ## Copyable Resume Prompt
 
-Use the following prompt when continuous execution is needed. It deliberately
-keeps every task iteration bounded while allowing successful handoffs to proceed
-automatically:
+Use the following prompt when continuous execution is needed. It is the
+copyable, end-to-end command for bounded implementation, verification, handoff,
+and (when authorized) repository push:
 
 ```text
 按 nextTask.md 接续执行。
 
 Treat this as an execution command, not a request for a plan or status report.
-Enter CONTINUOUS mode and repeat the following bounded iteration until a stop
-condition is reached:
+Enter CONTINUOUS mode and repeat one bounded task iteration at a time until a
+stop condition is reached:
 
-1. Read docs/EXECUTION_QUEUE.md, run print-task-context, then run
-   check-task-context before editing.
+1. Read `docs/EXECUTION_QUEUE.md`; run `node tools/web/print-task-context.mjs`
+   and `node tools/web/check-task-context.mjs` before editing.
 2. Read only the current task card, parent manifest/status, and the focused
-   files named by the task context. Do not open the full next-task-plan.json,
-   all status logs, or historical project plans.
-3. Complete exactly the current task: implement the scoped behavior, run the
-   focused desktop/npm/direct checks, verify save/reopen and the negative case,
-   write reports/status/manifest/task-context with SHA-256 values, then run
-   governance checks and git diff --check.
-4. Advance the queue only after every exit criterion and hash check passes,
-   using repository generators for the task index/catalog/card.
-5. After a successful handoff, discard the previous task transcript and begin
-   the next iteration from a fresh print-task-context package. Do not wait for
-   another user message and do not carry prior task files into the next
-   iteration except through the new parent manifest and status summary.
+   files named by the task context. Never open the full
+   `next-task-plan.json`, all `docs/status` logs, or historical plans.
+3. Complete exactly the current task: implement the scoped behavior, generate
+   the fixture, run the focused desktop Blender check, npm comparator, and
+   direct comparator, then verify save/reopen and the malformed/negative case.
+   Chromium is the only permitted browser runtime.
+4. Keep long output in `tests/golden/<task>/command.log`; report only exit
+   codes, short tails, artifact paths, and SHA-256 values.
+5. After every exit criterion passes, run
+   `node tools/web/check-task-context.mjs --task <task-id> --write`, write the
+   report/status/manifest/task-context handoff, and verify all artifact hashes.
+6. Run every post-handoff gate:
 
-Keep tool output and context bounded. On any failure or hash drift, keep the
-current task `in_progress`/`blocked`, do not advance `nextTask`, and stop the
-loop. End only when a stop condition is reached, with a compact summary of all
-tasks completed in this run (task, state, nextTask, command exit codes, and
-artifact paths/hashes).
-For stream-disconnect or remote-compact errors, stop the active request and
-use the recovery procedure below in a new request. Do not paste the failed
-transcript, invoke another compact operation, or blindly repeat a state-
-changing command.
+   ```bash
+   node tools/web/check-blender-next-task-plan.mjs
+   node tools/web/check-task-index.mjs
+   npm --prefix web run test:task-context
+   npm --prefix web run test:context-governance
+   node tools/web/check-context-governance.mjs
+   git diff --check
+   ```
+
+7. Only after all gates pass, use repository generators for the task
+   index/catalog/card and advance `docs/EXECUTION_QUEUE.md` to the newly
+   completed manifest's `nextTask`. Do not manually edit task-index offsets,
+   catalog lines, parent evidence, or a guessed task number.
+8. If repository saving has been authorized, commit the successful handoff and
+   push the current branch to its existing `origin`; use the credential helper
+   or an interactive prompt, never write credentials into files, URLs, logs, or
+   prompts. Verify `HEAD` and `origin/<branch>` match after the push.
+9. After a successful handoff, discard the previous task transcript and begin
+   the next iteration from a fresh `print-task-context` package. Do not wait for
+   another user message and carry forward only the new parent manifest/status.
+
+On any failed command, missing focused entry, unavailable environment, budget
+overflow, hash drift, governance failure, cancellation, or inconsistent queue,
+keep the task `in_progress`/`blocked`, do not advance `nextTask`, and stop with
+the exact blocker and evidence paths. Do not fake completion or retry an
+unknown state-changing command. For stream-disconnect, error-decoding, or
+remote-compact failures, use the recovery procedure below in a new request.
+End with a compact summary of completed tasks, states, nextTask, command exit
+codes, artifact hashes, push status, and any remaining blocker.
 ```
 
 ## Resume Command