Skip to content

Synchronize Wright's Workshop dependency graph on workshop-rs 0.1.18 #259

Description

@Teakowa

Blocks: #245
Depends on: wrightkit/workshop-rs#141, wrightkit/opy-rs#185, wrightkit/deltin-rs#86

Goal

Synchronize Wright's canonical Workshop dependency graph on the released workshop-rs 0.1.18 contract used by the current first-party OPY provider, then rerun the real-project compile gate before assigning any remaining artifact parser failure to a semantic owner.

Context

The released opy-provider v0.1.18 consumes workshop-rs v0.1.18 and produces non-empty workshop-rs/text-v1 artifacts with zero provider diagnostics for the pinned Bastion zh-CN/en-US and Overwatch-AI-PVE zh-CN workflows.

Wright currently consumes an older Workshop contract directly, while its released deltin-rs dependency also exactly requires workshop-rs 0.1.11. Cargo cannot resolve that released DEL dependency together with a direct Wright workshop-rs 0.1.18 requirement. The downstream graph therefore needs a released DEL consumer aligned with 0.1.18 before Wright can remove the canonical-core version skew.

Scope

  • Consume released workshop-rs 0.1.18 as Wright's canonical Workshop dependency.
  • Consume a released deltin-rs version from [M11 settings] Typed custom-game-settings support in the native frontend (v1 corpus boundary) #86 that is compatible with the same workshop-rs 0.1.18 contract.
  • Adapt Wright only where required by the released public Workshop/DEL contracts; do not recreate source-language or Workshop semantics locally.
  • Preserve raw Workshop and existing DEL integration behavior through the dependency migration.
  • Rerun the pinned Bastion src/main.opy zh-CN and en-US workflows and Overwatch-AI-PVE src/main.opy --root src zh-CN through released opy-provider v0.1.18.
  • Record whether the two existing settings parser diagnostics disappear or remain after producer and consumer use the synchronized released Workshop contract.
  • Route any remaining independently reproduced semantic defect to its owning repository rather than expanding this migration.

Non-goals

  • Changing OPY or DEL syntax/semantics, preprocessing, lowering, or provider protocol behavior.
  • Adding Wright-side Workshop/source-language semantic fallbacks or compatibility copies.
  • Broad dependency modernization unrelated to Workshop contract convergence.
  • Redesigning Wright's provider/dependency architecture in this issue.
  • Treating compiler-output text identity with upstream compilers as the compatibility target.
  • Fixing unrelated semantic defects exposed after the version skew is removed.

Acceptance criteria

  • Wright resolves, builds, and tests with one released workshop-rs 0.1.18 contract across its direct and released source-language dependencies.
  • No second canonical Workshop implementation or semantic compatibility shim is introduced.
  • Existing raw Workshop and DEL integration regressions remain green within their declared supported surfaces.
  • Released opy-provider v0.1.18 can be acquired/used through the existing Wright provider path without fallback.
  • The three pinned correct-entry OPY compile workflows are rerun after dependency convergence.
  • If the previous settings parser errors disappear, Run real OPY check and compile workflows through the first-party provider #245 records the version-skew resolution and proceeds to final verification.
  • If either error remains, its provider-artifact provenance is preserved and ownership is established from the synchronized canonical contract before a new implementation issue is filed.
  • Independent implementation ablation restoring the previous released dependency graph reproduces the exact-version resolution conflict or the relevant real-project regression.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions