docs: Current Version paragraph still reads 0.4.4 after 0.4.6 shipped #167

Publishing 0.4.6 left the hand-written "Current Version" paragraph behind. It
still opens with 0.4.4, published 2026-07-30.

This is the automation's boundary working as intended rather than a bug in it. #152
maintains the Release Log and the Package Status Table, both of which are correct
at 0.4.6. The narrative sentence is deliberately human, because a per-release
description is commentary rather than a fact, so it has to be moved by hand.

Stale

• Opens at 0.4.4 / firmware-update-failure / 2026-07-30. Current is 0.4.6 /
  heartbeat-timeout / 2026-08-08.
• Says "0.4.3 and 0.4.4 each carry a good-first-issue completed by an outside
  contributor" and totals "three external good-first contributions". With feat(scenarios): add heartbeat-timeout scenario for TIMEOUT_NO_HEARTBEAT #161 in
  0.4.6 there are now four, and three of them sit in the 0.4.x line:
  Add a new detection rule: REPEATED_BOOT_NOTIFICATION #105 via PR feat(core): detect repeated boot notifications #114 in 0.3.1, Add a new scenario: firmware-update-success #104 via PR feat(scenarios): add firmware update success scenario #133 in 0.4.3, Add a new scenario: firmware-update-failure #138 via PR feat(scenarios): add firmware-update-failure scenario #147 in
  0.4.4, and Add a new scenario: heartbeat-timeout #137 via PR feat(scenarios): add heartbeat-timeout scenario for TIMEOUT_NO_HEARTBEAT #161 in 0.4.6.

Fix

Move the paragraph to 0.4.6 and correct the count to four, naming the three that
landed in 0.4.x.

Documentation only. No changeset: CURRENT_STATE.md is not in the package files
list.