workinf_Blender_Wasm/my-tools/BLENDER_NEXTTASK_REFERENCE.md

Blender Web Next Task Reference

nextTask.md documents the continuation contract, but the authoritative execution pointer is docs/EXECUTION_QUEUE.md and the authoritative handoff is the parent/child manifest chain under tests/golden/.

Resume

node tools/web/print-task-context.mjs
node tools/web/check-task-context.mjs
node tools/web/check-context-governance.mjs
node tools/web/check-execution-control-plane.mjs

Only the current task card, its parent manifest/status and the packet-listed inputs may be loaded. Do not infer a successor from numeric task IDs or old history. A task is complete only when its source-backed positive and negative cases, recovery/save-reopen evidence, Chromium receipt, hashes and handoff checks all pass.

Continuous Mode

node tools/web/run-wbv2-scheduler.mjs --max-iterations 0 --commit --push

For a detached process:

setsid -f nohup node tools/web/run-wbv2-scheduler.mjs --max-iterations 0 --commit --push \
  > tests/golden/WBV2/continuous-scheduler.stdout.log 2>&1 < /dev/null

my-tools/start_unattended.sh starts the same scheduler plus a watchdog. The watchdog never retries blocked or unknown checkpoints and never changes task state. Inspect live state with:

node tools/web/print-wbv2-live-status.mjs
python3 my-tools/show_blender_web_scheduler.py --json

Boundaries

• Blender source and compiled WebEngine/WASM are the only behavior authority.
• Chromium is the only browser evidence environment.
• Historical inventory remains read-only; only hash-bound dynamic evidence changes verified coverage.
• Commit/push completion requires remote main HEAD to equal local HEAD.
• A real build, test, credential or architecture block is preserved as a precise checkpoint instead of being bypassed.