chore: rebase PR #28 CHANGELOG onto develop (preserve 0.0.9/0.0.10) and clarify package version

[marassteiner]

Context

Follow-up from review of #28

Evidence

1. Branch lag / CHANGELOG rewrite

   • PR branch rewrites CHANGELOG.md starting at ## 0.0.8 and fills 0.0.1–0.0.7.
   • origin/develop already has ## 0.0.10 and ## 0.0.9 (from feat(status): expose cached device status for unseeded-device detection #29 / fix(android): align native libs to 16 KB pages #30).
   • merge-tree reports CHANGELOG.md as changed in both; tags exist through v0.0.10.
   • Before merge, rebase onto current develop and keep 0.0.9 / 0.0.10 entries while retaining the backfilled 0.0.2–0.0.7 history.

2. pubspec version still 0.0.1

   • pubspec.yaml:3 → version: 0.0.1 (unchanged by chore: harden repo CI, docs, license and native logging #28; pre-existing on develop).
   • CHANGELOG / git tags describe releases through 0.0.10.
   • Auto-tag flow manages tags separately, but package metadata and CHANGELOG head remain confusing for pub consumers.

Suggested fix

• Rebase chore/repo-hardening onto latest develop and resolve CHANGELOG by keeping the union of both histories.
• Decide whether pubspec.yaml should track the latest tag (or next unreleased version) or document why it stays at 0.0.1 under the auto-release model.

Severity

Follow-up only — Git will surface the CHANGELOG conflict at merge time; not a silent production bug. Still worth fixing before/during merge so release notes are not dropped.