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

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

View File

@@ -0,0 +1,35 @@
# C6-003 reactivate_queue
状态in_progress
计划:`BLENDER_WASM_CORRECTIVE_TASK_PLAN`
阶段P6
GateG5
依赖:`C6-002`
lifecycleStatus`in_progress`
blockedBy`post_write_verification`
writeScope`queue_reactivation`
queueMutationAllowed`true`owner review 已通过)
## 目标
从已验证 capability manifest 生成 queue-reactivation dry-run、new capability
task cards、manifest/status/context candidates 和 release decision。dry-run 与
write bytes 相同、legacy parent hashes 已在写前验证、primary mapping 唯一且
owner review 已明确通过;原子 queue write 已完成,当前只剩 post-write gates。
## 输入
- `tests/golden/corrective/C5-003/inventory-report.json`
- `tests/golden/corrective/C5-003/capability-manifest.json`
- `tests/golden/corrective/C5-003/legacy-evidence-classification.json`
- `tests/golden/corrective/C6-002/manifest.json`
- `docs/EXECUTION_QUEUE.md`
- `tests/golden/M16-GAP-00275/manifest.json`
## 交付
- `queue-reactivation-dry-run.json` and release decision。
- protected legacy hashes, dry-run/write byte comparison, owner-review evidence,
atomic write receipt, and post-handoff gates。
- 未获得 owner review 或任一 hash/diff 不一致时保持 `in_progress`/`blocked`
不写旧 queue。