perf(web): add idempotent batch verification fast paths
Some checks failed
M6 deployable RC / quick (push) Has been cancelled
M6 deployable RC / chromium (push) Has been cancelled
M6 deployable RC / release (push) Has been cancelled

This commit is contained in:
mes123456
2026-09-03 20:29:51 +08:00
parent b849eb657b
commit b28b365f3a
19 changed files with 652 additions and 71 deletions

View File

@@ -13,6 +13,8 @@ commit and push.
a missing scheduler and stops on a terminal or blocked checkpoint.
- `show_blender_web_scheduler.py`: delegates live RUNNING/IDLE/BLOCKED state to
`tools/web/print-wbv2-live-status.mjs`.
- `validate_incremental_context.py`: validates only the active batch metadata;
unchanged inputs return `incremental-context-ok ... context=REUSED`.
- `start_unattended.sh`: launches the scheduler and watchdog with `nohup` and
`setsid` for process-level continuity.
- `check_continuation_state.py` and `validate_web_context.py`: read-only WBV2
@@ -60,6 +62,12 @@ For machine-readable live state:
python3 my-tools/show_blender_web_scheduler.py --json
```
Implementation cycles use a bounded fast path: each module manifest carries a
stable `batchId` and selected record IDs, context metadata compares
`bytes`/`mtime_ns` before hashing, and the outer scheduler owns planner and
continuation rotation. Full API, format, Chromium, performance and release
gates remain an explicit final-audit operation.
`--commit --push` is enabled by the launcher and can be disabled for a local
dry run with `WBV2_AUTO_COMMIT=0 WBV2_AUTO_PUSH=0`.