chore: bump to v0.12.759 [skip ci]

[github-actions]

Auto-opened by release-on-merge.yml after publishing clawmetry==0.12.759 to PyPI (run 32602227169).

This PR only syncs __version__ in dashboard.py with what is already live on PyPI. Safe to squash-merge as-is.

Triggered by: #5103

[vivekchand]

Automated maintainer pass (2026-08-23): This is the current auto-bump PR syncing __version__ in dashboard.py to v0.12.759, which is already live on PyPI. The two older stale bumps (#5096 for v0.12.757, #5104 for v0.12.758) have been closed as superseded.

This PR is blocked waiting for reviewer approval from @vivekchand. It is a 1-line change and safe to squash-merge once approved.

---

Generated by Claude Code

[vivekchand]

Autonomous maintainer pass (2026-08-23): merge attempted, blocked by branch protection.

The required status check "E2E Gate (required)" has never run on this PR because [skip ci] is in the title. The branch protection rule requires that check to pass, so the GitHub merge API returns 405.

Two options to unblock:

1. Owner admin-merge: you can bypass required status checks as a repo admin via the GitHub UI ("Merge pull request" with admin override).
2. Remove [skip ci] and re-push: if the auto-bump workflow is updated to only skip non-required checks (e.g. use [skip e2e] instead of [skip ci]), the E2E Gate would run and satisfy the protection rule. This is a workflow-level fix worth making for future auto-bumps.

The change itself is safe: one line, __version__ = "0.12.748" → "0.12.759", already live on PyPI. No code risk.

---

Generated by Claude Code

[vivekchand]

Autonomous maintainer pass (2026-08-23): this PR is blocked by branch protection — the required "E2E Gate (required)" check was never satisfied because the auto-generated commit includes [skip ci], which suppresses all CI runs on the branch.

Cannot be merged autonomously without CI. One of two options to unblock:

1. Preferred — push a trivial commit to the branch (e.g., a whitespace-only touch of any file without [skip ci] in the message). CI will run on the new HEAD and the required check will pass, after which the PR can be squash-merged.
2. Admin override — merge via the GitHub UI using repository admin privileges, which can bypass required status checks.

Everything else is fine: the change is 1 line (version bump to match the already-published PyPI release clawmetry==0.12.759), no CI is semantically needed, and it is safe to squash-merge once the gate is satisfied.

---

Generated by Claude Code

[vivekchand]

Closing as stale — superseded by #5118 (v0.12.760 bump, which is the current live PyPI version). Squash-merge #5118 instead.

---

Generated by Claude Code