docs: bring CURRENT_STATE forward after #161 and fix the stale station ID allocation #164

Bringing the narrative parts of CURRENT_STATE.md forward after PR #161 and this
week's contributor work. The automated half is fine: #152 correctly logged 0.4.5
and moved the Package Status Table with no manual step, so this is only the prose
the automation deliberately leaves alone.

Stale claims

• Station ID allocation (line 408) says 017 goes to Add a new scenario: meter-value-zero #108. It does not:
  refused-authorization.ts:8 took CS-SYNTHETIC-017 when it shipped in 0.4.5,
  after that line was written. Add a new scenario: meter-value-zero #108 has been corrected to reserve
  CS-SYNTHETIC-021. The line also still lists 018 as merely assigned to Add a new scenario: heartbeat-timeout #137,
  which has now shipped.
• Rule coverage (lines 426 to 428) says two of the sixteen rules lack a
  scenario. After feat(scenarios): add heartbeat-timeout scenario for TIMEOUT_NO_HEARTBEAT #161 only one does. Verified by iterating the registry: 15 of 16
  codes appear in some scenario's expectedFailures, and
  REPEATED_BOOT_NOTIFICATION is the sole gap, tracked by Add a new scenario: repeated-boot-notification #139.
• Corpus arithmetic (line 430) says "17 today". The registry is at 19.
• The pipeline section stops at Add a new scenario: firmware-update-failure #138 and records nothing about feat(scenarios): add heartbeat-timeout scenario for TIMEOUT_NO_HEARTBEAT #161, the third
  external contributor's first merged pull request.

Fix

Correct those four, and add an entry covering this week: #161 merged, the two
remaining scenario issues assigned, the #108 ID collision caught and fixed, and
#163 opened for the assertions-coverage gap found while reviewing #161.

Documentation only. No changeset: CURRENT_STATE.md is not in the package files
list, so nothing here ships to npm.