Skip to content

[v0.2] Establish the language-provider boundary and canonical Workshop core #135

Description

@Teakowa

Roadmap: #134

Goal

Deliver Wright v0.2 as the first real multi-repository architecture release: neutral provider protocol, independent canonical Workshop core, and Wright-side integration without prematurely cutting over OPY/DEL production providers.

Release work

Non-goals

  • Production opy-rs cutover; target v0.3.
  • Production del-rs cutover; target v0.4.
  • New refactoring categories merely to exercise LPP.
  • Implementing a third real language; conformance/mock-provider evidence is sufficient for v0.2.
  • Public AST/HIR/WIR ABI.
  • Compatibility expansion unrelated to the ownership migration.

Acceptance criteria

  • The ownership decision is accepted and living Wright docs match it.
  • language-provider-protocol and workshop-rs are real independently versioned repositories with usable contracts, not placeholders.
  • LPP v1 is provider/language agnostic and has machine-testable conformance.
  • workshop-rs owns canonical Workshop semantics/catalog/WIR and demonstrates the declared en-US <-> zh-CN raw Workshop conversion gate.
  • Wright consumes workshop-rs without retaining a second canonical Workshop implementation.
  • Wright initializes a conforming provider through its LPP client and exercises validated mutation through that boundary.
  • Existing declared Wright compile/check/lint/analyze/inspect/convert/language-service behavior stays regression-green during migration.
  • Active repository terminology and AGENTS.md route work to the correct repository owner.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Status
    Done

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions