v0.15.0

Deploying

Three supported paths — see docs/deployment.md. The short
version: use waxwing-stalwart-v0.15.0.zip for a Stalwart
Application (recommended, same-origin, no CORS), and
waxwing-web-v0.15.0.tar.gz behind your own web server.

Verify what you downloaded before deploying it. The two checks answer different
questions and the second is the stronger one:

# Did the file survive the network and the hoster intact?
# (--ignore-missing: SHA256SUMS lists all three artefacts, you downloaded one.)
sha256sum -c SHA256SUMS --ignore-missing

# Was it built by this repository's release workflow, from THIS TAG?
# (SHA256SUMS cannot answer that: anyone who can replace the zip can regenerate it.
#  --source-ref is required: without it a build from any branch of this repository
#  passes too, and this workflow makes those deliberately as rehearsals.)
gh attestation verify waxwing-stalwart-v0.15.0.zip \
  --repo Heiko-W/waxwing \
  --source-ref refs/tags/v0.15.0

Configuration lives in config.json next to index.html and needs no rebuild —
docs/configuration.md is the reference.

What's Changed

• feat(web): redesign the logo as a constructed single-contour mark by @Heiko-W in #31
• fix(web): the 58 findings from the 2026-08-21 UI walkthrough by @Heiko-W in #32
• fix: die 67 Befunde der JMAP-Lückenanalyse by @Heiko-W in #34
• docs: JMAP-Lückenanalyse — was Stalwart anbietet und Waxwing noch nicht nutzt by @Heiko-W in #33

Full Changelog: v0.14.0...v0.15.0