Update Claude Opus 4.6 SWE-Bench Score

[insign]

This PR updates the SWE-Bench score for claude-opus-4-6-20260205 strictly verifying against the source.

The score has been updated to 75.60 from null based on a scrape from www.swebench.com that yielded: Claude Opus 4.6 | 75.60.
Additionally, the metadata last_update and version fields have been updated to represent the data freshness.

I have strictly followed UPDATE.md ensuring all added values are strictly verified. Other fields lacking robust confirmation have been explicitly maintained without modification. All checks using ./precommit.sh passed successfully.

---

PR created automatically by Jules for task 130439358020788897 started by @insign

[cloudflare-workers-and-pages]

Deploying showd with    Cloudflare Pages

Latest commit:	533a7e5
Status:	✅  Deploy successful!
Preview URL:	https://b7ee23bc.showd.pages.dev
Branch Preview URL:	https://update-claude-opus-swe-score.showd.pages.dev

View logs

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[insign]

This targeted update still looks useful, but it no longer merges cleanly against the current \ because the same data file changed after newer Showdown PRs were merged. Please rebase onto the current base branch and reapply the verified \ SWE-Bench update so the final diff stays limited to the missing score and the current metadata refresh.

[insign]

This targeted update still looks useful, but it no longer merges cleanly against the current main because the same data file changed after newer Showdown PRs were merged. Please rebase onto the current base branch and reapply the verified claude-opus-4-6-20260205 SWE-Bench update so the final diff stays limited to the missing score and the current metadata refresh.

[google-labs-jules]

This targeted update still looks useful, but it no longer merges cleanly against the current \ because the same data file changed after newer Showdown PRs were merged. Please rebase onto the current base branch and reapply the verified \ SWE-Bench update so the final diff stays limited to the missing score and the current metadata refresh.

I have successfully rebased the branch onto the current base branch (main) and resolved the merge conflicts. The missing score and metadata refresh for claude-opus-4-6-20260205 are now applied correctly to the updated data file.

[google-labs-jules]

This targeted update still looks useful, but it no longer merges cleanly against the current main because the same data file changed after newer Showdown PRs were merged. Please rebase onto the current base branch and reapply the verified claude-opus-4-6-20260205 SWE-Bench update so the final diff stays limited to the missing score and the current metadata refresh.

I have successfully rebased the branch onto the current base branch (main) and resolved the merge conflicts. The missing score and metadata refresh for claude-opus-4-6-20260205 are now applied correctly to the updated data file.