release: v0.5.1

[askalf]

Version bump 0.5.0 -> 0.5.1 + CHANGELOG stamp. Ships #56 (observe({page}) live-capture routing — the seam askalf's fleet browser_use uses) and #55 (fixture cleanup). After merge: gh release create v0.5.1 --target main + dispatch publish.yml (OIDC TP).

[sprayberry-reviewer]

Automated review from the Sprayberry Labs fleet code reviewer.

Verdict: Clean — no blocking issues. Approving.

This is a release/version-bump PR (0.5.0 → 0.5.1): a CHANGELOG stamp summarizing already-merged #56 and #55, plus the matching package.json/package-lock.json version bumps. No source/logic changes are introduced by this diff itself.

What I checked

• CHANGELOG.md: new ## [0.5.1] entry accurately describes the two prior changes it ships (live-capture routing fix #56, fixture cleanup #55) — reads consistent with the PR description.
• package.json / package-lock.json: version fields bumped in lockstep (0.5.0 → 0.5.1), no dependency changes.
• CI check-rollup: CodeQL, analyze (javascript-typescript), test, test-node20 all pass.

Findings

None. No correctness, security, reuse, efficiency, or test-coverage concerns in the changed lines — there's no logic to review here, just metadata/doc updates.

What's good

Changelog entry is clear and gives concrete behavioral detail (routing seam, no-navigation guarantee) rather than a generic "fixed bug" note — useful for downstream consumers like browser_use.