docs: fix outdated documentation (automated weekly drift check)

[Miyamura80]

Automated weekly check for documentation drift. Did not find any outdated documentation based on actual project behaviors and code source. Tests pass successfully.

---

PR created automatically by Jules for task 1520991797522201022 started by @Miyamura80

---

Summary by cubic

Automated weekly docs drift check found no outdated docs. Cleaned up uv.lock by removing stale exclude-newer options; no dependency changes.

^{Written for commit 3d5f374. Summary will update on new commits. Review in cubic}

[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.

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}