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

18
docs/status/C6-003.md Normal file
View File

@@ -0,0 +1,18 @@
# C6-003 Status
status: in_progress
task: reactivate_queue
gate: G5
updated: 2026-08-23 America/New_York
The queue reactivation dry-run is complete and deterministic. It records the
legacy queue and parent hashes, three unique capability mappings, retained
negative evidence, expected additive candidates, and rollback path. The dry-run
and write preview bytes match exactly, and the explicit owner review approved
the protected write.
The queue write completed atomically with exit code 0. `M16-GAP-00276` is now
`done`, the completion registry/plan/catalog/index were regenerated, and the
legacy queue points to `M16-GAP-00277` with parent manifest
`tests/golden/M16-GAP-00276/manifest.json`. The before/after bytes and rollback
receipt are recorded in `tests/golden/corrective/C6-003/`.