Add corpus-backed OPY builtin enum coverage for `ChaseTimeReeval.NONE` and nearby real-world gaps

[Teakowa]

Discovered by: wrightkit/agent-lab#68
Split from: #104

Goal

Extend Wright's OPY builtin enum/catalog compatibility using real-project evidence, starting with ChaseTimeReeval.NONE, without conflating data coverage with receiver/member parser correctness.

Context

The current OPY support matrix intentionally supports a corpus-backed subset of builtin Workshop/OverPy enum spellings. Unknown enum members fail deterministically with unknown-enum-member / unsupported-member style diagnostics rather than being guessed.

The first real agent-lab integration exposed a concrete missing enum used by an existing Workshop project:

chaseOverTime(Round_Attack_Time, 0, 30, ChaseTimeReeval.NONE)

Wright v0.1.0 rejects ChaseTimeReeval.NONE, forcing the consumer to fall back to OverPy for this otherwise relevant source path.

This is no longer hypothetical compatibility breadth: the construct now has real consumer/corpus evidence and is therefore a justified compatibility addition.

Scope

• Confirm the upstream/reference semantics and emitted Workshop representation for ChaseTimeReeval.NONE using the pinned/reference compatibility machinery.
• Add the enum/member through the appropriate data/catalog compatibility layer rather than special-casing the source text in parser logic.
• Audit the same real project/corpus for nearby members of the same enum family that would otherwise cause immediate serial fallback, and add only those justified by evidence/reference validation.
• Add differential/reference fixtures proving the accepted enum spellings lower to the expected semantic value.
• Keep unknown enum/member behavior deterministic and source-located.
• Update docs/opy/support-matrix.md to reflect the newly evidenced supported enum surface.

Non-goals

• Implementing every OverPy builtin enum solely for completeness in this issue.
• Changing OPY grammar or receiver/member parsing; Fix real-world OPY receiver/member call compatibility (eventPlayer.setMoveSpeed and peers) #104 owns that correctness path.
• Introducing Wright-only enum aliases or redefining upstream enum semantics.
• Treating generated Workshop text identity as the correctness criterion when semantic/reference equivalence is sufficient.

Acceptance criteria

• ChaseTimeReeval.NONE is accepted by the native .opy frontend and lowers/emits with reference-equivalent semantics.
• The implementation is represented through the appropriate enum/catalog data path rather than a one-off parser exception.
• At least one real-consumer/corpus fixture from the agent-lab discovery protects the behavior.
• Any additional enum members added in the same change have explicit corpus/reference evidence.
• Unknown members continue to produce deterministic structured diagnostics.
• The OPY support matrix records the expanded, evidenced enum coverage.
• Differential/frontend regression suites and CI are green.

Relationships

• Split from Fix real-world OPY receiver/member call compatibility (eventPlayer.setMoveSpeed and peers) #104 so parser/member-call correctness and enum/catalog coverage can be implemented and reviewed independently.
• Real-consumer discovery: wrightkit/agent-lab#68.
• This is compatibility expansion justified by consumer evidence, not coverage-count symmetry.