chore(release): reset version to 0.0.1 and regenerate lockfile

[QueryPlanner]

This PR resets the version to 0.0.1 and regenerates uv.lock from scratch. This fixes the build issue where the renamed 'agent' package was not being picked up by Docker.

[gemini-code-assist]

Summary of Changes

Hello @QueryPlanner, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical Docker build failure by performing a full reset of the project's versioning and dependency lockfile. The core change involves setting the project version to 0.0.1 and then regenerating the uv.lock file, which implicitly updates several third-party dependencies to their latest compatible versions. This comprehensive update ensures that the build process correctly recognizes and incorporates all necessary packages, specifically resolving an issue where a renamed 'agent' package was not being picked up by Docker.

Highlights

• Project Version Reset: The project's version has been explicitly reset from 0.8.0 to 0.0.1 in pyproject.toml and uv.lock.
• Dependency Lockfile Regeneration: The uv.lock file has been completely regenerated from scratch, ensuring all dependencies are re-evaluated and pinned.
• Build Issue Resolution: This change is intended to fix a Docker build issue where a renamed 'agent' package was not being correctly picked up.
• Dependency Updates: As a result of the lockfile regeneration, several key dependencies have been updated, including litellm (from 1.81.1 to 1.81.3, removing grpcio), mcp (from 1.25.0 to 1.26.0), python-multipart (from 0.0.21 to 0.0.22), and wcwidth (from 0.3.2 to 0.3.5).

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request resets the project version to 0.0.1 in pyproject.toml and regenerates the uv.lock file to address a build issue. The changes are consistent with the description, updating the project's version and refreshing dependencies in the lock file. This appears to be a standard maintenance operation, and I see no issues with the proposed changes.