GameCult/Thing
Watch
9
0
Fork
You've already forked Thing
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Extend plugin ABI fixture coverage

Browse source
This commit is contained in:
Meta Vens 2026-07-09 01:03:57 +01:00
commit 3385cff2ef
7 changed files with 117 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/eve-migration-roadmap.md
View file

@ -280,6 +280,11 @@ Exit criteria:
Recently cut:
- Sai, Norn, and TeX plugin ABI fixtures now cover `lower` and `measure` in
addition to `describe`, `validate`, `project`, and `apply`. Eve validates the
operation shape, preserved component kinds, measurement outputs, and provider
authority flag without importing plugin internals or deciding plugin
semantics.
- The web reference now publishes a runtime capability manifest at
`web/eve-runtime-capability.json`, and the parity harness validates it through
the same runtime capability path as Unity. Web remains Eve's behavior oracle,
@ -354,9 +359,9 @@ Recently cut:
command boundary consumption, command intents, and provider-owned receipt
states without importing Aetheria internals into Eve.
- Sai, Norn, and TeX now have plugin ABI fixtures for describe, validate,
project, and apply behavior. The parity harness validates those fixtures
against plugin manifests, so Eve proves the ABI shape without owning plugin
semantics.
project, lower, measure, and apply behavior. The parity harness validates
those fixtures against plugin manifests, so Eve proves the ABI shape without
owning plugin semantics.
- Split-readiness reporting now exists for `EveFlutter` and `EveUnity`. The
parity report lists member runtime health, required plugin capability claims,
pending proofs, and blockers before either repo can graduate out of Eve

4
docs/plugin-architecture.md
View file

@ -573,8 +573,8 @@ For Sai VN:
- embedded surface slot fixture with optional Norn/TeX plugin dependencies;
- degraded renderer fixture for clients without scene placement;
- receipt round-trip fixture driven by a fake provider.
- ABI fixture proving `validate`, `apply`, and `project` produce the expected
plugin results without direct imports.
- ABI fixture proving `describe`, `validate`, `project`, `lower`, `measure`,
and `apply` publish the expected contract shape without direct imports.
The parity manifest should be extended so runtimes declare plugin support: