Changelog

2026-05-11 — Docs upstream legacy-sidecar fallback (v0.3.26)

Hotfix for v0.3.25: production deployments serve /docs/* via a sidecar container at http://localhost:8082; the cloud container itself has no docs/site/ on disk. The v0.3.25 change that flipped the default to filesystem mode broke the prod path. DocsUpstreamClient now picks the right mode at startup:

1. HTTP mode when jengu.docs.upstream-url is set explicitly.
2. Filesystem mode when jengu.docs.local-path exists and has an index.html (typical of a developer workstation that ran preDev).
3. Legacy sidecar fallback (http://localhost:8082) otherwise — restores the pre-v0.3.25 prod behaviour without an env-var change in the deployment.

No customer-visible change in the docs content; just /docs/* coming back online on jengu.cloud.

2026-05-11 — Customer-facing docs pass

End-to-end rewrite of the public documentation site for clarity and customer voice. Platform behaviour is unchanged; what changed is how it reads.

• Principles, in customer voice. The eight architectural principles are reframed as "Our principles" with a hero that says how Jengu builds, not what the architecture diagram looks like. Per-principle bodies tightened: "the edge" introduced plainly before being used, "FHIR project" replaced with plain-English data store, the dense REQ/class-name paragraph in Principle 5 rewritten as a customer-readable claim with the detailed traceability linked to the status page.
• Platform features. The combined "Principles & Capabilities" page is split into Our principles and Platform features. Customer-facing vocabulary unified to Features; the previous "Capability" wording stays only as internal REQ-prefix identifiers and stable URL slugs.
• Module overviews. Jengu Lab and Visit Assistant overview pages each lead with a high-level "what you get / how it fits / what changes" narrative customer-leaders can read in two minutes, with the per-feature drill-down on the sibling Features page.
• Landing page. The site landing now leads with the customer pitch ("Clinical modules are the product. The platform underneath makes them legally and operationally usable.") and the top three reasons to choose Jengu, followed by references to Principles + Features pages rather than enumerating them inline.
• Security pages consolidated. Encrypted fields and Audit catalogue now render inside the documentation shell with a consistent navigation experience for both anonymous visitors and logged-in users. Anonymous viewers see the platform-wide catalogue; logged-in tenants see their resolved set with zone and private-IG overlays applied.
• Implementation status page. Renamed throughout to Feature Implementation Status; copy follows the same vocabulary change.
• Dev ergonomics. :assembly:jengu-cloud:dev now serves the /docs/* static content directly from the working tree's docs/site/ directory — no separate python -m http.server needed. Production deployments override with a configured CDN / static-site upstream.
• Honest scope adjustment: edge fleet management moved from "Not open" to "Open" in Principle 2 — appliance images now ship inside the cloud release, so a self-hosting customer operates their own fleet from their own cloud with no vendor-only tooling in the loop.

2026-05-02 — Public site, MIT license, self-hosting bundle

• Open-source positioning: platform code is now MIT-licensed. LICENSE is at the repository root.
• Self-hosting bundle: deploy/self-host/docker-compose.yml boots Postgres, Redis, Medplum FHIR R4, Temporal (single-node), LiveKit (single-node), and the cloud assembly from ghcr.io/jengu-net/jengu-runtime. A demo hogwarts tenant provisions automatically from the public starter config repo.
• Open-vs-closed line documented: see self-hosting deployment topology. Open: platform code, module repos, build workflows. Not open: release/deploy CI beyond build, monitoring/SLO automation, edge fleet management UI, certified per-zone profile bundles outside zone-ee, support, SLA.
• Public site: introductory site at the platform's hostname under /docs/, available to anonymous visitors and embedded in the cloud shell for logged-in users via a Work / Docs context switcher in the top bar.
• Capability status report: redesigned around a five-segment status bar — Gap → Regressing → Pending → Unknown → Strong — with row tinting by health. Health now reflects what is actually verified by automated tests, not what is merely declared.

(Earlier internal milestones — multi-tenant foundations, JWT cookie auth, Spring Authorization Server, edge image build pipeline, zone architecture, LLM router — are tracked in git history and arc42 documentation. This changelog starts with the first public release.)