Skip to content

Resolve residual source failure-frontier mismatches after #162 #167

Description

@Teakowa

Parent: #1
Evidence baseline: #158 / PR #159
Discovered by: full conformance rerun after #162 / PR #166

Goal

Resolve the remaining OPY source-language failure-frontier mismatches exposed after #160, #161, and #162 completed, before residual work is handed to compiler/canonical-WIR convergence in #157.

Context

The full offline conformance rerun from PR #166 reports 63 fixtures with 44 match, 17 divergence, and 2 inconclusive. Most remaining divergences now occur at lowering/canonical-WIR, but two cases still fail earlier in native source processing than in pinned OverPy:

  • real-world/6v6-adjustments: pinned OverPy reaches an unknown-member semantic failure; native stops earlier with parser errors, first at constants/adj_constants.opy.
  • synthetic/issue-29-invalid: pinned OverPy reaches the duplicate-rule-name semantic failure; native stops earlier on @Name parsing/placement.

These are not compiler/WIR residuals and must not be folded into #157 merely because the earlier stage workstreams are closed.

Scope

  • Determine the root source-language capability behind each remaining earlier native failure using the existing Re-establish offline OverPy conformance with independent oracle evidence #158 oracle/provenance evidence.
  • Make native parsing/source semantics reach the pinned reference frontier for the demonstrated constructs.
  • Preserve diagnostic provenance and the existing stage/frontier comparison contract.
  • Re-run the full offline conformance suite and confirm that no remaining divergence fails earlier than the pinned reference before lowering.
  • Reclassify only genuinely later-stage residuals to Converge residual OPY compiler and canonical-WIR gaps #157 after this boundary is clean.

Non-goals

Acceptance criteria

  • real-world/6v6-adjustments no longer fails natively before the pinned semantic frontier, or independent evidence demonstrates a different valid ownership classification.
  • synthetic/issue-29-invalid no longer fails natively before the pinned duplicate-rule-name semantic frontier, or independent evidence demonstrates a different valid ownership classification.
  • The full offline conformance rerun contains no remaining OPY-owned lexer/parser/preprocessing/source-semantic divergence that precedes a later pinned reference frontier.
  • Remaining divergences are demonstrably lowering/canonical-WIR, Workshop-owned, or explicitly inconclusive with provenance.
  • Existing Re-establish offline OverPy conformance with independent oracle evidence #158 oracle expectations remain independent of the implementation changes.

Dependencies / ownership

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

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions