Cuts the 0.3.0 release prep

[johnnyt]

Why

changelog.d/ had accumulated fourteen fragments since the 0.2.0 prep
(1562d8c), and the release recipe landed in .claude/wurk.json earlier
today (sui#78, 0d4ae49) - so this is the first prep this repo cuts through
/wurk:release rather than by hand. sui-dba is the operator-named release
bead the authority table's "a version bump on a release bead's branch" row
requires.

What

The four carriers .claude/wurk/release.md names, and nothing else:

• mix.exs - @version 0.2.0 -> 0.3.0
• README.md - the install pin {:statifier_ui, "~> 0.1"} -> "~> 0.3"
• CHANGELOG.md - a new ## [0.3.0] 2026-09-02 section
• changelog.d/*.md - all fourteen fragments deleted in the same commit

Version: 0.3.0, a minor rather than a patch. StatifierUI.Live and
Live.State, Live.ExpressionInput and Expression, Trace.Capture,
Trace.Projection, Trace.Otel, Trace.DeepLink, Trace.Json.decode/1
and the inspector's scrubber API (points/1, step/3, resolution/2,
selection_note/2) are all new public surface since 0.2.0. Nothing is
removed and nothing breaks: otel and $redacted are additive
reservations, the wire format stays at version 1, and
Inspector.event_log/1 keeps its behaviour beside the new event_log/2.
Pre-1.0, that is a minor.

The section follows the shape 1562d8c set and release.md step A
records: the no-separator ## [X.Y.Z] YYYY-MM-DD heading form, no
link-reference block, a composed lead paragraph, then the fragments'
entries grouped Added (11 blocks) / Changed (6) / Fixed (5). Every
one of the 26 fragment blocks was verified present byte for byte by script
before the commit.

Notes

• README pin drift repaired, not corrected back. The pin still read
  ~> 0.1 while mix.exs read 0.2.0, because the 0.2.0 prep bumped the
  version file without the pin. Per release.md's "The README install pin"
  section, this prep moves it straight to the new minor.
• assets/package.json's "version" is untouched, still 0.2.0.
  release.md records it explicitly as not a release carrier: it
  describes the JS source package a host's own esbuild compiles through
  file:../deps/, it was created already carrying that string
  (61d647f), 1562d8c did not move it, and nothing asserts it against
  Mix.Project.config()[:version].
• mix.lock is untouched. release.md's steps are silent on
  refreshing the lock, so the statifier 2.0.0 entry was left where it is
  rather than moved on inference.
• Four prose paragraphs carried over in place. sui-3gg, sui-4w2,
  sui-6e4 and sui-8hg each closed with a prose paragraph under their
  own heading rather than a bullet. release.md forbids reordering,
  consolidating or rewording a fragment at release time, so those
  paragraphs were carried byte for byte where they sat, which leaves four
  prose interludes inside the Added list. Flagged for the pre-tag
  editorial read rather than silently dropped or moved.
• Gate: full mix quality green - 943 of 943 tests, 93.0% coverage,
  attested. Gettext and Sobelow skip permanently
  (gate.not_applicable_skips); no third skip line appeared.
• mix hex.build succeeded: Building statifier_ui 0.3.0 ...
  Saved to statifier_ui-0.3.0.tar, checksum
  4a2ed94995b7952d69e4d978acfb5b7183e61e83e84264b3fe6795ff9c312ce2. The
  tarball was deleted afterwards and is not in the diff.
• No tag, no mix hex.publish, no GitHub release. git tag --points-at HEAD is empty. Tagging and publishing are the operator's, in
  every campaign; this request contains the bump and the promotion only.
• Separately, and deliberately not fixed here because it is outside the
  bump-and-promotion scope: .claude/wurk/commit.md's "Version bump: none"
  section still says the manifest's release key is null and that
  /wurk:release refuses in this repo. That went stale when sui#78 landed
  the release block.

Closes sui-dba