Skip to content

[EPIC][scorecard] Raise official compatibility scorecard from v0.1.2 baseline #98

Description

@midagedev

Context

Current documented scorecard baseline is from v0.1.1 and does not reflect command/transaction support added on main and released as v0.1.2.

Goal

Increase official-suite compatibility scorecard quality by reducing unsupported reasons and increasing imported differential coverage while keeping mismatch/error at zero.

Baseline (2026-02-24, documented)

  • imported: 146
  • unsupported: 868
  • mismatch: 0
  • error: 0

Success Criteria

  • Scorecard is regenerated on v0.1.2+ evidence and published.
  • Imported differential coverage increases from baseline.
  • Unsupported reason counts for targeted operations decrease materially.
  • Mismatch/error remain at zero for imported cases.

Child Issues

Priority Order

  1. [scorecard][baseline] Re-run official suite and publish v0.1.2 compatibility baseline #99 Rebaseline and freeze target gaps.
  2. [scorecard][utf] Support transaction operation adapters in unified runner #100 + [scorecard][utf] Wire unified CRUD operations to v0.1.2 command support #101 Expand UTF operation adapters for already-implemented commands.
  3. [scorecard][utf] Implement createEntities subset used by official suites #102 + [scorecard][aggregation] Reduce unsupported aggregate-stage reasons from failure ledger #104 Reduce remaining unsupported reasons (createEntities, aggregation-stage gaps).
  4. [scorecard][policy] Define and implement failPoint handling strategy for unified specs #103 Define and apply failPoint policy after baseline classification.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions