P1 contract — independent JSON-Schema (Draft 2020-12) validation smoke test

At a glance

Goals

None recorded yet.

Spec document

docs/specs/P1-scan-io-contract.md → · source ↗

Implementation — what to build

No implementation plan yet — derive it from the linked requirement (statement + done-when) and the Spec links below.

Checklist

• ✓ P1 Scan I/O contract schemas and versioning are frozen: request envelope, per-scan_type result schemas, scan_version/result_version, shared enums, and the normalized 0-1000 coordinate contract.

Gates & testing

• ✓ P1 Scan I/O contract schemas and versioning are frozen: request envelope, per-scan_type result schemas, scan_version/result_version, shared enums, and the normalized 0-1000 coordinate contract.
  CODE TEST

Requirements

No linked requirements.

Verify (done when)

Validate the packages/scan-contracts golden fixtures (valid + invalid) against the canonical JSON-Schema bundle with a standard Draft 2020-12 validator (not only the custom semantic validator), so external/provider consumers interpret the bundle identically. Keyless. From the P&C Wave 1 retro (D39, finding 3).

Cost triggers

No paid API / infra spend triggered by this item.

Status & editing

queued   Sprint: Backlog

Edit status / sprint on the ★ Live Board → — changes are logged live with who / when / why.

Human-in-the-loop

No human tasks linked.

Findings

None recorded yet.

Concerns

None recorded yet.

Risks

None recorded yet.

Tech debt

None recorded yet.

Tools used

No tool calls recorded.

Files & artifacts

No files / artifacts recorded.

Update log

No log entries yet.