[E11-S03] Compatibility validator #95

New Issue

2026-08-27T00:02:36Z

kpcto commented

2026-08-27 00:02:36 +00:00

Parent epic: [E11] Extension API v1 (#39)

Intent

Validate extension compatibility before activation across API version, core version range, dependencies, manifest schema, and contribution IDs, and mark incompatible extensions safely.

Acceptance criteria

Validates that the extension API version is supported before activation.
Validates that the running core satisfies the extension's declared core version range.
Validates that all declared dependencies are present.
Validates the manifest against the manifest JSON Schema.
Validates that contribution IDs are unique and namespaced.
An incompatible extension is marked incompatible with diagnostics without taking down unrelated features.

Explicitly out of scope

Publishing the manifest contract (E11-S01) or extension context (E11-S02).
Persisting extension state (E11-S04).
Extension migrations (E13).

Test plan

Drive the activation sequence with valid, out-of-range, missing-dependency, and duplicate-ID manifests and assert the resulting lifecycle state.

Rollback note

Disable the validation gate and re-activate; no data migration is required.

Owning stream

platform

Risk quadrant

agent-full

> Parent epic: [E11] Extension API v1 (#39) ## Intent Validate extension compatibility before activation across API version, core version range, dependencies, manifest schema, and contribution IDs, and mark incompatible extensions safely. ## Acceptance criteria - Validates that the extension API version is supported before activation. - Validates that the running core satisfies the extension's declared core version range. - Validates that all declared dependencies are present. - Validates the manifest against the manifest JSON Schema. - Validates that contribution IDs are unique and namespaced. - An incompatible extension is marked `incompatible` with diagnostics without taking down unrelated features. ## Explicitly out of scope - Publishing the manifest contract (E11-S01) or extension context (E11-S02). - Persisting extension state (E11-S04). - Extension migrations (E13). ## Test plan - Drive the activation sequence with valid, out-of-range, missing-dependency, and duplicate-ID manifests and assert the resulting lifecycle state. ## Rollback note - Disable the validation gate and re-activate; no data migration is required. ### Owning stream platform ### Risk quadrant agent-full

kpcto added this to the Sprint 3 milestone 2026-08-27 00:02:36 +00:00

kpcto added the

labels 2026-08-27 00:02:36 +00:00

kpcto referenced this issue

2026-08-27 08:02:01 +00:00

[E11-S03-T01] Compatibility validator #278

Sign in to join this conversation.