Skip to content

api: define divergence policy and guardrails for round-trip corpus coverage #214

Description

@webern

Sub-task of #208. See the parent tracking issue for the full plan and context.

Scope: keep discovery non-gating, decide per divergence class whether it belongs in the api, in a fixup-style expected alteration, or is out of scope, and optionally track a near-miss count to catch drift.

Metadata

Metadata

Assignees

No one assigned

    Labels

    aiIssues opened by, or through, a coding agent.area/mx::apinon-breakingfixes or implementation that do not require breaking changestesting

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions