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

21
docs/status/C2-002.md Normal file
View File

@@ -0,0 +1,21 @@
# C2-002 Status
status: done
task: atomic_main_mutation
gate: G2
updated: 2026-08-23 America/New_York
C2-002 adds an in-memory atomic Main transaction boundary. Commands mutate a
cloned draft and publish exactly one revision/dirty update only after the
outcome passes validation. Adapter exceptions, cancellation, malformed
outcomes, and stale revisions restore the original value, revision, and dirty
state before the shared runner normalizes the failure result.
The focused transaction test passed 5/5 assertions. Desktop and WASM positive
receipts matched with revision 4 -> 5; cancellation, malformed outcome, and
revision conflict all preserved revision 4 and the clean snapshot. Receipt
determinism, protected legacy hashes, typecheck, context/corrective governance,
task-context, and `git diff --check` all exited 0.
Evidence and manifest: `tests/golden/corrective/C2-002/`.
Next corrective task: `C2-003`.