chore(release): v0.12.0

[BenSheridanEdwards]

Summary

• Bump to 0.12.0 with a changelog entry covering the twelve merged PRs (fix(source): attribute matching must not match long-clickable as clickable #65–feat(locator): toHaveValue matcher and getByRole checked/disabled filters #76): scrollIntoView, nativeproof inspect, toHaveValue + role state filters, non-input fill warnings, the README overhaul, and seven correctness fixes across the locator core, CLI, and mock server.
• Minor bump per semver: additive API, no breaking changes.

Proof

• npm run check
  • Passed on release/v0.12.0.
• npm test
  • Passed: 181/181 (includes the packaged-CLI smoke test).
• Generated project/device proof, or N/A:
  • Merged main re-verified before bumping (check + 181/181). Device-facing features carry their own committed proofs from their PRs: docs/proof/scroll-into-view/ (both platforms), docs/proof/inspect/ (Android live run), docs/proof/atomic-fill/ (both platforms, v0.11.0).
  • Screenshots: Not applicable; version/changelog-only diff.

Risk

• Minimal. Version and changelog only.

Notes

• Full device coverage not run for this diff (no code changes).
• npm publish to follow once merged, so consumers pinning exact versions (WordlyMobileAutomatedTests pins 0.10.14) can bump.

PR Proof Law

• I followed .agents/DEFINITION_OF_DONE.md and .agents/skills/pr-inline-screenshot-proof/SKILL.md.
• Screenshots are committed and embedded inline with ![alt](...png?raw=1), or the proof section says Not applicable with the technical reason.
• The PR body has no bare screenshot links, local paths, relative paths, or proof placeholders.