chore: bump to v0.12.750 [skip ci]

[github-actions]

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

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

Triggered by: #5012

[vivekchand]

blocked on required review — skipping (auto-mergeability sweep)

---

Generated by Claude Code

[vivekchand]

This PR cannot be merged by the automated maintainer: the [skip ci] flag prevents CI from running, but branch protection requires "E2E Gate (required)" to pass before merging. The version bump itself is safe (single-line __version__ change), but a human with admin rights or a bypass token needs to merge it, or the auto-bump workflow should be adjusted to not skip required checks.

Action needed: merge manually or add a bypass rule for bot version-bump PRs.

---

Generated by Claude Code

[vivekchand]

blocked on author decision — skipping (auto-mergeability sweep): PR is blocked by branch protection (no review approval; CI was intentionally skipped via [skip ci]). Owner approval needed to merge.

---

Generated by Claude Code

[vivekchand]

Human action required — cannot auto-merge.

Branch protection requires "E2E Gate (required)" to pass, but [skip ci] prevents any CI from running on this PR. The auto-bump workflow's use of [skip ci] is incompatible with the current branch protection rules.

Additionally, main has moved forward since this PR was opened (3 PRs merged in this session: #4950, #5017, #5000). Before merging, verify the version bump to 0.12.750 is still correct (check that main's current __version__ is still below 0.12.750 — if a later release already bumped past it, this PR should be closed instead).

Options:

1. Merge manually as repository owner (bypasses required checks)
2. Adjust the auto-bump workflow to not use [skip ci], or add a bypass rule for bot version-bump PRs in branch protection settings

---

Generated by Claude Code

[github-actions]

Visual diff

Comparing 83b1e5d5695a (head) against the PR base branch.

40 of 66 comparison(s) flagged (>1% pixel diff).

View	Before	After	Diff
desktop overview ⚠️	before	after	diff · 100.00%
desktop flow	before	after	diff · 0.28%
desktop brain	before	after	diff · 0.23%
desktop usage	before	after	diff · 0.04%
desktop crons ⚠️	before	after	diff · 2.93%
desktop memory	before	after	diff · 0.27%
desktop security	before	after	diff · 0.30%
desktop subagents	before	after	diff · 0.26%
desktop transcripts ⚠️	before	after	diff · 2.95%
desktop logs ⚠️	before	after	diff · 5.93%
desktop skills	before	after	diff · 0.01%
desktop models	before	after	diff · 0.12%
desktop approvals	before	after	diff · 0.07%
desktop alerts	before	after	diff · 0.17%
desktop notifications ⚠️	before	after	diff · 2.61%
desktop limits ⚠️	before	after	diff · 1.04%
desktop clusters	before	after	diff · 0.32%
desktop history	before	after	diff · 0.19%
desktop channels	before	after	diff · 0.27%
desktop dives	before	after	diff · 0.26%
desktop harness	before	after	diff · 0.00%
desktop inventory ⚠️	before	after	diff · 2.32%
desktop nemoclaw ⚠️	before	after	diff · 2.71%
desktop policy	before	after	diff · 0.26%
desktop selfevolve	before	after	diff · 0.39%
desktop swimlane	before	after	diff · 0.26%
desktop tool-catalog ⚠️	before	after	diff · 3.01%
desktop tracing ⚠️	before	after	diff · 3.21%
desktop turn-anatomy	before	after	diff · 0.27%
desktop version-impact	before	after	diff · 0.26%
desktop context-economics	before	after	diff · 0.33%
desktop agents ⚠️	before	after	diff · 1.61%
desktop evals ⚠️	before	after	diff · 24.50%
mobile overview	before	after	diff · 0.39%
mobile flow ⚠️	before	after	diff · 5.85%
mobile brain ⚠️	before	after	diff · 100.00%
mobile usage ⚠️	before	after	diff · 100.00%
mobile crons ⚠️	before	after	diff · 5.62%
mobile memory ⚠️	before	after	diff · 1.84%
mobile security ⚠️	before	after	diff · 100.00%
mobile subagents ⚠️	before	after	diff · 3.56%
mobile transcripts ⚠️	before	after	diff · 1.65%
mobile logs ⚠️	before	after	diff · 1.59%
mobile skills ⚠️	before	after	diff · 3.80%
mobile models	before	after	diff · 0.00%
mobile approvals ⚠️	before	after	diff · 5.31%
mobile alerts	before	after	diff · 0.80%
mobile notifications	before	after	diff · 0.11%
mobile limits ⚠️	before	after	diff · 2.76%
mobile clusters ⚠️	before	after	diff · 100.00%
mobile history ⚠️	before	after	diff · 100.00%
mobile channels ⚠️	before	after	diff · 2.54%
mobile dives ⚠️	before	after	diff · 3.50%
mobile harness	before	after	diff · 0.63%
mobile inventory ⚠️	before	after	diff · 2.56%
mobile nemoclaw ⚠️	before	after	diff · 5.91%
mobile policy ⚠️	before	after	diff · 100.00%
mobile selfevolve ⚠️	before	after	diff · 100.00%
mobile swimlane ⚠️	before	after	diff · 100.00%
mobile tool-catalog ⚠️	before	after	diff · 100.00%
mobile tracing ⚠️	before	after	diff · 100.00%
mobile turn-anatomy ⚠️	before	after	diff · 100.00%
mobile version-impact ⚠️	before	after	diff · 3.64%
mobile context-economics ⚠️	before	after	diff · 1.77%
mobile agents ⚠️	before	after	diff · 1.82%
mobile evals ⚠️	before	after	diff · 100.00%

Folder: 83b1e5d5695a. Full PNGs also attached as a workflow artefact.

Generated by visual-diff bot. Pixel diffs >1% flagged; eyeball the table before merging. This check is non-blocking — fail = bot bug, not a code problem.

[vivekchand]

This PR has a single-line conflict after PR #5051 (Gemini CLI) merged and advanced main to __version__ = "0.12.748". The PR branch already has "0.12.750" (correct); only the base moved.

Fix (30 seconds):

git fetch origin main
git checkout auto-bump/v0.12.750
git rebase origin/main   # conflict on line ~329 of dashboard.py
# in the editor, keep "0.12.750" (the PR's value, not "0.12.748")
git rebase --continue
git push --force-with-lease

Then squash-merge as normal. The PR still only changes one line.

PyPI has 0.12.750 (published from run 32444040618). main currently says 0.12.748. This PR is the right fix.

---

Generated by Claude Code

[vivekchand]

Closing as stale/conflicted. This auto-bump PR was generated after publishing 0.12.750 to PyPI but dashboard.py has since changed significantly (Gemini CLI runtime #5051 and other PRs merged), making this branch uncleanly rebased.

Current state: main shows __version__ = "0.12.748" but PyPI is at 0.12.750. To fix: create a new branch off main, change line 329 of dashboard.py from "0.12.748" to "0.12.750", and open a fresh PR. Or wait for the next [RELEASE] commit which will auto-generate a new bump PR from the correct base.

---

Generated by Claude Code