CLAUDE.md: bring up to date with dev

[derrynknife]

This audits CLAUDE.md against dev and corrects it without rewriting it. It goes from 555 to 534 lines.

Changed

• Pointer to CONTRIBUTING.md at the top. CONTRIBUTING covers setup, checks, tests, pull requests, deprecations and releases. The duplicated Testing and Releasing sections are now one short list of what CONTRIBUTING leaves to the maintainer: no extra CI runs, every merge and release needs a go-ahead, merge the release with a merge commit, do a dry run first, then check the release.
• Version status. 0.13 is the latest release. 0.14 is prepared on dev (CHANGELOG dated 2026-10-16) and waiting on Release 0.14 #353. dev needs surpyval >= 0.24.
• Deprecations. The long history of what 0.11–0.13 deprecated is cut down to the tests that keep those removals gone, plus what 0.14 deprecates for 0.15 (NEXT_REMOVAL).
• surpyval workarounds.
  • #821 (the mixture quantile) is fixed on surpyval's develop but not released, so the workaround stays.
  • #845 only added a unit label, with no conversion. The duty-cycle rescaling therefore stays, and the units note now says this.
  • Added #830, which rbd/uncertainty.py works around by holding the offset, and the #833 refusal in rbd/_processes.py. Neither was listed before.
  • No listed workaround has been removed from the code yet.
• Removed a release step written in terms of one session's tool names (actions_run_trigger).
• "Reliafy app (separate, open source)" now reads "(separate)".

Checked, unchanged

• The timelines/calendars scope rule matches repyability/maintenance on dev.
• The symbols, test names and files the notes reference exist on dev.
• Nothing private: the only engine hits are the public numba/python engines and the public engines.py plugin interface.

Not changed here: CONTRIBUTING.md still calls the event loop RepairableRBD._replicate. It is now _event_loop._replicate.

🤖 Generated with Claude Code

https://claude.ai/code/session_019Km2eWBiPJ5JNkme3vRg4B