Close residual OPY frontend and project-corpus compiler gaps

[e54-bot]

Goal

Close the concrete OPY frontend and full-project compiler gaps that remain outside the #38 baseline.

Scope

Track and add executable pinned-oracle coverage for the currently declared gap cases:

• real-world/6v6-adjustments, overpy-broken-weapons, overpy-client-to-server,
  overpy-crosshair, overpy-inputhud, overpy-meipocalypse, overpy-parabola,
  overpy-pixelart, overpy-santa, overpy-zencopter, and ow1-emulator;
• synthetic/chase-keywords, declarations-rules, diagnostics,
  expressions-values, issue-28-invalid-syntax, issue-28-string-modifiers,
  issue-28-syntax, issue-29-directives, issue-29-invalid, issue-31-negative,
  issue-31-nested-scope, issue-31-positive, issue-33-f-string,
  issue-33-lambda-negative, and receiver-playervar.

These cases are OPY frontend or project-corpus gaps. Preserve source attribution and the full-project provenance for every fix. Update the compiler expectation only after the public compile path reaches the pinned oracle contract.

Non-goals

• No Wright-side fallback or duplicated Workshop semantics.
• No weakening of the compatibility runner or its independent oracle evidence.
• No changes to the bounded control-flow/WIR carrier work tracked separately.
• No canonical Workshop parser/catalog fixes; those belong in workshop-rs.

Acceptance criteria

• Each listed fixture has an executable minimized or project-level regression.
• Successful cases compare through canonical WIR or a semantics-preserving normalized contract; failures retain stable source diagnostics.
• The support matrix and compiler expectations identify the concrete capability and no longer use the Integrate OPY lowering and end-to-end compatibility with workshop-rs #8 parent as the owner.
• Every listed gap is closed or remains explicitly linked to this issue with fixture provenance and an independently verified result.