Checkpoint web parity through Chromium input tasks
This commit is contained in:
47
docs/status/M13-01A.md
Normal file
47
docs/status/M13-01A.md
Normal file
@@ -0,0 +1,47 @@
|
||||
# M13-01A Status
|
||||
|
||||
status: done
|
||||
task: inventory Text, Python Console, autorun, driver expression, handler, and add-on entry points
|
||||
updated: 2026-08-18 America/New_York
|
||||
enablingTask: true
|
||||
parityStateChange: false
|
||||
|
||||
## Scope
|
||||
|
||||
Pinned Blender 5.2 now has a machine-readable scripting entry inventory covering three Text
|
||||
datablocks, Python Console operators, a module-autorun request, one driver expression, 39 handler
|
||||
groups, and four add-on operators. The report records the entry source and default Web policy:
|
||||
Text is metadata-only, while Console, autorun, driver expressions, handlers, and add-on operations
|
||||
are `DENY`. This task only inventories entry points; it does not execute script text or open a
|
||||
browser scripting route.
|
||||
|
||||
## Evidence
|
||||
|
||||
- `build_blender_5.2.0/bin/blender -b --factory-startup --python
|
||||
tools/web/generate-script-entry-inventory.py -- tests/files/web/m13_script_entry_v1
|
||||
tests/golden/M13-01A/entry-inventory.json` created a fixture with internal/external Text,
|
||||
`use_module` autorun metadata, and a driver expression without executing user code.
|
||||
- `node tools/web/check-script-entry-inventory.mjs` matched pinned runtime identity, policy and
|
||||
semantic inventory, then regenerated the report in a fresh directory. Blender's `.blend` save
|
||||
contains runtime save bytes that may differ between runs, so determinism is asserted on the
|
||||
inventory and fixture byte length; the checked-in fixture hash remains bound in the manifest.
|
||||
Output: `script-entry-inventory-ok texts=3 console=3 autorun=1 drivers=1 handlers=39 addonOps=4 deterministic=true next=M13-01B`.
|
||||
- `python3 -m py_compile tools/web/generate-script-entry-inventory.py`, Node syntax check and
|
||||
`git diff --check` passed.
|
||||
|
||||
## Artifact Hashes
|
||||
|
||||
- generator: `b72667493cfe9957161ef3fb9814180e0cfad5f8aaa1c60c9b6f132e915f3d6f`
|
||||
- checker: `68478f15de4d63ed175e6b580761fd478b1fe9bccbfcaeee82218d13063dfa51`
|
||||
- report: `e024995c53f01beaf725f281f74a6e5ec6018a53435da61a66f5e58a9e50973c`
|
||||
- fixture: `bd6375d02908bfcc57ff7cdeec3f9827bfc4336d1e46e165c5fbbf4d04f19645`
|
||||
- manifest: `d4a305033343ef5fb1ffc073617b59d9012f64b80ecb233e743fb0789a8b4893`
|
||||
|
||||
## Next Task
|
||||
|
||||
`M13-01B`: read script metadata on `.blend` open without executing arbitrary content.
|
||||
|
||||
## Rollback
|
||||
|
||||
Remove the generator, checker, fixture, report, manifest, and this status entry. Restore M12-07J
|
||||
as the queue tail and move the machine queue back to M13-01A. No parity ledger rollback is required.
|
||||
Reference in New Issue
Block a user