Stabilize context catalog schema v1

Problem

The context catalog schema is still fluid — field definitions, enrichment layer contracts, and integration points between the inspect pipeline, dashboard generation, and agent flows are not formally stabilized. This instability means that any component can silently break when another component changes its output format. Moving beyond the pilot to broader internal adoption and design partners requires a stable v1 schema that all consumers can depend on without fear of unannounced breaking changes.

Context

Possible Solutions

Plan

Implementation Progress

• Confirm scope and acceptance with milestone owner.

• Milestone readiness signal is updated.

• Track blockers and mitigation owner.

Review Feedback

• Review cleared