Add deduplicated WBV2 inventory coverage workflow
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-08-28 10:12:29 +08:00
parent ea18416ff2
commit dc55bacce6
39 changed files with 72823 additions and 78 deletions

View File

@@ -9,3 +9,6 @@
- nextTask: `NONE`
The high-value gate reuses the batch ledger and hash-bound receipts. Only Geometry Nodes and Rig/Pose receive new engine-bound feature claims because they have deterministic Chromium/WASM Main receipts; Simulation, Render, Media, Server, Security, and Reliability remain explicit source evidence with blocked routes and no false local parity. The 6900-entry remainder and provenance limitation remain visible.
- authorized continuation: `WBV2-P14-000`
Inventory coverage may continue under a new root without changing the high-value claim boundary.

View File

@@ -0,0 +1,8 @@
# WBV2-P14-000 status
- task: `WBV2-P14-000`; parent: `WBV2-P13-005`; status: `done`
- inventory scope: `6900` total, `6618` pending
- capability buckets: `15`; duplicate validation: `forbidden`
- nextTask: `WBV2-P14-001`
P14 is an authorized coverage continuation. It preserves the P13 high-value declaration and starts with a capability-family ledger so one representative receipt can be reused without claiming the entire family is complete.

View File

@@ -0,0 +1,11 @@
# WBV2-P14-001 status
- task: `WBV2-P14-001`; parent: `WBV2-P14-000`; status: `done`
- inventory streamed: `6900` entries across `15` capability buckets
- state: `281 completed`, `1 active`, `6618 pending`
- representative-evidence buckets: `7`; unproven buckets: `8`
- repeated Blender/Chromium validation: `0`; duplicate validation avoided: `true`
- entry digest: `06debe05e086868dcad99980a04161f71172df23a27e36e14670da94af3db516`
- nextTask: `WBV2-P14-002`
The full inventory is streamed once and grouped by capability family. Existing P13 receipts are attached only as representative slices; no bucket is promoted to complete parity unless every entry has independent evidence. The 6618-entry remainder remains explicit.

View File

@@ -0,0 +1,10 @@
# WBV2-P14-002 status
- task: `WBV2-P14-002`; parent: `WBV2-P14-001`; status: `done`
- capability buckets reconciled: `15`; inventory: `6900` total, `6618` pending
- representative-evidence buckets: `7`; unproven pending buckets: `7`; active unproven: `1`
- engine-bound claims referenced: `8`; full-family parity claims: `0`
- repeated Blender/Chromium validation: `0`; duplicate validation avoided: `true`
- nextTask: `WBV2-P14-003`
This matrix binds the P14 coverage ledger to the eight P13 feature claims. Representative receipts remain partial slices; a capability family is not complete until each entry has its own evidence.

View File

@@ -0,0 +1,10 @@
# WBV2-P14-003 status
- task: `WBV2-P14-003`; parent: `WBV2-P14-002`; status: `done`
- inventory accounted: `6900/6900`; pending remains `6618`; active: `1`
- capability batches: `15`; representative-evidence buckets: `7`; full-family parity claims: `0`
- engine-bound feature claims retained: `8`; provenance epoch: `2`
- minimum new runs under batch policy: `14`; repeated Blender/Chromium runs: `0`
- nextTask: `NONE`
The coverage gate closes the 6900-entry accounting problem without pretending that inventory metadata is feature parity. Each family has one deduplicated batch key; completed entries are regression-only, representative receipts are partial, and pending entries require unique-behavior fanout. Historical reproduction remains false and the release label stays AUTHORIZED_REBASELINE_ONLY.