wangdequan/workinf_Blender_Wasm
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Reorganize Blender Web execution around capabilities
Some checks are pending
M6 deployable RC / quick (push) Waiting to run
Details
M6 deployable RC / chromium (push) Blocked by required conditions
Details
M6 deployable RC / release (push) Blocked by required conditions
Details

Browse Source
This commit is contained in:
mes123456
2026-08-24 18:37:46 -04:00
parent 0b2c3ba0dd
commit a081c68c87
2530 changed files with 763976 additions and 79 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
nextTask.md
View File

@@ -27,9 +27,10 @@ stop condition is reached:
2. Read only the current task card, parent manifest/status, and the focused
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.
3. Complete exactly the current task using the commands in its task card. Legacy
`M*-GAP-*` tasks are coverage-only; capability `WBV2-*` tasks own production
behavior and may use shared desktop/WASM/Chromium runners. Do not run a
desktop fixture or comparator unless the current card requires it.
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.
@@ -39,6 +40,7 @@ stop condition is reached:
6. Run every post-handoff gate:
```bash
node tools/web/check-execution-control-plane.mjs
node tools/web/check-blender-next-task-plan.mjs
node tools/web/check-task-index.mjs
npm --prefix web run test:task-context
@@ -238,12 +240,12 @@ Recorded: 2026-08-22 America/New_York
| Field | Value |
| --- | --- |
| Current task when this file was written | `M16-GAP-00227` |
| Current task when this file was written | `WBV2-P0-002` |
| Current task state | `in_progress` |
| Parent manifest | `tests/golden/M16-GAP-00226/manifest.json` |
| Current task card | `docs/tasks/M16-GAP-00227.md` |
| Current task-context nextTask | `M16-GAP-00228` |
| Focused command | `npm --prefix web run test:generated-gap -- --task M16-GAP-00227` |
| Parent manifest | `tests/golden/WBV2-P0-001/manifest.json` |
| Current task card | `docs/tasks/WBV2-P0-002.md` |
| Current task-context nextTask | `WBV2-P0-003` |
| Focused command | `node tools/web/check-execution-control-plane.mjs` |
The snapshot is informational and may become stale. On every resume, the queue,
parent manifest, and fresh `print-task-context` output win. Never infer a task