v0.10.1

Changed

• CI checks a release's version bump against its own changelog section, so
  the numbering rule is enforced rather than remembered: a BREAKING entry
  must move the slot reserved for it (the minor while 0.x, the major from
  1.0), and moving that slot without one is refused. scripts/check_version_bump.py
  runs the same check locally. Releases through 0.10.0 bumped the minor for
  features before the rule was written down; they are grandfathered, and the
  check applies from 0.10.1 on.

Fixed

• The version guard reads a declared break, not the word: it looks for the
  bolded entry prefix CONTRIBUTING mandates (or the commit-footer spelling)
  rather than any occurrence of "BREAKING". A bare substring match meant
  release notes that merely described the rule were read as declaring a
  break, which refused the very release introducing the guard.
• An active entry whose adapter reports present: False now alerts "expected
  present, not observed", the same as observing nothing at all. Only the
  retired path consulted that fact, so a booted-out service the adapter had
  looked at produced a soft report at most, and with tolerance: auto it was
  folded into silence: the one thing the loop exists to catch. The alert is
  structural, so tolerance cannot fold it, and the soft signals below it are
  skipped because they describe a thing that is not there. A parked entry
  stays silent (dormancy is its expected state) and an unconfigured active
  secret keeps its own more specific message.