Add EveFlutter provider picker proof

This commit is contained in:
Meta Vens 2026-07-09 01:24:21 +01:00
commit e2e9b21e2f
6 changed files with 235 additions and 4 deletions

View file

@ -280,6 +280,13 @@ Exit criteria:
Recently cut:
- EveFlutter now has a provider-catalog picker primitive. `EveProviderCatalog`
parses conformance-export provider entries, including Sai/Norn/TeX plugin
requirements, and `EveProviderPicker` selects those provider ids without
reading web fixture paths. The Flutter smoke test proves provider selection
from an export-shaped provider list, so the split-readiness report records the
provider-picker proof as passed while leaving release/capture lifecycle
ownership as the remaining EveFlutter blocker.
- EveFlutter now has a conformance consumer smoke at
`scripts/run-eveflutter-conformance-consumer-smoke.ps1`. It runs from
`flutter/eve_parity`, consumes the exported conformance pack, and asserts the

View file

@ -120,6 +120,11 @@ That script runs the export consumer from `flutter/eve_parity` and asserts the
runtime pack, Sai provider fixture, Flutter runtime targets, and `EveFlutter`
split target without reading `tools/parity/parity-manifest.json`.
The Flutter widget smoke also exercises `EveProviderCatalog` and
`EveProviderPicker` against a conformance-export-shaped provider list. That is
the runtime-side provider picker proof; it consumes provider entries and plugin
requirements without reading web fixture paths.
Aetheria Unity package consumer smoke:
```powershell

View file

@ -155,6 +155,9 @@ First cuts:
- Scaffold a generic Eve Flutter app with the same provider picker as web.
- Load the same local provider advertisements and local fixture surfaces during
development.
- Consume conformance-export provider entries through `EveProviderCatalog` and
select them through `EveProviderPicker`; this is the split-ready provider
picker input shape, distinct from web-local fallback fixture discovery.
- Lower `surface.root` recursively into Flutter widgets/custom painters.
- Lower CultUI partitions, `fieldRow`, labels, cards, buttons, metrics, and
slider anatomy from `control.box`, `control.part`, and `control.hitArea`.