docs: DEVELOPMENT.md described a release architecture that does not exist

[BernardJen]

Documentation only. Found while checking that the markdown left after deleting TODO.md (#240)
was actually current — it wasn't.

The one line I was asked to fix, and what was behind it

The quick reference said "After PR merge, release happens automatically". It does not. Chasing
that turned up that the entire release story in this file describes workflows that were replaced:

Claimed	Reality
Auto-Release workflow runs on main push	no such workflow; only CI runs on push
Build and Release triggers on a new tag	no such workflow, and nothing triggers on a tag push
Actions → Build and Release	not in the Actions list
Two workflows, chained by a tag	One workflow, Release, workflow_dispatch only

Verified against .github/workflows rather than assumed: two files, CI (pull_request, push)
and Release (workflow_dispatch only).

Why this was worse than a stale sentence

Anyone following section 6's "manual release" procedure would create and push a tag expecting a
build, get nothing, and be left with a tag that has no release attached — which then has to be
deleted before the real release can use that version.

I hit the live version of this today: releasing v2.14.0 required gh workflow run release.yml by
hand, exactly as CLAUDE.md says and exactly as this file said it wouldn't.

What changed

• Section 5 now says plainly that merging releases nothing, and lists the six jobs the single
  Release workflow does in one run — including that lint and test gate it.
• Flow diagram redrawn with the manual step where it actually is.
• Section 6 rewritten around gh workflow run release.yml, with a "do not release by pushing
  a tag" warning that names what goes wrong.
• Two post-release checks added, because both have failed silently before and neither shows as
  a red run:
  • all three version files moved together (fix: keep package-lock.json in step with the version bump #197 — the lock sat at 2.9.0 while package.json
    reached 2.13.0 for four releases);
  • the update manifests name assets that exist (bug: macOS auto-update is broken — latest-mac.yml references filenames that don't exist #86 — otherwise every macOS auto-update 404s
    while the release looks perfect).
• Troubleshooting: "Release Not Triggering" → "No Release Appeared", which starts by asking
  whether it was run at all. The old version assumed an automatic trigger that has never existed
  here.
• "Version Mismatch" now covers package-lock.json. Syncing only package.json is precisely
  how fix: keep package-lock.json in step with the version bump #197 happened.
• The hotfix section's "Auto-release will create a patch version" corrected.

Verification

• Branched from main (e1d1367).
• Every workflow name the document now mentions was checked to exist against
  .github/workflows/*.yml; the only remaining "Auto-Release" mention is a deliberate one saying
  it does not exist.
• npm run lint clean (no code touched).
• The documented release command is the one I used for v2.14.0 an hour ago, so it is verified by
  use rather than by reading.

Not verified

• The hotfix and rollback procedures elsewhere in the file are untouched and I have not exercised
  them. They do not mention the phantom workflows, but "does not contradict the workflow files" is
  a weaker claim than "known to work".