v0.2.1

Portfolio-readiness pass on top of v0.2.0 — a real feature surfaced on the
dashboard, a couple of real bugs fixed, and a pass to make the landing page
and README read well to someone skimming them cold.

What's new since v0.2.0:

• Task pool surfaced on the dashboard. The pull-based queue/next
  dispatch model (added in v0.2.0) now shows up visually: the dashboard's
  Active tasks stat gets an "N in pool, unclaimed" chip whenever something's
  sitting in the shared pool, so push-based and pull-based dispatch are both
  visible at a glance instead of only inferable from a task's assignee.
• Fixed: the landing page's release button pointed at a pinned tag
  instead of /releases/latest, so it would've gone stale on every future
  release. Fixed, and the README's test count (which had drifted from the
  actual suite size) was corrected too.
• Richer, more realistic seed data (a ci-runner session/host, a
  reworked task pool and message thread with a real burst/lull pattern) and
  a scrollable-timeline CSS fix so the dashboard's two columns balance
  visually instead of one trailing off far past the other.
• Portfolio readability pass: the landing hero now leads with a
  plain-English line and a stat strip (test count, verified platforms, the
  two-machine dogfood story) instead of burying that context below the
  fold. README gained a "Known limitations" section (queue has no priority
  or expiry, dashboard is intentionally local-only with no auth) so those
  read as deliberate scope, not oversights.
• package.json's version had been stuck at 0.1.0 since the project
  started, even through the v0.2.0 tag. Synced to 0.2.1 here.

62/62 tests passing, CI green, verified cross-platform (macOS, Windows,
Linux via CI).

Full Changelog: v0.2.0...v0.2.1