Files
workinf_Blender_Wasm/docs/status/M12-03M.md
mes123456 380cbed4ff
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
Checkpoint web parity through Chromium input tasks
2026-08-19 10:39:03 -04:00

39 lines
1.6 KiB
Markdown

# M12-03M Status
status: done
task: dependency cycle, ID collision, cross-library cycle, and duplicate reload negatives
updated: 2026-08-17 America/New_York
enablingTask: false
parityStateChange: false
## Scope
Schema-1 negative-case validation checks library dependency graphs, cross-library references,
data-block identity ownership, and reload generation identities. Acyclic graphs with unique IDs are
accepted; dependency/cross-library cycles, missing source libraries, duplicate data-block IDs, and
duplicate reload generations fail with stable codes before any writer or Main mutation.
## Evidence
- `npm --prefix web run test:library-negative-cases` passed 4/4 unit tests.
- Direct dependency cycles and cross-library cycles return `LIBRARY_DEPENDENCY_CYCLE`.
- Data-block collision returns `TASK_VALIDATION_FAILED`; duplicate reload returns `REVISION_CONFLICT`;
a missing source library returns `ASSET_SOURCE_HASH_MISMATCH`.
## Artifact Hashes
- protocol: `efc7cc810089eab6178fc5c2f2a45d641625a032ecfa5b2b4ef37694d0decc97`
- unit: `b7ae41b2c35b2fe1598bca4425dd434230bfe4bf342320c88214a060dcbb0a16`
- manifest: `693cbedfe8e29167283a753d119de5a9cfe5e20bc96aff7ba84d720ffde9148a`
- package commands: `cfb232baa494ff59f6c8d65514a08c86332ee9354350b2a0392b6f932a7ee42c`
## Next Task
`M12-03N`: append/link/override each receive independent desktop/WASM/Chromium commands.
## Rollback
Remove the negative-case protocol, unit suite, manifest, package command, and this status entry.
Restore M12-03L to pending and move the machine queue back to `M12-03M`. No parity ledger rollback
is required.