wangdequan/workinf_Blender_Wasm
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
0d61c641503f904c1b7a141a38e6a114849364dd
workinf_Blender_Wasm/my-tools/BLENDER_WEB_CONTEXT_PROTOCOL_REFERENCE.md
mes123456 0d61c64150 feat(web): authorize corrective smooth reader
2026-09-02 18:35:58 +08:00

1.2 KiB
Raw Blame History

Blender Web Context Protocol

The authoritative context builder is tools/web/task-context-lib.mjs. my-tools/prepare_web_task_context.py is a small compatibility launcher.

Required Inputs

  • docs/EXECUTION_QUEUE.md supplies the current task and parent manifest.
  • docs/tasks/WBV2-*.md supplies the focused task contract.
  • tests/golden/<task>/manifest.json and its parent provide hash-bound evidence.
  • tests/golden/<task>/task-context.json is the generated bounded packet.

Every task starts with:

node tools/web/print-task-context.mjs
node tools/web/check-task-context.mjs

Only files listed by the current packet may be loaded as direct context. Source trees, raw logs and broad inventories stay on disk and are inspected by the task's focused commands. A budget or hash failure stops execution.

Handoff

After a task has produced its receipt and manifest:

node tools/web/check-task-context.mjs --task <task-id> --write
node tools/web/check-context-governance.mjs
node tools/web/check-v2-handoff.mjs --task <task-id>

The queue is never advanced by this context helper. Only the production WBV2 runner may authorize and persist a successor after all required evidence, Chromium gates, commit and remote verification succeed.

Reference in New Issue View Git Blame Copy Permalink