Skip to content

Follow up conformance-suite polish after PR #248 #253

@mickdarling

Description

@mickdarling

This tracks the lower-priority follow-up work intentionally deferred from PR #248.

Context: the current PR keeps the conformance runner and docs merge-ready, but these cleanup items are still worth doing in a later pass.

Open items:

  • Add a fixture schema for conformance evidence bundles and validate fixtures against it before execution.
  • Add a totals line to verify-fixtures output so CI logs are easier to scan.
  • Align or explicitly document the version command string versus package.json versioning.
  • Add a short maintainer comment explaining the intentional breadth/trade-off of the /at\s+\S+/i forbidden-error pattern.
  • Decide and document how empty round_trip_tests / update_preservation_tests should behave instead of trivially passing.

This follow-up is intentionally separate from PR #248 so the current conformance-suite work can land without turning into a larger design thread.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions