messagefoundry 0.3.1__tar.gz → 0.3.2__tar.gz

{messagefoundry-0.3.1 → messagefoundry-0.3.2}/.gitignore

@@ -59,6 +59,22 @@ secrets/
 .vscode/
 .idea/
 
+# CI-only quality artifacts (generated by .github/workflows/quality-advisory.yml, and by anyone
+# reproducing those jobs locally). None of these were ignored before, which mattered: the C901 delta
+# inputs are ruff JSON carrying ABSOLUTE local paths, so a local `git add -A` would stage a home
+# directory path straight into a commit -- exactly what scripts/security/scan_forbidden.py fires on.
+coverage.xml
+.coverage
+diff-cover.md
+jscpd-report/
+.mutmut-cache
+mutants/
+mutmut-run.txt
+mutmut-results.txt
+c901-head.json
+c901-base.json
+base-tree/
+
 # Claude Code: settings.json is shared/tracked; settings.local.json is machine-local (never commit)
 .claude/settings.local.json
 

{messagefoundry-0.3.1 → messagefoundry-0.3.2}/CHANGELOG.md

@@ -6,6 +6,37 @@ All notable changes to MessageFoundry are documented here. The format follows
 
 ## [Unreleased]
 
+## [0.3.2] — 2026-07-28 — Early Access
+
+A patch release for one adopter-facing defect shipped in 0.3.1, plus two gates that were passing
+without being able to fail.
+
+### Fixed
+- **The scaffolded supply-chain gate named a repository adopters cannot read.** `messagefoundry init`
+  writes a fail-closed CI gate that runs `gh attestation verify --repo …` on the pinned engine wheel
+  before installing it. It named the retired private development vault rather than the public
+  repository that actually mints the attestations, so **every project scaffolded by 0.3.1 shipped a
+  provenance gate that fails on its owner's first CI run.** If you scaffolded against 0.3.1, either
+  re-run `messagefoundry init`, or edit that one `--repo` argument in
+  `.github/workflows/check.yml` to `MEFORORG/MessageFoundry`; setting the repository variable
+  `MEFOR_VERIFY_ENGINE=off` skips the job entirely as a stopgap. The scaffold test had pinned the
+  wrong value, so the defect was being actively enforced; it now also pins the negative.
+- **The weekly vulnerability-metrics job measured an empty window instead of failing.**
+  `vuln-metrics.yml` invokes `scripts/security/vuln_metrics.py` with no `--repo`, so the argparse
+  default silently decided what was measured — and it named the same retired vault, whose Dependabot
+  PRs a public token cannot read. All seven KPIs were computed over zero pull requests rather than
+  erroring. The default is now `$GITHUB_REPOSITORY`, so the job measures the repository it runs in.
+- **A partially-failed release could not be retried.** The GitHub release step failed when the tag or
+  release already existed, so a publish that died midway (as 0.3.0's did) left no clean path forward.
+  It is now idempotent.
+- **The load harness's no-loss reconcile false-failed a demonstrably zero-loss run.** It excuses a
+  send left unconfirmed at connection teardown, capped so a dead ACK path cannot pass as zero-loss —
+  but the cap modelled legitimate stranding as "~one in-flight frame per connection". The sender
+  keeps an unbounded in-flight window and paces open-loop sends by offered rate, so real stranding
+  scales with rate × ACK-latency instead. A run that stranded 14 of 90 sends while the engine read
+  and delivered every one of the rest was reported as message loss. The cap is now
+  `max(connections, half the run)`, which keeps `read >= sent // 2` always required.
+
 ## [0.3.1] — 2026-07-27 — Early Access
 
 ### Security
@@ -84,6 +115,14 @@ All notable changes to MessageFoundry are documented here. The format follows
   ON). Residuals in [SERVICE.md](docs/SERVICE.md).
 
 ### Fixed
+- **The harness message list could livelock and stop updating entirely.** `MessagesPanel._apply` cleared
+  its in-flight guard, re-fired any refresh latched during the read, then returned *before* rendering —
+  discarding the snapshot as superseded. Whenever refreshes arrive faster than a read completes there is
+  always a latch waiting when the read lands, so every snapshot was discarded and the table never
+  updated: permanently stuck, not merely slow (measured: 391 reads served, 0 rendered). It now renders
+  first and drains afterwards, costing at most one read of staleness while still converging on the
+  latest filter. This surfaced as an intermittent CI failure that no timeout or retry could fix, because
+  neither addresses a livelock.
 - **Two config blocks in the off-loopback runbook aborted at load** — `[diagnostics].audit_all_authz` and
   `[ai].data_class` had been relocated by ADR 0118, so an operator copy-pasting either block got an
   immediate start failure. Corrected to `[security].audit_all_authorization_decisions` and
@@ -956,7 +995,8 @@ tests, but the external code review + penetration test (the bar for a security-c
 - Releases are built, SBOM'd (CycloneDX), and signed with [Sigstore](https://www.sigstore.dev/) — see the
   `release` workflow.
 
-[Unreleased]: https://github.com/MEFORORG/MessageFoundry/compare/v0.3.1...HEAD
+[Unreleased]: https://github.com/MEFORORG/MessageFoundry/compare/v0.3.2...HEAD
+[0.3.2]: https://github.com/MEFORORG/MessageFoundry/compare/v0.3.1...v0.3.2
 [0.3.1]: https://github.com/MEFORORG/MessageFoundry/compare/v0.3.0...v0.3.1
 [0.3.0]: https://github.com/MEFORORG/MessageFoundry/compare/v0.2.15...v0.3.0
 [0.2.15]: https://github.com/MEFORORG/MessageFoundry/compare/v0.2.14...v0.2.15

{messagefoundry-0.3.1 → messagefoundry-0.3.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: messagefoundry
-Version: 0.3.1
+Version: 0.3.2
 Summary: Open-source healthcare integration engine — route, transform, and validate messages across many formats and connection types
 Project-URL: Homepage, https://messagefoundry.org/
 Project-URL: Documentation, https://messagefoundry.org/

{messagefoundry-0.3.1 → messagefoundry-0.3.2}/messagefoundry/__init__.py

@@ -107,7 +107,7 @@ from messagefoundry.timezone import (
     to_zone,
 )
 
-__version__ = "0.3.1"
+__version__ = "0.3.2"
 
 __all__ = [
     "Message",

{messagefoundry-0.3.1 → messagefoundry-0.3.2}/messagefoundry/scaffold.py

@@ -162,7 +162,7 @@ jobs:
       - name: Verify SLSA build provenance before install
         env:
           GH_TOKEN: ${{ github.token }}
-        run: gh attestation verify dist-verify/messagefoundry-*.whl --repo wshallwshall/MessageFoundry
+        run: gh attestation verify dist-verify/messagefoundry-*.whl --repo MEFORORG/MessageFoundry
 
   check:
     needs: verify-engine