Skip to content

Freeze the stable API and artifact compatibility boundary #59

Description

@stefan-jansen

Findings: BR-013.

Enforce exact versioned snapshots for the stable exports, documented imports, signatures, enums,
configuration schema, profiles, result methods, metrics, and artifacts. Correctness-breaking beta
behavior must have explicit migration treatment rather than accidental compatibility claims.

Primary surfaces: public API tests, config and profile snapshots, artifact fixtures, deprecation
tests and documentation.

Acceptance:

  • Unreviewed additions, removals, signature changes, default changes, enum changes, or schema
    changes fail compatibility tests.
  • Representative supported beta artifacts load without silent semantic change.
  • The documented deprecated Broker constructor either follows the deprecation contract or is
    removed from compatibility claims with a documented correctness exception.

Dependencies: Issues 3, 5-7, and 12.


Plan reference: /home/stefan/ml4t/libraries/ml4t-backtest-dev/.workspace/work/backtest-stable-release/milestone-3/plan.md - Issue 19 in milestone 0.1.0-m3 - Compatibility and release enforcement.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions