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

• Multiple consumers already depend on context artifacts: inspect outputs, schema-context formatting, MCP tools, eval backends, and generation flows.
• M1 established early contract patterns, but field semantics, optional enrichments, and compatibility expectations are still not locked tightly enough for wider M2 adoption.
• The v1 goal should be stability and explicit compatibility rules, not maximal richness or new source ingestion.

Possible Solutions

• A - Freeze the current shape informally and rely on tests to catch drift: cheap, but it leaves field meaning and migration rules ambiguous.
• B - Recommended: publish a versioned v1 context schema contract with required and optional fields, source-attribution rules, and compatibility expectations, then align key producers and consumers to it.
• C - Rebuild the schema around a larger typed framework before stabilizing anything: more ambitious, but too disruptive for M2 hardening.

Plan

1. Inventory the current producer and consumer surfaces and identify the minimum stable field set they all rely on.
2. Define and document the v1 schema contract, including versioning, optional sections, provenance, and compatibility rules.
3. Update the main producer and consumer paths to conform to that contract and add golden or contract-style tests.
4. Record migration notes, deferred enrichments, and the acceptance criteria for calling schema v1 stable.

Implementation Progress

• Confirm scope and acceptance with milestone owner.

• Milestone readiness signal is updated.

• Track blockers and mitigation owner.

Review Feedback

• [ ] Review cleared