Qualify all seven stable libraries against the ecosystem standard

[stefan-jansen]

Objective

Qualify data, engineer, backtest, specs, live, diagnostic, and models against the shared stable-release standard, remediate every actionable deviation, and retain a dated evidence snapshot.

Libraries

• ml4t/data
• ml4t/engineer
• ml4t/backtest
• ml4t/specs
• ml4t/live
• ml4t/diagnostic
• ml4t/models

Required evidence

• Python 3.12 through 3.14 on Linux, macOS, and Windows
• Python 3.15 prerelease installation and non-hardware-dependent tests on all three systems
• Installation from built wheel and public import
• Tests, Ruff, ty, and package build
• Stable source and published metadata
• Strict MkDocs build and correct deployment route
• Standard issue forms, labels, pull-request linkage, and private vulnerability reporting
• Central qualification in pull requests and release workflows
• Current user issue and pull-request response review

Completion

Every linked library issue is closed by a verified pull request and required patch release, or records an exact product-decision or credential blocker with all independent work complete.

[stefan-jansen]

Current release blocker: #2. The integration branches now contain the completed runner, dependency-group, Pydantic, and PyTorch fixes. Final merge and stable publication remain blocked until the accepted upstream Polars Python 3.15 datetime fix is released and the full three-OS prerelease matrix passes.

[stefan-jansen]

Branch qualification is complete for the reviewed commits. Backtest, specs, live, and models satisfy the full Python 3.12-3.15 policy. Data and engineer pass every stable job but fail all three Python 3.15 jobs in Polars. Diagnostic passes every stable job but fails all three Python 3.15 installations because SciPy has no compatible wheels. Authenticated monitoring reports no overdue open issue or pull-request responses. No integration pull request is merged: the app token receives HTTP 403 and the maintainer CLI merge action is unavailable in this execution environment. Full evidence: https://github.com/ml4t/ecosystem/blob/main/reviews/2026-08-11-initial-qualification.md

[stefan-jansen]

Qualification update for 2026-08-11: temporary, expiring Python 3.15 exceptions are now enforced for data and engineer (Polars) and diagnostic (SciPy). Data, backtest, live, and diagnostic have completed their latest hosted checks without failures; engineer, specs, and models still have hosted jobs running with no failures observed. Canonical release checkouts are clean and synchronized, proven dead branches and completed worktrees were removed, and unique unresolved branches were retained to prevent data loss. The ecosystem CI and authenticated audit pass on commit 723cd71 or later. Merge attempts remain blocked by the execution environment's disabled approval path, so an authorized maintainer must merge the reviewed PR heads after all checks complete.

[stefan-jansen]

Progress update on 2026-08-11:\n\n- All seven reviewed qualification PRs merged without bypassing checks. Canonical release checkouts are clean, synchronized main branches.\n- Fresh local default-branch gates pass in all seven libraries. The two discovered failures have fixes in engineer#36 and backtest#77; both full local suites and documentation/package gates pass.\n- Diagnostic fixes are requalified in PRs #35 and #36, with release PR #37 retained for the subsequent 0.1.1 merge.\n- Specs and models release branches are pushed at release/0.1.3 (7a213ef) and release/0.1.1 (8620a8e), with full local gates and isolated wheel imports passing.\n- The Specs deploy key is installed. Its docs workflow succeeded and pushed ml4t/website@8839f1a; downstream website CI is running, so the public route is not yet accepted.\n- PyPI artifact imports pass on Python 3.14.3 for all current releases. The temporary collector now fails only the known published-state gaps: live 0.1.0 still excludes Python 3.15, and diagnostic 0.1.0 lacks the stable classifier.\n- Retained unique branches are assigned to data#43, engineer#38, backtest#78, live#57, and diagnostic#41. The one explicitly rejected obsolete live branch was removed; ecosystem#3 is complete.\n- Upstream exceptions were rechecked and remain necessary without expansion.\n\nCurrent external blockers: GitHub-hosted final jobs are still queued with no observed failures, and the execution harness rejects both gh pr create and later gh pr merge commands before they reach GitHub because its approval path is disabled. This is not a GitHub authentication or branch-protection failure.