[RomainROCH]

What this PR does

Finalize the v0.2.1 changelog and release notes for bounded control requests,
status discovery, singleton lifecycle coverage, the corrected status shutdown
wake-up, and the passive physical-power validation kit. Keep unsigned-binary,
local-security and Windows/manual acceptance limits explicit.

Why

The notes need to describe the reproducible missed status wake-up and the passive
kit while preserving the distinction between mocked preparation, historical VM
results and acceptance of the final release binary. The shutdown regression does
not establish the cause of the earlier CI stall.

How it was tested

• scripts/check.ps1 -Mode Docs: PASS, 26 Markdown files in the isolated notes
  checkout; local destinations and encoding checked, local anchors not validated.

• git diff --check: PASS. The original notes checkout remains clean and its
  two source hashes match the recorded pre-edit hashes.

• Local private-content and identity checks: PASS for the prepared documents,
  diff, PR text and receipts. Final staged/history/publication gates remain the
  integrator's responsibility.

• Runtime smoke, native Power Requests and physical power tests were not run for
  this docs-only change. The kit's 111 checks use mocked diagnostics.

• scripts/check.ps1 -Mode Full passes for Rust changes (or -Mode Docs for docs only)

• tests/developer_checks.ps1 passes if developer tooling changed (not changed here)

• tests/smoke_safety.ps1 passes if smoke setup or cleanup changed (not changed here)

• Relevant smoke/manual checks run in an isolated environment, or skips explained

• Docs updated if behavior changed

Checklist

• Base branch stated; intended integration target follows CONTRIBUTING.md
  (target main for the authorized v0.2.1 release integration).
• Intentional architecture changes include rationale; unrelated drift is reported
  (no architecture change in this documentation PR).
• Business-model changes reflect an explicit maintainer decision
  (no business-model change; unsigned downloads and community support retained).

Publish these notes only after the separate status fix and passive kit are
integrated and the exact final main commit passes the required release gates.