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

22
docs/status/C3-003.md Normal file
View File

@@ -0,0 +1,22 @@
# C3-003 Status
status: done
task: asset_catalog_pilot_e2e
gate: G3
updated: 2026-08-23 America/New_York
C3-003 runs the same Asset Catalog fixture and command in Chromium through the
Vite production pilot bridge. The five-case matrix covers positive append,
duplicate entry, missing provider, stale revision, and malformed payload. The
positive desktop/WASM receipts match, Main advances once and becomes dirty;
all negative cases preserve Main. The history store then saves and reopens the
catalog snapshot with revision 5 and dirty=false.
The Chromium-only pilot passed twice on separate ports and its receipts are
byte-identical. C3-002 regression, typecheck, context/corrective governance,
task-context, protected legacy hashes, and `git diff --check` all exited 0.
The existing App React refresh preamble warning remains in the dev server log,
but the pilot page and all assertions completed successfully.
Evidence and manifest: `tests/golden/corrective/C3-003/`.
Next corrective task: `C4-001`.