Implementation Plans¶
Detailed, actionable plans for the remaining use-case gaps identified in the
Use-Case Coverage Evaluation. Each gap in
usecase-registry.yaml whose status is partial,
modeled, or planned links to one of these plans via its plan: field, and
tests/test_usecase_registry.py enforces that the linked plan file exists.
Each plan follows the same template: Problem · Goal & acceptance criteria · Design · Files & surfaces · Tests · Example fixtures · Effort & risk · Out of scope.
| Gap | Plan | Registry use cases | Effort |
|---|---|---|---|
| G4 | libclang header-AST extractor | UC-ARCH-header-only |
XL |
| G9 | manylinux/auditwheel vendored-library pairing | UC-WF-wheel-vendored |
M |
| G10 | manylinux glibc-floor check | UC-TC-glibc-floor |
S |
| G11 | Single-binary ABI audit / lint | UC-WF-audit |
M |
| G13 | Cross-architecture comparison guardrail | UC-PLAT-arch-guard |
S |
| G14 | CPython Limited-API / abi3 import-contract |
UC-WF-stable-abi-subset |
M |
| G15 | Inline-namespace version-stamp normalization | UC-CHANGE-inline-ns-version |
M |
| G16 | Header-scope toolchain robustness | UC-TC-header-scope-robustness |
M |
| G17 | Real-world validation corpus | UC-WORKFLOW-real-world-corpus |
M |
| G18 | Bazel build-evidence | UC-TC-bazel-build-evidence |
M |
| G21 | One-shot deep compare & CLI usability | UC-WF-oneshot-deep |
M |
| G22 | CLI consolidation & interface-contract enforcement | UC-WF-cli-contract |
L |
Initiative plans (cross-cutting, not tied to a single registry gap):
| Plan | ADR | Effort |
|---|---|---|
| G19 | PR-tier source intelligence & cross-source validation | ADR-035 · XL (phased) |
Completed or decided plans are retained for implementation history:
| Gap | State | Reference |
|---|---|---|
| G1 | Done — native PE/Mach-O compare validation and non-blocking MSVC+PDB lane | g1 |
| G2 | Done — build matrix folds into compare/compare-release; bundle soname-skew is wired |
g2 |
| G3 | Done — workflow scenarios and Markdown/HTML coverage | g3 |
| G5 | Done — plugin-check CLI and host↔plugin API |
g5 |
| G6 | Done — BTF/CTF and SYCL PI/UR workflows | g6 |
| G7 | Done — release recommendation | abicheck/semver.py |
| G8 | Decided — static/import archives are a by-design non-goal | g8 |
| G12 | Done — security-hardening drift surface and policy preset | g12 |
How to pick up a plan¶
- Read the plan and its registry entry/entries.
- Implement against the acceptance criteria (each plan lists them).
- Flip the registry
statustocomplete(or a higher tier) and pointevidenceat the new tests/examples. The registry test will fail if you claim coverage without real evidence — that's the gate that proves the gap is actually closed. - Update the scorecard row in the evaluation doc.