Disambiguate canonical enum members for downstream compiler oracle fixtures

[e54-bot]

Goal

Resolve canonical Workshop catalog ambiguity that currently prevents downstream compiler compatibility harnesses from parsing pinned oracle Workshop text into canonical WIR.

Context

The opy-rs #38 compiler gate has two concrete cases that cannot reach semantic-WIR comparison because the released workshop-rs catalog reports ambiguous enum members:

• opy-rs real-world/overpy-cake: Visible To matches multiple domains;
• opy-rs synthetic/chase-condition-agentlab: None matches multiple domains.

These are canonical catalog/parser domain-resolution failures, not OPY lowering gaps. The affected pinned oracle and fixture provenance remain in opy-rs and must stay independently verifiable.

Scope

• Define the canonical domain-resolution rule for the affected enum members.
• Add parser/catalog tests that prove the selected identity is deterministic and locale-independent.
• Expose a released canonical-WIR parse contract that downstream opy-rs can consume without aliases, fallback guesses, or text-only evidence.

Non-goals

• No OPY parser or lowering implementation.
• No source-language-specific aliases in workshop-rs.
• No acceptance based only on emitted text or a reparse round trip.

Acceptance criteria

• Both pinned oracle cases parse to canonical WIR with a stable, documented identity under the released catalog.
• Ambiguous domain resolution has direct canonical tests and remains explicit for unsupported inputs.
• opy-rs can switch its compiler expectation entries from compiler-contract to direct semantic-wir comparison without adding a fallback path.