cut: v0.42.0

[InauguralPhysicist]

Cuts v0.42.0. Updates the four sites the v0.41.0 cut touched: VERSION, CLAUDE.md's "Latest release" line, the CHANGELOG.md section, and docs/llms.txt's version stamp.

Contents since v0.41.0

• stdlib: complex numbers and general eigenvalues (stdlib: complex numbers (#1043) and general eigenvalues (#1042) #1051, closing stdlib: polynomial roots / general eigenvalues (lib/linalg stops at eigenvalues_2x2) #1042 and stdlib: complex-number module (every numeric consumer re-rolls [re,im] arithmetic) #1043) — new lib/complex.eigs (arithmetic, polar form, poly_roots), linalg.charpoly + linalg.eigenvalues for any square n with complex spectra, and engineering.phase_spectrum with magnitude_spectrum/power_spectrum now delegating to complex.mag/mag2.
• build(deps): github-actions group bump (build(deps): bump the github-actions group with 4 updates #1050).

Why now

The tag is the version pin for consumers. phugoid's devcontainer clones EigenScript at a released tag; lib/complex.eigs does not exist in v0.41.0, so phugoid's modes.eigs stdlib swap — 45 lines of hand-rolled complex arithmetic and root-finding deleted, chain eigenvalues verified bit-identical — is blocked until this tag exists.

On the apparent doc-drift contradiction

CLAUDE.md now names a tag that does not exist yet. That is the documented ordering, not an oversight: doc-drift rule 2 compares that line to the latest tag, and the release build runs after the tag is created, so a stale line fails the release's own suite (it bit the v0.27.0 cut).

It does not fail this PR's CI because only the first ci.yml job checks out with fetch-depth: 0; the suite job's default checkout fetches no tags, so the rule reports "no tags; skipping" there. Verified against the v0.41.0 cut (#1037), which passed 18/18 in exactly this state.

Verification

Rebuilt and re-ran tests/test_cli.sh, because --version is baked in at compile time from VERSION — a bump without a rebuild makes the binary disagree with the file. 15/15, and --version prints 0.42.0.

After merge: dispatch Actions → Release → Run workflow (this environment's git proxy cannot push tags, and a GITHUB_TOKEN-pushed tag would not retrigger the workflow).

🤖 Generated with Claude Code

https://claude.ai/code/session_01Aj9b82JBb8WS3b8ExoV5Yt