Verify opy-rs against the final workshop-rs 1.0 public API

[Teakowa]

Goal

Verify opy-rs against the final supported workshop-rs 1.0 public API and satisfy the OPY-owned downstream release gate for workshop-rs#252.

Context

opy-rs is a public-API consumer of canonical Workshop Program/domain contracts. workshop-rs#252 requires OPY-owned workflow verification of the final 1.0 candidate before release.

This issue is a final consumer verification gate, not a request to restore migration-only or private Workshop surfaces.

Scope

• Adopt the final workshop-rs 1.0 release candidate through the supported public API.
• Run the repository-required Rust/Python gates and the OPY compiler/provider workflows affected by the final candidate.
• Run pinned compatibility/reference comparisons and representative real-project workflows when the candidate changes behavior they exercise.
• Fix OPY-owned consumer breakage locally when it is caused by legitimate public-API migration.
• Route missing or incorrect canonical Workshop capability back to workshop-rs rather than duplicating or bypassing it in opy-rs.
• Report successful OPY consumer verification back to wrightkit/workshop-rs#252.

Non-goals

• Restoring private WIR/storage APIs or superseded Workshop compatibility facades.
• Reimplementing Workshop semantics inside opy-rs.
• Changing the Program-to-OPY reconstruction contract tracked separately by Define the scoped Workshop Program to OPY reconstruction contract #254.
• Expanding OPY language compatibility beyond what is required to validate the final Workshop 1.0 consumer boundary.

Acceptance criteria

• opy-rs, opy-cli, and opy-provider build and pass their required tests against the final workshop-rs 1.0 candidate.
• Relevant pinned compatibility/reference checks remain green without weakened assertions.
• Representative OPY workflows required by the candidate verification complete successfully.
• No private or migration-only Workshop API is required by opy-rs.
• Any canonical Workshop defect discovered by the verification is owned and resolved in workshop-rs, not locally approximated.
• The successful verification satisfies the opy-rs downstream gate in wrightkit/workshop-rs#252.

Ownership

• opy-rs: downstream consumer integration and OPY workflow verification.
• workshop-rs: canonical Workshop public API and 1.0 release candidate.

[e54-bot]

Dependency note: the next workshop-rs release will include wrightkit/workshop-rs#300 (ADR-0015), which stops the parser from normalizing contextual literals (False/True → 0/1, 0/zero vector → Null). Parsed programs and round-trip comparisons will distinguish these forms.

Adopting that release makes 14 oracle/fixture tests fail until OPY writes OverPy's optimizeForSize False/True substitutions; that work is tracked in #388. Keep the two apart when triaging failures from the dependency bump: API-migration failures belong here, Number vs Bool literal diffs belong to #388.

[e54-bot]

Final consumer verification — 2026-09-28

Verified opy-rs at 64bd655c6312e1774f412af6f9780bbd5cfb4094 (v0.1.61) against the published workshop-rs = 0.11.0 candidate. No source changes were needed: the consumer migrations were already present on main.

• cargo fmt --all -- --check: passed.
• cargo clippy --workspace --all-targets --all-features -- -D warnings: passed for all three crates.
• cargo test --workspace --all-targets --all-features: 539 passed, 1 ignored.
• cargo build --locked --workspace --all-targets --all-features: passed.
• python3 -B -m unittest discover -s tools/overpy/tests: 37 passed.
• Native pinned-reference gate: 108 fixtures, 100 matches, 8 declared known gaps, no unexplained divergence.
• Pinned structural gate against Bastion f693704f6ce657ccb73cbc8632568ec897f7aa20: both src/main.opy and src/externalMain.opy had 0 recorded and 0 unrecorded differences.
• Builtin-call probe: 5,152 probes, 0 unexplained differences. The probe reports 69 manifest functions without a valid generated sample call.
• GitHub CI run 36339403527 passed on the same commit.

All three consumer crates build against the published Workshop crate; no direct private WIR/storage API use was found. No canonical Workshop defect was found. This satisfies the acceptance criteria for #359.

Separate toolchain finding: a direct cargo +1.85.0 clippy --locked --workspace --all-targets --all-features -- -D warnings fails on existing let-chain syntax in OPY sources. rust-toolchain.toml pins stable, so the CI job named Rust (1.85.0) actually ran stable; the run logs confirm the override. This is an OPY MSRV/CI mismatch outside the Workshop API migration scope and was not changed here.