# Sprint 92 Plan: Interop Testbeds and Reference Implementations

## Context

External ecosystem adoption improves when reference implementations are available.
Sprint 92 delivers interop testbeds and canonical references.

---

## Goals

1. Build multi-language interop testbeds for common migration classes
2. Publish reference implementations for core specs
3. Validate third-party conformance against reference behavior
4. Reduce ambiguity in cross-vendor interpretation

---

## Steps

### Step 1149: Interop testbed manifest model (12 tests)
### Step 1150: Reference implementation harness for IR/evidence specs (10 tests)
### Step 1151: Third-party conformance replay runner (10 tests)
### Step 1152: Canonical fixture and oracle dataset packs (10 tests)
### Step 1153: Divergence triage model for interop failures (10 tests)
### Step 1154: Interop certification policy bindings (8 tests)
### Step 1155: `whetstone_run_interop_testbed` MCP tool (8 tests)
### Step 1156: `whetstone_get_reference_conformance_report` MCP tool (8 tests)
### Step 1157: Interop publication bundle (8 tests)
### Step 1158: Sprint 92 integration summary + regression (8 tests)

---

## Interop Rule

- Spec compliance claims require passing published interop testbeds.