feat(web): classify and route complete Blender inventory
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-06 21:10:31 +08:00
parent 66d3f4e0f4
commit e2e81c7c00
41 changed files with 116672 additions and 37 deletions

View File

@@ -59,3 +59,26 @@ features when a browser-native equivalent exists.
Verification remains incremental and deferred to user operation. No completion
claim is made from inventory counts alone.
## Source-unit route dashboard
`featureRouteCoverage` publishes the complete route assignment for the current
3,745-unit source inventory. `featureRouteGaps` publishes route-assignment gaps,
unavailable units, and the separate behavioral-evidence gap. The scheduler JSON
summary exposes both command names under `progress`; its text view prints the
same category counts.
| execution route | source units | production boundary |
| --- | ---: | --- |
| `WEB_MAIN` | 1,698 | typed native Main/WASM or shared reflection route |
| `SERVER_NATIVE` | 1,613 | bounded Blender background operator job |
| `BROWSER_EQUIVALENT` | 434 | browser-native replacement for desktop UI/context |
| `UNAVAILABLE` | 0 | no Web platform equivalent |
| **total** | **3,745** | all source units have an explicit route classification |
Route assignment is complete. Existing exact evidence remains `1,025` verified
units, while `2,720` units retain explicit `UNVERIFIED` behavioral evidence
until real user operation exercises the declared route. The dashboard does not
convert classification into a completion claim. `WEB_MAIN` behavior must
continue through existing typed Blender
Main/WASM commands, and `SERVER_NATIVE` behavior through bounded Blender jobs.