Governance repair. src/ is untouched — the wheel is byte-identical to v1.10.0 apart from metadata.
Upgrading
pip install --upgrade views-datafactoryOne thing changes for you: the views-frames floor moves from >=1.0 to >=1.10.2. If your environment pins views-frames below 1.10.2, resolution will now fail. That is deliberate.
Why the floor moved
views-frames changed how the summary statistics are computed, three times, all shipped MINOR so none of it reads as breaking:
| Version | Change |
|---|---|
| 1.2.0 | outside-in HDI tower + mass-aware tip — "fixes a silent" error |
| 1.3.0 | no magnitude-based zeroing by default |
| 1.9.0 | tower-tip MAP: tip_mass 0.5 → 0.25 — "Behavior change to tower_point/summarize_tower outputs" |
A floor of >=1.0 admitted all three semantics. Worse, it froze one: uv lock keeps an existing pin while it still satisfies the constraint, so our lockfile held views-frames 1.0.0 from June until 2026-08-02, and six weeks of CI ran against pre-amendment MAP/HDI.
This package does not import the estimators — and that is irrelevant. A floor constrains the resolver, not the import list. Registered as C-337; views-frames#237 filed upstream, because CONFORMANCE_FLOOR = "1.0.0" reads as a safe dependency floor and is not one.
Also in this release
Release procedure (#402). Two guides described contradictory rituals and the more detailed one prescribed git merge development --ff-only and git push origin development — both forbidden by branch protection since July. Consolidated into publishing_to_pypi.md, with the post-release back-merge that had been silently skipped after every release before v1.10.0. release-topology.yml now detects the divergence daily.
Monitoring. C-335 closed — the serving path is now watched from outside the host and verified live. Previously, if the web server stopped while the machine stayed up, the pipeline kept succeeding, kept pinging, and nothing ever noticed. The freshness half is serving-freshness.yml rather than a paid vendor feature — and the drill found ADR-051's specification of that check was itself wrong (it would have matched the page's own legend), so buying it would not have helped.
Documentation. validate_docs.sh now runs in CI as a required check, having previously run nowhere at all. Full audit of 54 ADRs and 34 CICs: ten line-number citations replaced with symbol names, references to a package another repo deleted annotated rather than erased, and a contract written for load_dataset — the public consumer entry point, which had none while 32 config dataclasses did.
Operational. C-330 resolved on the server: logrotate had been pointing at a path the pipeline left months earlier, and missingok made it exit successfully every night for four months. C-339 registered — the pipeline log was destroyed by a badly-formed command during that fix.
Full changelog: v1.10.0...v1.11.0