Add EveElectron split boundary

This commit is contained in:
Meta Vens 2026-07-09 02:36:09 +01:00
commit edf1af7ece
6 changed files with 153 additions and 8 deletions

View file

@ -290,6 +290,13 @@ Recently cut:
`packs/runtime.json`, the runtime-owner smoke asserts them, and the generic
conformance smoke now reports the advertised but unclaimed `unity-scene`
lowering target as an explicit capability gap.
- EveElectron now has a pending split target and handoff at
`runtimes/incubating/eve-electron/eveelectron-split-handoff.json`. It does
not claim an Electron runtime body yet. The handoff draws the line between a
future provider-agnostic Electron shell and Aetheria's Starbridge RTS product
client, and the split-target consumer smoke keeps the missing shell,
provider-advertisement consumption, command transport, and capture proofs
visible as blockers.
- Aetheria interactive world surfaces now carry a structured provider-owned
`worldInteraction` contract. The provider advertisement names projection
kind, provider state schemas, daemon command boundary, receipt schema,

View file

@ -199,11 +199,14 @@ Split-target consumer smoke:
powershell -ExecutionPolicy Bypass -File .\scripts\run-split-target-conformance-consumer-smoke.ps1
```
That script asserts that EveFlutter and EveUnity are exported as incubating
split targets, that their current split-readiness proofs are passed, and that
their graduation blockers remain visible to consumers. A target being present
is not enough; future owner repos must be able to consume why it is or is not
ready to leave Eve incubation.
That script asserts that EveFlutter, EveUnity, and EveElectron are exported as
incubating split targets, that their current split-readiness proofs are passed,
and that their graduation blockers remain visible to consumers. A target being
present is not enough; future owner repos must be able to consume why it is or
is not ready to leave Eve incubation. EveElectron is intentionally pending: its
handoff names the generic Electron shell boundary, while the Starbridge RTS
client remains Aetheria-owned product code until a provider-agnostic shell
exists.
The Flutter widget smoke also exercises `EveProviderCatalog` and
`EveProviderPicker` against a conformance-export-shaped provider list. That is