Validate provider plugin requirements

This commit is contained in:
Meta Vens 2026-07-09 01:10:32 +01:00
commit 5839ae2acb
7 changed files with 222 additions and 5 deletions

View file

@ -280,6 +280,13 @@ Exit criteria:
Recently cut:
- Provider advertisements can now name sidecar plugin requirements per surface
with `surfaces[].requiresPlugins[]`. The parity harness validates those
requirements against known plugin manifests, exports them in the conformance
provider list, and reports missing plugins or capabilities as provider
capability gaps. The Sai VN fixture now has an advertisement-shaped provider
entry for `gamecult.home.vn`, so Sai/Norn/TeX requirements sit at the
provider/plugin boundary instead of hiding only in fixture metadata.
- The conformance runtime pack now exports `runtimeTargets` in
`artifacts/conformance/latest/packs/runtime.json`. Runtime repos can consume
runtime status, feature/plugin claims, command schema, lifecycle, capture

View file

@ -307,6 +307,12 @@ Recommended discovery path:
6. Unsupported required plugin capability becomes a visible capability gap.
7. Optional unsupported capability becomes a visible degraded lowering.
Eve's parity harness validates this boundary directly: provider-advertised
`surfaces[].requiresPlugins[]` entries must name known plugin manifests, and
each `requiredCapabilities` item must be claimed by that plugin manifest. This
keeps plugin requirements in the provider advertisement instead of hiding them
in runtime lowerers or fixture-only metadata.
Provider advertisement sketch:
```json

View file

@ -72,6 +72,10 @@ Required top-level meanings:
- `witnesses`: CultCache `.cc` files, database exports, or document keys that
witness durable state.
- `surfaces`: Eve surface documents or endpoints the provider publishes.
- `surfaces[].requiresPlugins`: sidecar plugin capabilities required to render
or interact with that surface. Runtimes compare these requirements with their
local projection support and report visible capability gaps; they must not
import provider or plugin internals to recover missing semantics.
- `commands`: command boundaries the provider accepts.
- `routes`: transport, store, or compatibility routes used to reach the
semantic address. WebSocket and HTTP routes live here when they still exist.