PUMA v3.1.0 — Sprint 11' Post-v3.0.0 Reconciliation¶

Release date: 2026-05-25
Previous release: v3.0.0 (2026-05-20)
Tag: v3.1.0

Overview¶

Sprint 11' is a post-v3.0.0 hardening Sprint: it reconciles the v3.0.0 release artifacts (version strings, CHANGELOG, release notes), completes the puma community CLI subgroup, applies minimal repairs to the wiki-sync workflows and the Verifier Space, and cleans residual documentation drift while preserving historical accuracy. No breaking changes.

Highlights¶

New puma community Typer group with four subcommands — browse, pull, verify-hash, validate. The GitHub Contents API is read over httpx (mockable in tests); verify-hash recomputes the predictions hash byte-identically to the client and is D23-aware on --remote.
Server-side hash output now matches schema v1.0.0 — the public verifier service no longer emits the sha256: prefix, so its digest conforms to ^[a-f0-9]{64}$.
Wiki sync works again in both repos — the wiki-sync.yml workflows now declare contents: write, so the GitHub Wiki publishes on push; both /wiki pages render (HTTP 200).
D23 technical-debt entry documented — the server-side (2-field JSONL) and client (4-field DB CSV) hash algorithms differ by construction; reconciliation is deferred to v4.x with a schema decision.

Quality at release time¶

mypy --strict: 0 errors / 81 files
pytest -m "not ollama": 597 passed, 1 skipped, 7 deselected
pytest -m ollama: 7 passed
F1 triage baseline: 0.5831 ± 0.01 (Δ = −0.0036)
MAE estimation baseline: 5.7150 bit-exact (Δ = +0.0000)
Coverage on community CLI: browse 80%, pull 87%, verify 85%, validate 89%
Schema v1.0.0 unchanged (P3); zero federation references in code (P4).

Known limitations¶

D23: puma community verify-hash --remote returns mismatch by construction for schema v1.0.0 submissions even when the local hash is correct, because the server-side hash and the client hash are computed over different input shapes. Local verification (the canonical path) is unaffected. Reconciliation deferred to v4.x with a schema decision. See docs/known_debt.md.
Kaggle mirror activation (S11'.6): the mirror-kaggle.yml workflow is fully hardened (companion PR pumacp/puma-community#4: --dir-mode zip, robust create-vs-version, CC-BY-4.0 license, 50-char-safe title, post-publish HEAD verification). Publication is pending a Kaggle-internal soft-delete grace period that reserves the slug pumacp/puma-community-submissions; it resolves automatically once Kaggle releases the slug — no further code action is needed.

Upgrade path¶

No breaking changes since v3.0.0. Refresh with:

git pull && pip install -e '.[dev]'