# Blender Web Continuation Contract

Copy this contract only when creating a new Blender/WBV2 queue. Existing
repositories must keep `docs/EXECUTION_QUEUE.md` and the hash-bound manifests as
the authoritative state.

## Required Properties

- One authoritative current task and one parent manifest.
- One task card with source paths, native command, Chromium evidence and
  explicit negative/recovery cases.
- A manifest with source/protocol/artifact SHA-256 values and `nextTask`.
- A bounded task-context packet generated by
  `node tools/web/check-task-context.mjs --write`.
- A precise `blocked` checkpoint for failures or unknown state.

## Terminal Rule

Do not declare the Blender project complete until the task index has no active
task, all required gates pass, and the final manifest has `status: done` and
`nextTask: null`. A generated report or an idle process alone is not completion.