deps: update wonton to v0.0.38 and refresh dependencies

[myzie]

Summary

• Bump github.com/deepnoodle-ai/wonton v0.0.37 -> v0.0.38:
  • httpguard: SSRF-guarded HTTP client now drops credentials on a downgraded redirect, and the guard's reach was widened
  • deps: cleared reachable vulnerabilities, added govulncheck to CI
  • port: added strs, ptr, and thumbnail packages
  • docs: README cover image + badge refresh
• General Go dependency refresh via go get -u -t ./... && go mod tidy, notably:
  • github.com/deepnoodle-ai/dive v1.12.0 -> v1.25.1
  • github.com/oapi-codegen/runtime v1.4.0 -> v1.7.0
  • github.com/pelletier/go-toml/v2 v2.3.0 -> v2.4.3
  • github.com/alecthomas/chroma/v2 v2.20.0 -> v2.27.0
  • github.com/yuin/goldmark v1.7.13 -> v1.8.5
  • golang.org/x/sys v0.41.0 -> v0.47.0
  • golang.org/x/term v0.38.0 -> v0.45.0
  • github.com/dlclark/regexp2 -> github.com/dlclark/regexp2/v2 v2.7.1 (transitive)

Only go.mod/go.sum changed. No application code was modified.

Test plan

• go build ./... — clean
• make test-go (go test ./...) — all packages pass:
  • cmd/mobius, internal/authstore, internal/cligen, mobius, mobius/action, mobius/api
• TypeScript / Python were not touched (no test-ts/test-py run, per scope)

Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your current included review allowance is based on your included PR review attempts over the past 7 days.

Next review available in: 4 minutes

Limit details: You’ve used the included review currently available. Your 61 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ea0bbf68-4788-4583-8b6e-e99dcd3d8c91

📥 Commits

Reviewing files that changed from the base of the PR and between db40dc7 and 3c83265.

⛔ Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (1)

• go.mod

---

_{Comment @coderabbitai help to get the list of available commands.}