v1.3.4: Release notes describe the tag they are published under

Every entry in this file was rewritten to lead with what changed for an operator. Sections
that described something other than the tag they sit under were corrected against the tags
themselves; the corrections are listed below.

No tag was moved and no released code changed. This is a documentation release.

Fixed

• The [1.1.0] section now describes what the v1.1.0 tag shipped. Reconstructed from
  the published release body, which had it right all along, and verified against git diff v1.0.0 v1.1.0: four files, none of them the alert socket. What the section listed before
  is preserved in [1.0.0], where it belongs, marked as predecessor history
• The [1.0.0] section said 18 security layers where the release shipped 24. Counted in
  the tag itself: git show v1.0.0:README.md carries a 24-row layer table, and
  docs/SECURITY_AUDIT_REPORT.md numbers its findings up to SEC-F15. The figure 18 was
  the count before the last hardening round of the predecessor, not the count that shipped
• Both early sections were dated 2026-02-16, which is neither tag date. v1.0.0 is
  tagged 2026-02-19 and v1.1.0 2026-05-30. The headings now carry the tag dates, and the
  three-month gap between the two is no longer hidden behind an identical date
• Every entry now opens with a bold line stating the effect. All 108 entries were plain
  prose before, so a reader scanning the bold lines of a release got nothing. The cause,
  the measurement and the code anchor follow in the paragraph below, unchanged
• The em dashes and the ellipsis are gone. Ten em dashes and one ellipsis had entered
  the 1.2.3, 1.3.1 and 1.3.2 sections. Replaced by the punctuation or the word each stood
  for

Changed

• Release titles carry a headline after the colon instead of repeating the version. All
  ten published releases were titled with the bare number, which the release list already
  shows next to them. The headline is drawn from the section rather than invented

Security

• Nothing about the running bot changed. No source file, no dependency and no
  configuration was touched. Every measured figure, path, function name and version
  reference in the older sections was verified against its tag and left as it stood, except
  the layer count named above