messagefoundry 0.2.5__tar.gz → 0.2.7__tar.gz

{messagefoundry-0.2.5 → messagefoundry-0.2.7}/.gitattributes

@@ -2,3 +2,4 @@
 # `git diff --exit-code`) can't be tripped by Windows CRLF drift (DEP-1).
 uv.lock text eol=lf
 requirements.lock text eol=lf
+.mefor-hooks/** text eol=lf

{messagefoundry-0.2.5 → messagefoundry-0.2.7}/.github/dependabot.yml

@@ -18,7 +18,10 @@ updates:
     # behavior), so a real advisory fix still arrives immediately. Pairs with the auto-merge
     # workflow: routine patches auto-merge AFTER aging; security patches auto-merge now.
     cooldown:
-      default-days: 3
+      # ~5-day aging window (DEPENDENCY-POSTURE-REVIEW.md) lengthens the malicious-fresh-publish
+      # dodge on the routine VERSION track; the SECURITY track still bypasses cooldown (Dependabot
+      # design), now backstopped by the published-GHSA gate in dependabot-auto-merge.yml (SEC-007 #2).
+      default-days: 5
       semver-major-days: 7
     groups:
       # Version-update grouping (applies-to defaults to version-updates).

messagefoundry-0.2.7/.github/workflows/dependabot-auto-merge.yml

@@ -0,0 +1,165 @@
+name: Dependabot auto-merge
+
+# Scoped auto-merge for Dependabot PRs (A4 of the dependency fast-response plan).
+#
+# SAFE because main's required status checks are the gate: the full pytest suite, pip-audit, the
+# DEP-1 lock-sync check (incl. the A3 lock-resync commit), bandit/semgrep/gitleaks all must pass
+# before GitHub completes the merge. A bad bump turns CI red and never merges — auto-merge only
+# removes the human-latency on the safe, common case, not the safety net.
+#
+# IN SCOPE (auto-merged):
+#   - any PATCH update (incl. security patches — most security fixes are patches)
+#   - MINOR updates of DEV-only dependencies
+# OUT OF SCOPE (left for human review, surfaced same-day by the daily security cron + alerts):
+#   - MINOR/MAJOR updates of runtime deps, and ALL MAJOR updates
+#
+# Fresh-release supply-chain poisoning is handled upstream by the dependabot.yml `cooldown`
+# (routine updates age before a PR opens); SECURITY updates bypass cooldown by design, so a real
+# advisory fix still arrives immediately and (if a patch) auto-merges.
+#
+# SECURITY-TRACK GUARDRAILS (DEPENDENCY-POSTURE-REVIEW.md #2 and #3 — close SEC-007, CWE-829):
+#   #3 DENY-LIST — the auth/token/crypto stack (cryptography, argon2-cffi, fastapi, …) is NEVER
+#      auto-merged, not even for a patch: any such dep routes the PR to MANUAL review. A grouped
+#      PR that includes ANY denied dep is denied WHOLE (fail-safe — never partial-merge a group).
+#   #2 PUBLISHED-GHSA GATE — a SECURITY-track PR (which bypasses the cooldown by Dependabot design)
+#      auto-merges ONLY when a real, published, non-withdrawn advisory is confirmed against the
+#      dependency's PREVIOUS version (the axios-1.14.1 pattern). The advisory lookup FAILS CLOSED:
+#      a rate-limit/API error or no-matching-advisory routes to manual review, never auto-merge.
+#      The non-security VERSION track keeps its cooldown-aged auto-merge unchanged (already aged by
+#      dependabot.yml, so it does not need the GHSA gate).
+#
+# RESIDUAL ACCEPTED RISK: a malicious patch that BOTH rides a real concurrent published advisory
+# AND is not on the deny-list would still auto-merge. The deny-list shields the highest-value
+# (auth/crypto) deps unconditionally; the GHSA gate blocks the no-advisory fast-publish poison on
+# the security track; main's required CI (pip-audit/bandit/tests/lock-sync) backstops both.
+#
+# Why `pull_request` (not pull_request_target): a Dependabot `pull_request` run gets a read-only
+# GITHUB_TOKEN by default, which the `permissions:` block below elevates to exactly what the merge
+# API needs — no untrusted-code-with-secrets exposure, no GitHub App required. This is the pattern
+# GitHub documents for Dependabot auto-merge.
+
+on: pull_request
+
+permissions:
+  contents: write # complete the merge
+  pull-requests: write # enable auto-merge on the PR
+  security-events: read # read Dependabot alerts for the published-GHSA gate (#2)
+
+concurrency:
+  group: dependabot-automerge-${{ github.event.pull_request.number }}
+  cancel-in-progress: false
+
+jobs:
+  auto-merge:
+    runs-on: ubuntu-latest
+    # Only Dependabot's own PRs. pull_request.user.login is the immutable PR author, so an A3
+    # lock-resync `synchronize` (pushed by the App) still satisfies this — the author stays
+    # dependabot[bot] even though the triggering actor is the App.
+    if: github.event.pull_request.user.login == 'dependabot[bot]'
+    timeout-minutes: 10
+    steps:
+      - name: Fetch Dependabot metadata
+        id: meta
+        uses: dependabot/fetch-metadata@25dd0e34f4fe68f24cc83900b1fe3fe149efef98 # v3.1.0
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+
+      # Guardrail #3 (DEPENDENCY-POSTURE-REVIEW.md): the auth/token/crypto stack NEVER auto-merges,
+      # not even a patch. dependency-names is comma-separated for grouped PRs; we deny the WHOLE
+      # group if ANY token matches (fail-safe — never partial-merge a group). Exact token match on
+      # the comma-split names (not a naive substring) so 'cffi' does not match 'argon2-cffi-bindings'
+      # and vice-versa.
+      - name: Reject security-critical deps (deny-list)
+        id: denylist
+        env:
+          DEP_NAMES: ${{ steps.meta.outputs.dependency-names }}
+        run: |
+          # Single source of truth for the security-critical deny-list.
+          denylist="cryptography argon2-cffi argon2-cffi-bindings paramiko ldap3 pyspnego \
+            fastapi starlette uvicorn pydantic pydantic-core python-jose pyjwt passlib bcrypt cffi"
+          deny=false
+          IFS=',' read -ra names <<< "$DEP_NAMES"
+          for raw in "${names[@]}"; do
+            # trim surrounding whitespace and lowercase
+            name="$(echo "$raw" | tr '[:upper:]' '[:lower:]' | xargs)"
+            [ -z "$name" ] && continue
+            for crit in $denylist; do
+              if [ "$name" = "$crit" ]; then
+                echo "::notice::'$name' is a security-critical dependency — routing to manual review (no auto-merge)."
+                deny=true
+              fi
+            done
+          done
+          echo "deny=$deny" >> "$GITHUB_OUTPUT"
+
+      # Guardrail #2 (DEPENDENCY-POSTURE-REVIEW.md): a SECURITY-track PR auto-merges ONLY when a
+      # real, published, non-withdrawn advisory covers the dependency's PREVIOUS version. The
+      # security track is detected by Dependabot's `dependency-group` (python-security/ide-security)
+      # — a security-update group — falling back to a present-but-empty group meaning version track.
+      # The advisory lookup FAILS CLOSED: any error or no-match leaves advisory_ok=false.
+      - name: Verify a published advisory backs the security track
+        id: ghsa
+        env:
+          DEP_NAMES: ${{ steps.meta.outputs.dependency-names }}
+          DEP_GROUP: ${{ steps.meta.outputs.dependency-group }}
+          PREV_VERSION: ${{ steps.meta.outputs.previous-version }}
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          set -u
+          # Is this the security track? Dependabot tags security-update grouped PRs with a
+          # *-security dependency-group. A non-security (version) PR has no security group.
+          is_security=false
+          case "$DEP_GROUP" in
+            *security*) is_security=true ;;
+          esac
+
+          if [ "$is_security" != "true" ]; then
+            # Version track: already cooldown-aged by dependabot.yml — the GHSA gate does not apply.
+            echo "security_track=false" >> "$GITHUB_OUTPUT"
+            echo "advisory_ok=false" >> "$GITHUB_OUTPUT"
+            exit 0
+          fi
+          echo "security_track=true" >> "$GITHUB_OUTPUT"
+
+          # Require at least one matching published (non-withdrawn) advisory for EVERY named dep at
+          # the previous version. Query the global advisories endpoint (ecosystem pip — Python
+          # advisories are pip-keyed). Fail closed on any error.
+          advisory_ok=true
+          IFS=',' read -ra names <<< "$DEP_NAMES"
+          for raw in "${names[@]}"; do
+            name="$(echo "$raw" | tr '[:upper:]' '[:lower:]' | xargs)"
+            [ -z "$name" ] && continue
+            count="$(gh api -X GET /advisories \
+              -f ecosystem=pip \
+              -f affects="${name}@${PREV_VERSION}" \
+              --jq '[.[] | select(.withdrawn_at == null)] | length' 2>/dev/null || echo "ERR")"
+            if [ "$count" = "ERR" ] || [ -z "$count" ]; then
+              echo "::warning::advisory lookup failed for '$name' — failing closed (manual review)."
+              advisory_ok=false
+              break
+            fi
+            if [ "$count" -lt 1 ]; then
+              echo "::warning::no published advisory covers '${name}@${PREV_VERSION}' — failing closed (manual review)."
+              advisory_ok=false
+              break
+            fi
+            echo "::notice::published advisory confirmed for '${name}@${PREV_VERSION}'."
+          done
+          echo "advisory_ok=$advisory_ok" >> "$GITHUB_OUTPUT"
+
+      - name: Enable auto-merge for in-scope updates
+        # Auto-merge only when: (a) the update is an in-scope type (any patch, or a dev-only minor),
+        # AND (b) no security-critical dep is involved (deny-list #3), AND (c) for the SECURITY track
+        # ONLY, a published advisory is confirmed (#2). A non-security (version-track) patch keeps its
+        # cooldown-aged auto-merge — advisory_ok is not required there.
+        if: >-
+          steps.denylist.outputs.deny != 'true' &&
+          (steps.ghsa.outputs.security_track != 'true' ||
+           steps.ghsa.outputs.advisory_ok == 'true') &&
+          (steps.meta.outputs.update-type == 'version-update:semver-patch' ||
+           (steps.meta.outputs.update-type == 'version-update:semver-minor' &&
+            steps.meta.outputs.dependency-type == 'direct:development'))
+        run: gh pr merge --auto --squash "$PR_URL"
+        env:
+          PR_URL: ${{ github.event.pull_request.html_url }}
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

messagefoundry-0.2.7/.github/workflows/freethread-smoke.yml

@@ -0,0 +1,95 @@
+# Free-threaded (no-GIL / PEP 703, cp314t) engine canary — INFORMATIONAL, NEVER BLOCKING.
+#
+# This is an EXPLORATORY signal (see docs/design/freethread.md), not a supported config. The engine
+# ships on the GIL build; this leg only tells us, on a weekly schedule, whether the engine still
+# installs + imports + smoke-tests under the free-threaded 3.14t interpreter, so a regression in a
+# dependency's cp314t wheel surfaces early. It is an early-warning tripwire, not a per-PR gate —
+# hence weekly (+ manual dispatch), not on every push/PR.
+#
+# IT MUST NEVER BLOCK A MERGE:
+#   * It is a SEPARATE workflow, deliberately not part of ci.yml's `ci-gate` (the required "CI gate"
+#     context). It is not in any `needs:` list a PR waits on.
+#   * The job AND its fragile steps are `continue-on-error: true`, so a red canary is an informational
+#     red check, never a failed required one.
+#   * DO NOT add the "freethread smoke (3.14t)" context to branch-protection required checks. The
+#     required set is the `test` matrix + bandit + pip-audit + cla — keep it that way.
+#
+# If actions/setup-python ever cannot provision 3.14t on the runner, the continue-on-error job simply
+# goes red as information; nothing downstream is gated on it.
+
+name: freethread smoke
+
+on:
+  # Weekly early-warning tripwire (Mondays 06:00 UTC) + manual dispatch. NOT per-PR/per-push: this is
+  # an informational cp314t-readiness signal, not a gate, so it doesn't need to run on every change.
+  schedule:
+    - cron: "0 6 * * 1"
+  workflow_dispatch:
+
+concurrency:
+  group: freethread-${{ github.ref }}
+  cancel-in-progress: true
+
+# Read-only: install deps + run a pure test subset. No gh writes, no secrets.
+permissions:
+  contents: read
+
+jobs:
+  freethread:
+    name: freethread smoke (3.14t)
+    # The whole job is non-blocking: a failure here is reported but never fails the workflow's
+    # required-context resolution, so it cannot block a PR even if it is ever (mis)added to protection.
+    continue-on-error: true
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    steps:
+      - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+        with:
+          persist-credentials: false # read-only smoke job; don't persist the token (zizmor: artipacked)
+
+      # Provision the FREE-THREADED 3.14 interpreter (distinct cp314t ABI). `freethreaded: true` +
+      # the `t` suffix both select it; allow-prereleases covers the 3.14 line. This step is allowed to
+      # fail (continue-on-error) so a runner that cannot yet provide 3.14t never reds a blocking check.
+      - name: Set up free-threaded Python 3.14t
+        id: setup
+        continue-on-error: true
+        uses: actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405 # v6
+        with:
+          python-version: "3.14t"
+          freethreaded: true
+          allow-prereleases: true
+
+      # Install the CORE engine only (no Qt/SQL/DICOM/SFTP extras), so the smoke exercises the minimal
+      # free-threaded-relevant compiled surface: pydantic-core, cryptography, and the argon2-cffi + cffi
+      # chain. --prerelease handling: pip resolves the cp314t wheels; the cffi 2.0 chain may need a
+      # prerelease allowance depending on the index state at run time.
+      - name: Install the core engine (dev extra; no compiled-heavy extras)
+        if: steps.setup.outcome == 'success'
+        continue-on-error: true
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+
+      # Prove we are actually on the no-GIL interpreter — an incompatible C extension importing can make
+      # CPython silently RE-ENABLE the GIL, which would make a "green" canary meaningless. Fail (softly)
+      # if the GIL is back on.
+      - name: Assert the GIL is actually disabled
+        if: steps.setup.outcome == 'success'
+        continue-on-error: true
+        run: |
+          python - <<'PY'
+          import sys
+          gil_on = sys._is_gil_enabled()
+          print(f"sys._is_gil_enabled() = {gil_on}")
+          print(f"sys.version = {sys.version}")
+          if gil_on:
+              raise SystemExit("GIL is ENABLED on the 3.14t build — an extension likely forced it back on")
+          PY
+
+      # Run a PURE, fast subset under 3.14t: parsing (pure HL7 library) + config wiring. This is the
+      # cheap install-and-import + smoke signal, NOT the perf experiment (that lives in the load harness,
+      # run manually — see docs/LOAD-TESTING.md / docs/design/freethread.md §4).
+      - name: Smoke a pure test subset under 3.14t
+        if: steps.setup.outcome == 'success'
+        continue-on-error: true
+        run: pytest -q tests/test_parsing.py tests/test_wiring.py

{messagefoundry-0.2.5 → messagefoundry-0.2.7}/.github/workflows/release.yml

@@ -54,6 +54,21 @@ jobs:
         with:
           python-version: "3.14"
 
+      - name: Rewrite README repo slug for the public PyPI long_description
+        run: |
+          # PyPI renders README.md (pyproject `readme = "README.md"`) as the project description and
+          # fetches it anonymously. The source README points at the PRIVATE source repo
+          # (wshallwshall/MessageFoundry) so the team's GitHub view shows the private repo's own CI
+          # badges — but anonymous fetches of a private repo's Actions badge SVG 404 (broken badge
+          # images), and every body link 404s on click. The public mirror (MEFORORG/MessageFoundry)
+          # runs the same workflows and is anonymously reachable, so rewrite the slug here (the same
+          # rewrite scripts/publish/publish.ps1 applies to the mirror) before `python -m build` embeds
+          # the README. Ephemeral runner edit only — never committed.
+          sed -i 's#wshallwshall/MessageFoundry#MEFORORG/MessageFoundry#g' README.md
+          if grep -q 'wshallwshall/MessageFoundry' README.md; then
+            echo '::error::README slug rewrite left private-repo links'; exit 1
+          fi
+
       - name: Build sdist + wheel
         run: |
           python -m pip install --upgrade pip build
@@ -117,7 +132,7 @@ jobs:
       # `github.event.repository.private` is populated on the tag-push event.
       - name: Attest build provenance (SLSA) for sdist + wheel
         if: ${{ !github.event.repository.private }}
-        uses: actions/attest-build-provenance@a2bbfa25375fe432b6a289bc6b6cd05ecd0c4c32 # v4.1.0
+        uses: actions/attest-build-provenance@0f67c3f4856b2e3261c31976d6725780e5e4c373 # v4.1.1
         with:
           subject-path: "dist/*.tar.gz, dist/*.whl"
 

{messagefoundry-0.2.5 → messagefoundry-0.2.7}/.gitignore

@@ -80,3 +80,8 @@ TRANSCRIPTS.md
 # Still usable by name (they sit in PROFILES_DIR) and copy-on to the test box.
 /harness/load/profiles/hospital-baseline.toml
 /harness/load/profiles/soak-12h.toml
+# --- MessageFoundry ---
+.mefor/
+*.db*
+.DS_Store
+Thumbs.db

messagefoundry-0.2.7/.mefor-hooks/pre-commit

@@ -0,0 +1,25 @@
+#!/bin/sh
+# MessageFoundry pre-commit checks — generated by the VS Code extension.
+# Runs `messagefoundry check` so a commit can't introduce a broken config.
+# Bypass once with: git commit --no-verify
+
+PY=python
+command -v python >/dev/null 2>&1 || PY=python3
+if ! command -v "$PY" >/dev/null 2>&1; then
+  echo "MessageFoundry: python not found; skipping checks." >&2
+  exit 0
+fi
+
+# Prefer a project virtualenv if present (Windows + POSIX layouts).
+if [ -x ".venv/Scripts/python.exe" ]; then
+  PY=".venv/Scripts/python.exe"
+elif [ -x ".venv/bin/python" ]; then
+  PY=".venv/bin/python"
+fi
+
+if ! "$PY" -c "import messagefoundry" >/dev/null 2>&1; then
+  echo "MessageFoundry: 'messagefoundry' not importable in this environment; skipping checks." >&2
+  exit 0
+fi
+
+exec "$PY" -m messagefoundry check --config 'samples/config' --messages 'samples/messages'

{messagefoundry-0.2.5 → messagefoundry-0.2.7}/CHANGELOG.md

@@ -6,6 +6,102 @@ All notable changes to MessageFoundry are documented here. The format follows
 
 ## [Unreleased]
 
+## [0.2.7] — 2026-06-27 — Early Access
+
+A docs/packaging release that fixes the broken badge images on the PyPI project page
+and adds a config-check pre-commit hook.
+
+### Fixed
+- **Broken badge images in the PyPI project description.** The CI and Security status
+  badges in the README pointed at the **private** source repo, so they rendered as
+  broken images on the public PyPI page — an anonymous viewer can't fetch a private
+  repo's GitHub Actions badge SVG (it 404s). The README now points at the public
+  mirror (`MEFORORG/MessageFoundry`), and the release build additionally rewrites any
+  remaining `wshallwshall`→`MEFORORG` repo slug in the README before it is embedded as
+  the PyPI `long_description`, so the rendered badges resolve anonymously. (#568)
+
+### Added
+- **`messagefoundry check` pre-commit hook.** A VS Code-extension-generated
+  `.mefor-hooks/pre-commit` runs `messagefoundry check` so a commit can't introduce a
+  broken config (skips cleanly if python or the package isn't importable; bypass with
+  `--no-verify`). (#568)
+
+### Docs
+- Backlog **#47** — base64 embedded-document (attachment) pruning (Mirth
+  attachment-handler / data-pruner parity); and a Changelog link in the README. (#568)
+
+## [0.2.6] — 2026-06-27 — Early Access
+
+A large release: the **throughput-maximization build** (high-fan-out store-once, multi-process
+sharding, and internal pass-through connectors with full Postgres/SQL Server parity), a console +
+IDE **"fleet" tier** for managing multiple engine shards, and a broad **security-hardening wave**
+from the 2026-06 audit.
+
+### Added
+- **Multi-process sharding (L3).** An inbound connection can carry an optional `shard` tag;
+  `serve --shard <id>` runs an engine process that owns only that shard's inbound connections
+  (outbound + routing/handlers are shared), and a new `supervise` command spawns, monitors, and
+  restarts one `serve` subprocess per shard (each with its own SQLite db file and API port).
+  Per-connection sharding parallelizes intake across CPU cores; per-channel FIFO is preserved
+  within a shard. (#584)
+- **Internal pass-through (PT) connectors (L4).** A Handler may `Send` into an internal
+  `PassThrough()` inbound that carries its own router; the message re-ingresses as a new
+  content-addressed child message inside the same transaction (at-least-once, count-and-log, and
+  single-finalizer authority all preserved), bounded by a correlation-depth loop guard. This
+  generalizes the ADR 0013 re-ingress primitive. Implemented on **all three store backends** —
+  SQLite, plus full **Postgres and SQL Server parity** for the atomic re-ingress. (#585, #590)
+- **Store-once-deliver-many (L2b).** A high-fan-out outbound now stores the message body **once**
+  (content-addressed, reference-counted `shared_body`) instead of once per destination;
+  single-destination delivery is unchanged (inline, byte-identical). (#580)
+- **Fleet tier — manage multiple engine shards.** The console can register and switch between
+  multiple engine endpoints (#582); the IDE promote flow can target a specific engine
+  instance/shard (#583).
+- **IDE editor productivity.** A MessageFoundry build toolbar + CodeLens on config files (#593),
+  an "Insert Element" quick-pick with expanded transform-idiom snippets (#595), a Wizards group
+  with collapsible Home groups (#578), and a `vsce` VSIX packaging script (#577).
+- **Config-fingerprint attestation.** Config reloads record a config fingerprint in the reload
+  audit (ADR 0041 load-path attestation). (#597)
+
+### Changed
+- **Faster fan-out.** On a fan-out the engine parses the per-message payload once where it is
+  value-identical, avoiding redundant re-parsing. (#581)
+
+### Fixed
+- **Fail-fast pass-through guard.** A graph with a PT inbound on a store backend that does not
+  implement PT re-ingress is now rejected at startup *and* on reload/dry-run (a clear configuration
+  error, HTTP 422) — before any listener binds — instead of failing at the first `Send`. (#587)
+- **Auth hardening.** Tighter field-level authorization, a last-admin guard, a corrected TOTP
+  window, and rate-limit documentation fixes. (#563)
+- **API / store.** Channel-scoped event and topology reads, faster WebSocket session revocation,
+  and atomic bootstrap-secret creation. (#565)
+- **IDE.** Workspace-trust gating, machine-scoped promote targets, and a fail-closed AI-assist
+  policy (SEC-004/005/022). (#561)
+
+### Security
+The 2026-06 security-audit remediation wave (in-repo remediation ledger, #566):
+- **Transport TLS / SSRF / injection:** FTPS TLS verification, an FHIR-path SSRF guard, and
+  read-only enforcement on `db_lookup` (SEC-001/010/009). (#560)
+- **Listener hardening:** a cleartext-bind guard plus source-IP allowlist for the raw-TCP/X12
+  listeners. (#558)
+- **DICOM:** fail-closed C-STORE SCP peer controls (calling-AE + peer-IP) and a passphrase-key
+  callback (SEC-012/016). (#559)
+- **Pipeline:** off-event-loop router/transform execution and a non-HL7 ingress size cap
+  (SEC-013/017). (#562)
+- **Config trust:** enforce Windows config-source trust and scope the sibling-helper finder
+  (SEC-003/019). (#564)
+- **PHI redaction:** narrowed a free-text PHI residual and added an advisory raise-fstring lint
+  (SEC-023). (#557)
+- **Supply chain:** Dependabot security-track guardrails and adopter-scaffold hash-pinning. (#556)
+- **Static analysis:** resolved two real CodeQL findings (webview HTML attribute escaping;
+  owner-only file-delivery fallback) (#554) and adopted a CodeQL triage policy + accepted-risk
+  register (ADR 0034). (#567)
+
+### Docs
+- ADRs 0037–0040 record the throughput-build decisions (multi-process sharding, pass-through
+  connectors, the shelved L5 DB-sharding design, and the not-adopted free-threading assessment)
+  (#591); design notes for L5 DB-sharding (#588) and cp314t readiness (#589); and the Secure
+  AI-Assisted Development Standards updated with the audit lessons (#576).
+
 ## [0.2.5] — 2026-06-26 — Early Access
 
 A bug-fix release hardening SQL Server cluster cold-start.
@@ -203,7 +299,9 @@ 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/wshallwshall/MessageFoundry/compare/v0.2.5...HEAD
+[Unreleased]: https://github.com/wshallwshall/MessageFoundry/compare/v0.2.7...HEAD
+[0.2.7]: https://github.com/wshallwshall/MessageFoundry/compare/v0.2.6...v0.2.7
+[0.2.6]: https://github.com/wshallwshall/MessageFoundry/compare/v0.2.5...v0.2.6
 [0.2.5]: https://github.com/wshallwshall/MessageFoundry/compare/v0.2.4...v0.2.5
 [0.2.4]: https://github.com/wshallwshall/MessageFoundry/compare/v0.2.3...v0.2.4
 [0.2.3]: https://github.com/wshallwshall/MessageFoundry/compare/v0.2.2...v0.2.3

{messagefoundry-0.2.5 → messagefoundry-0.2.7}/PKG-INFO

@@ -1,7 +1,11 @@
 Metadata-Version: 2.4
 Name: messagefoundry
-Version: 0.2.5
+Version: 0.2.7
 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/
+Project-URL: Repository, https://github.com/MEFORORG/MessageFoundry
+Project-URL: Issues, https://github.com/MEFORORG/MessageFoundry/issues
 License-Expression: AGPL-3.0-or-later
 License-File: LICENSE
 License-File: NOTICE
@@ -66,10 +70,13 @@ Description-Content-Type: text/markdown
 
 # MessageFoundry
 
-[![CI](https://github.com/wshallwshall/MessageFoundry/actions/workflows/ci.yml/badge.svg)](https://github.com/wshallwshall/MessageFoundry/actions/workflows/ci.yml)
-[![Security](https://github.com/wshallwshall/MessageFoundry/actions/workflows/security.yml/badge.svg)](https://github.com/wshallwshall/MessageFoundry/actions/workflows/security.yml)
-[![License: AGPL v3](https://img.shields.io/badge/License-AGPL_v3-blue.svg)](https://github.com/wshallwshall/MessageFoundry/blob/main/LICENSE)
-[![Python 3.14+](https://img.shields.io/badge/python-3.14%2B-blue.svg)](https://github.com/wshallwshall/MessageFoundry/blob/main/pyproject.toml)
+[![CI](https://github.com/MEFORORG/MessageFoundry/actions/workflows/ci.yml/badge.svg)](https://github.com/MEFORORG/MessageFoundry/actions/workflows/ci.yml)
+[![Security](https://github.com/MEFORORG/MessageFoundry/actions/workflows/security.yml/badge.svg)](https://github.com/MEFORORG/MessageFoundry/actions/workflows/security.yml)
+[![License: AGPL v3](https://img.shields.io/badge/License-AGPL_v3-blue.svg)](https://github.com/MEFORORG/MessageFoundry/blob/main/LICENSE)
+[![Python 3.14+](https://img.shields.io/badge/python-3.14%2B-blue.svg)](https://github.com/MEFORORG/MessageFoundry/blob/main/pyproject.toml)
+
+**Website & documentation: [messagefoundry.org](https://messagefoundry.org/)** ·
+**[Changelog](https://github.com/MEFORORG/MessageFoundry/blob/main/CHANGELOG.md)**
 
 MessageFoundry is an **open-source healthcare integration engine** — a modern, Python-native HL7
 interface engine. It connects clinical and business systems by routing, transforming, and validating
@@ -96,10 +103,10 @@ The PySide6 console talks to it over a localhost HTTP + WebSocket API — the sa
 whether the engine runs in-process, as a local daemon, or (later) on a remote host.
 No hand-rolled IPC; the deployment split is a config choice, not an architectural fork.
 
-See **[docs/architecture-diagram.md](https://github.com/wshallwshall/MessageFoundry/blob/main/docs/architecture-diagram.md)** for the rendered diagrams —
+See **[docs/architecture-diagram.md](https://github.com/MEFORORG/MessageFoundry/blob/main/docs/architecture-diagram.md)** for the rendered diagrams —
 system topology, runtime message flow through the staged queue, and the config wiring graph (Mermaid,
 renders on GitHub and in the VS Code preview). The prose source of truth is
-[docs/ARCHITECTURE.md](https://github.com/wshallwshall/MessageFoundry/blob/main/docs/ARCHITECTURE.md).
+[docs/ARCHITECTURE.md](https://github.com/MEFORORG/MessageFoundry/blob/main/docs/ARCHITECTURE.md).
 
 ### Key decisions
 - **Reliable by default.** A durable, transactional pipeline gives at-least-once delivery,
@@ -113,7 +120,7 @@ renders on GitHub and in the VS Code preview). The prose source of truth is
 - **PHI is first-class.** Authentication, RBAC, a user-attributed audit log of message
   views/replays, **encryption-at-rest** for message bodies (AES-256-GCM), **global PHI log redaction**,
   and **transport TLS** (HTTPS/WSS for the API plus MLLP-over-TLS) are **built**; MFA and off-box log
-  shipping remain on the roadmap. See [docs/PHI.md](https://github.com/wshallwshall/MessageFoundry/blob/main/docs/PHI.md) for the full data-protection map.
+  shipping remain on the roadmap. See [docs/PHI.md](https://github.com/MEFORORG/MessageFoundry/blob/main/docs/PHI.md) for the full data-protection map.
 
 ## Features
 
@@ -132,9 +139,9 @@ transport TLS — and it runs single-node or in active-passive high availability
 
 Full documentation lives on **[messagefoundry.org](https://messagefoundry.org/)**:
 
-- **[Mental map](https://messagefoundry.org/assets/docs/MessageFoundry-Mental-Model.pdf)** — a one-page
-  picture of how the pieces fit: Connections → Router → Handlers → Connections, with the headless
-  engine and the console/IDE that drive it.
+- **[Mental map](https://messagefoundry.org/assets/docs/MessageFoundry-Mental-Model.pdf)** — an
+  orientation guide to how the pieces fit: Connections → Router → Handlers → Connections, with the
+  headless engine and the console/IDE that drive it.
 - **[Install Guide](https://messagefoundry.org/assets/docs/MessageFoundry-Install-Guide.pdf)** — install,
   configure, secure, and roll out to production.
 - **[User Guide](https://messagefoundry.org/assets/docs/MessageFoundry-User-Guide.pdf)** — author and
@@ -149,7 +156,7 @@ Full documentation lives on **[messagefoundry.org](https://messagefoundry.org/)*
 **The recommended way to deploy MessageFoundry is to install the published package from
 [PyPI](https://pypi.org/project/messagefoundry/)** — a signed, version-pinned wheel is the
 supported production artifact, with no source checkout required. Install it as a **pinned
-dependency**, then scaffold your own config repo ([ADR 0017](https://github.com/wshallwshall/MessageFoundry/blob/main/docs/adr/0017-consumer-deployment-model.md)):
+dependency**, then scaffold your own config repo ([ADR 0017](https://github.com/MEFORORG/MessageFoundry/blob/main/docs/adr/0017-consumer-deployment-model.md)):
 
 ```bash
 pip install "messagefoundry==<version>"   # pin the exact engine version (core runtime, SQLite store)
@@ -181,8 +188,8 @@ test harness* below for where to get it.
 > **Verify before you install (supply chain).** Every release is built by a GitHub Actions workflow,
 > Sigstore-signed, and carries SLSA build-provenance + PEP 740 attestations. Verify a downloaded
 > wheel against its source commit with
-> `gh attestation verify <wheel> --repo wshallwshall/MessageFoundry`, or pull the signed wheel + SBOM
-> from the [GitHub Release assets](https://github.com/wshallwshall/MessageFoundry/releases). For an
+> `gh attestation verify <wheel> --repo MEFORORG/MessageFoundry`, or pull the signed wheel + SBOM
+> from the [GitHub Release assets](https://github.com/MEFORORG/MessageFoundry/releases). For an
 > air-gapped site, mirror the wheel to a private index.
 >
 > *(Engine developers install from a checkout instead — see [Development](#development).)*
@@ -219,14 +226,14 @@ python -m messagefoundry.console --url http://127.0.0.1:8765
 
 ### VS Code extension & test harness
 
-- **VS Code extension** ([`ide/`](https://github.com/wshallwshall/MessageFoundry/tree/main/ide/)) — author and test interfaces in your editor: a New Route
+- **VS Code extension** ([`ide/`](https://github.com/MEFORORG/MessageFoundry/tree/main/ide/)) — author and test interfaces in your editor: a New Route
   Wizard, validate-on-save, a Test Bench (dry-run `.hl7` files with before/after diffs), Stage →
   Promote to a running engine, and an HL7-aware `@messagefoundry` chat participant. **It is not on PyPI**
   (a VS Code extension is a different ecosystem) **and not yet on the VS Code Marketplace** — Marketplace
-  + Open VSX publishing is **planned** (see [the backlog](https://github.com/wshallwshall/MessageFoundry/blob/main/docs/BACKLOG.md)). Until then, get it from
+  + Open VSX publishing is **planned** (see [the backlog](https://github.com/MEFORORG/MessageFoundry/blob/main/docs/BACKLOG.md)). Until then, get it from
   this repo: open the `ide/` folder in VS Code and press **F5** (Extension Development Host), or build the
   VSIX (`cd ide && npm install && npx @vscode/vsce package`) and install the `.vsix`. See
-  [ide/README.md](https://github.com/wshallwshall/MessageFoundry/blob/main/ide/README.md).
+  [ide/README.md](https://github.com/MEFORORG/MessageFoundry/blob/main/ide/README.md).
 - **Test harness** — synthetic-only send/receive (MLLP), load, and failover tooling for exercising a
   running engine. It ships as a **separate distribution, `messagefoundry-harness`**, released in lockstep
   with the engine (it is *not* in the engine wheel): `pip install messagefoundry-harness`, then
@@ -235,14 +242,14 @@ python -m messagefoundry.console --url http://127.0.0.1:8765
 ## License
 
 MessageFoundry is licensed under the **GNU Affero General Public License v3.0 or later**
-(`AGPL-3.0-or-later`) — see [LICENSE](https://github.com/wshallwshall/MessageFoundry/blob/main/LICENSE). Running a modified version as a network service
+(`AGPL-3.0-or-later`) — see [LICENSE](https://github.com/MEFORORG/MessageFoundry/blob/main/LICENSE). Running a modified version as a network service
 triggers the AGPL's §13 source-offer obligation. A separately-licensed commercial edition is planned
 by **MessageFoundry Organization** under the standard open-core model — see
-[COMMERCIAL-LICENSE.md](https://github.com/wshallwshall/MessageFoundry/blob/main/COMMERCIAL-LICENSE.md) (terms pending legal review). See [NOTICE](https://github.com/wshallwshall/MessageFoundry/blob/main/NOTICE)
+[COMMERCIAL-LICENSE.md](https://github.com/MEFORORG/MessageFoundry/blob/main/COMMERCIAL-LICENSE.md) (terms pending legal review). See [NOTICE](https://github.com/MEFORORG/MessageFoundry/blob/main/NOTICE)
 for copyright and attribution.
 
 ## Contributing
 
-Contributions are welcome — see [CONTRIBUTING.md](https://github.com/wshallwshall/MessageFoundry/blob/main/CONTRIBUTING.md), our
-[Code of Conduct](https://github.com/wshallwshall/MessageFoundry/blob/main/CODE_OF_CONDUCT.md), and how the project is governed in [GOVERNANCE.md](https://github.com/wshallwshall/MessageFoundry/blob/main/GOVERNANCE.md).
-A signed [Contributor License Agreement](https://github.com/wshallwshall/MessageFoundry/blob/main/CLA.md) is required before a pull request can be merged.
+Contributions are welcome — see [CONTRIBUTING.md](https://github.com/MEFORORG/MessageFoundry/blob/main/CONTRIBUTING.md), our
+[Code of Conduct](https://github.com/MEFORORG/MessageFoundry/blob/main/CODE_OF_CONDUCT.md), and how the project is governed in [GOVERNANCE.md](https://github.com/MEFORORG/MessageFoundry/blob/main/GOVERNANCE.md).
+A signed [Contributor License Agreement](https://github.com/MEFORORG/MessageFoundry/blob/main/CLA.md) is required before a pull request can be merged.