docs(opy): remove stale compatibility contract residue

AGENTS.md

@@ -119,7 +119,7 @@ feature cohesive is in scope; unrelated cleanup remains out of scope.
 cargo fmt --all -- --check
 cargo clippy --workspace --all-targets --all-features -- -D warnings
 cargo test --workspace --all-targets --all-features
-python3 -m unittest discover -s compatibility/tests
+python3 -m unittest discover -s tools/overpy/tests
 ```
 
 Oracle-required compatibility probes run separately against the pinned

README.md

@@ -87,28 +87,16 @@ The Rust library surface, including the bounded Workshop compiler, lives in
 Compatibility targets observable OverPy semantics for the declared support
 surface, not byte-identical output, optimizer choices, formatting, temporary
 variables, or upstream internal architecture. Support claims are backed by the
-compatibility corpus and pinned OverPy reference evidence.
+canonical [language-support contract](docs/language-support.md), its linked
+inventories, and pinned OverPy reference evidence.
 
 > [!IMPORTANT]
 > `opy-rs` follows the OverPy language. It does not introduce a WrightKit-only
 > OPY dialect.
 
-| Capability | Status | Notes |
-| --- | --- | --- |
-| Core syntax & control flow | ✅ Supported | Workshop-independent parsing and semantic representation |
-| Declarations | ✅ Supported | `globalvar`/`playervar`, `subroutine`, `def`, `enum`, `macro` |
-| Preprocessing & macros | ✅ Supported | `#!include`, `#!define`, `#!undef`, bounded JavaScript macros |
-| Rules & directives | ✅ Supported | Rules, events, conditions, team/slot context in the declared surface |
-| Builtin actions & values | 🟡 Partial | Declared semantic subset works; full catalog-backed breadth is still being closed |
-| Receiver/member functions | 🟡 Partial | Declared members work; full member breadth is not yet complete |
-| Enums & constants | 🟡 Partial | Declared domains resolve; full domain breadth is not yet complete |
-| Advanced directives, translations & optimizer controls | 🟡 Partial | Source state exists; Workshop-dependent effects remain incomplete |
-| OPY → Workshop compilation | 🟡 Partial | The versioned library/CLI compile contract and bounded lowering surface are supported; remaining corpus gaps stay explicit |
-| Workshop → OPY reconstruction | ⏳ Not yet | Will consume canonical `workshop-rs` semantics and remain owned by `opy-rs` |
-
-The exhaustive per-feature evidence and pinned denominator are maintained in
-the [canonical human-readable support contract](docs/language-support.md) and
-its linked inventories.
+The exhaustive per-feature evidence, pinned denominator, and current status are
+maintained in the [canonical human-readable support contract](docs/language-support.md)
+and its linked inventories.
 
 ## Relationship with Wright
 

docs/README.md

@@ -41,9 +41,7 @@ compatibility pointers rather than separate architecture authorities.
 
 - [OverPy support contract](language-support.md): current evidenced feature
   coverage.
-- [Compatibility baseline](opy/compatibility-baseline.md): planning/reference
-  inventory for remaining evidence work.
-- [Offline conformance baseline](opy/conformance-baseline.md): oracle and
+- [Offline conformance evidence](opy/conformance-baseline.md): oracle and
   comparison methodology.
 - [Upstream references](compatibility/upstream-references.md): pinned upstream
   identity, provenance, licensing, and reference boundaries.

docs/compatibility/upstream-references.md

@@ -66,9 +66,9 @@ it serves as:
 * the reference for S (syntax), D (diagnostic), and N (normalized-output)
   evidence in the compatibility corpus (`crates/opy-rs/tests/fixtures/corpus/**`,
   `tools/overpy/oracle/`);
-* the source of systematic probe validation for the proactive compatibility
-  baseline (see [`docs/opy/compatibility-baseline.md`](../opy/compatibility-baseline.md)
-  and [`docs/opy/compat-manifest-spec.md`](../opy/compat-manifest-spec.md));
+* the source of systematic probe validation for the pinned language-support
+  inventories (see [`docs/language-support.md`](../language-support.md) and
+  [`docs/opy/compat-manifest-spec.md`](../opy/compat-manifest-spec.md));
 * the reference for differential parity at the Opy HIR v2 boundary
   ([`docs/hir/opy-hir-v2.md`](../hir/opy-hir-v2.md)): the native differential
   suite (`crates/opy-rs/tests/differential.rs`, merged in PR #13) runs
@@ -262,7 +262,6 @@ when the oracle is absent.
 ## Related documents
 
 * [`docs/language-support.md`](../language-support.md): audited public support contract and current states
-* [`docs/opy/compatibility-baseline.md`](../opy/compatibility-baseline.md): tiered planning baseline
 * [`docs/opy/compat-manifest-spec.md`](../opy/compat-manifest-spec.md): machine-readable semantic manifest specification
 * [`docs/opy/tooling-notes.md`](../opy/tooling-notes.md): harness usage
 * [`tools/overpy/README.md`](../../tools/overpy/README.md): oracle and fixture layout

docs/opy/architecture.md

@@ -7,5 +7,3 @@ The current architecture contracts are maintained under
 - [`workshop-boundary.md`](../architecture/workshop-boundary.md) — canonical Workshop dependency/lowering/reconstruction boundary.
 
 This path is retained for existing links. The previous "accepted living architecture" combined current contracts, implementation mechanisms, capability status, and references to the semantic manifest. That content remains available in Git history but is no longer the current architecture authority.
-
-Current support must be established from [`../language-support.md`](../language-support.md) and executable evidence. Current implementation reality comes from source, tests, Cargo metadata, corpus/differential evidence, and real-project workflows. ADRs or older design prose do not prove either.