Skip to content

Reconcile OPY semantic coverage with the workshop-rs catalog boundary #30

Description

@Teakowa

Parent: #7

Goal

Finish the pre-integration semantic contract for builtin actions/values, receiver members, and enum domains without turning opy-rs into a second Workshop catalog.

Context

The support matrix currently leaves full builtin/action/value, receiver/member, and enum-domain coverage as planned. The ownership-fixed manifest correctly owns OPY language/API identities, signatures, aliases, contextual dispatch, and catalogId links, while canonical Workshop existence/member/domain/content validation belongs to workshop-rs.

wrightkit/workshop-rs#2 is now complete, so these mixed rows should be resolved before #8: OPY-specific semantic overlay stays here; authoritative Workshop catalog coverage moves to the integration boundary rather than being duplicated locally.

Scope

  • Audit the three planned semantic rows (semantics/builtin-actions-values, semantics/receiver-members, semantics/enum-domains) against the accepted manifest ownership contract.
  • Identify the minimal OPY-owned metadata required before lowering: source spellings/aliases that differ from canonical Workshop identities, call kind, argument binding/signatures, contextual dispatch, receiver syntax/category semantics, OPY-only defaults/macros, and canonical catalogId/domain identity links.
  • Expand the manifest only where oracle/corpus evidence shows genuine OPY language semantics that cannot be derived from the canonical Workshop contract.
  • Do not add authoritative Workshop member lists, hero/map/mode/settings data, localized spellings, or a copied exhaustive Workshop builtin catalog.
  • Split/reclassify support-matrix rows so OPY semantic overlay coverage and Workshop catalog/member/domain validation have separate statuses.
  • Preserve unknown-name/arity/context diagnostics that can be decided from OPY-owned evidence; defer canonical Workshop existence/domain/member validation to Integrate OPY lowering and end-to-end compatibility with workshop-rs #8.
  • Define the concrete catalog-link/cross-check inputs that Integrate OPY lowering and end-to-end compatibility with workshop-rs #8 will consume from workshop-rs, without adding the dependency in this issue.
  • Add or refine probes/minimized fixtures for every OPY-owned semantic rule retained or added.

Non-goals

Acceptance criteria

  • The support matrix no longer represents canonical Workshop catalog breadth as unfinished Workshop-independent work in opy-rs.
  • Every semantic rule retained in the OPY manifest has independent oracle/corpus evidence and a clear OPY-language reason to live here.
  • Workshop-owned builtin/member/enum existence and content validation is explicitly assigned to Integrate OPY lowering and end-to-end compatibility with workshop-rs #8/workshop-rs.
  • No authoritative Workshop catalog/member/content data is duplicated in the repository.
  • The resulting OPY semantic model can be connected to workshop-rs through canonical identity links without parser/frontend redesign.
  • Existing semantic diagnostics, tooling APIs, differential evidence, and provenance gates remain green.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions