Skip to content

refactor(opy): retire top-level compatibility subsystem - #196

Merged
Teakowa merged 2 commits into
mainfrom
codex/issue-117-retire-compatibility
Sep 6, 2026
Merged

refactor(opy): retire top-level compatibility subsystem#196
Teakowa merged 2 commits into
mainfrom
codex/issue-117-retire-compatibility

Conversation

@e54-bot

@e54-bot e54-bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

Summary

  • retire the top-level compatibility/ subsystem
  • move the OverPy evidence harness to tools/overpy/
  • move the corpus and native expectations under opy-rs tests, and make the canonical language-support inventories authoritative
  • preserve the differential/compiler evidence gates and the CLI support projection

Validation

  • python3 -B -m unittest discover -s tools/overpy/tests
  • cargo fmt --all -- --check
  • cargo clippy --locked --workspace --all-targets --all-features -- -D warnings
  • cargo test --locked --workspace --all-targets --all-features
  • independent ablation confirmed the differential gate fails when the corpus is removed

Fixes #117

Move the OverPy corpus, oracle harness, and pinned inventories to their stable owners while keeping the differential and compiler evidence gates operational.

Fixes #117

@Teakowa Teakowa left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One blocking issue against #117's single-authoritative-support-contract acceptance criterion.

Comment thread docs/language-support.md Outdated
It is not a public inventory and its internal states are not public support
states. `docs/opy/support-matrix.md` is retained as historical context and
must not introduce another public status vocabulary.
The embedded `crates/opy-rs/support-matrix.json` is an operational CLI

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not currently a projection. crates/opy-rs/support-matrix.json still carries its own dated snapshot, support-state vocabulary, feature rows, and evidence, and SupportMatrix::builtin() / opy support expose it directly. Nothing derives or validates those states against docs/language-support/*, so this remains a competing support-status source that can drift—the exact bookkeeping #117 requires retiring. Derive the CLI output from the authoritative inventories, or retire the legacy support matrix/API after consumer migration.

Make the canonical language-support inventories the sole support-status contract by retiring the standalone matrix, accessor, CLI command, and linkage test.

Refs #117

@Teakowa Teakowa left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Teakowa
Teakowa merged commit e56a62e into main Sep 6, 2026
5 checks passed
@Teakowa
Teakowa deleted the codex/issue-117-retire-compatibility branch September 6, 2026 05:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Retire compatibility/ as a top-level subsystem

2 participants