chore(deps): Pin google-adk to version 1.17.0

[xCatG]

Summary

Pin google-adk dependency to version 1.17.0 for stability and compatibility with the Role Play System.

Changes

• Updated src/python/requirements.txt to pin google-adk==1.17.0

Testing

Comprehensive end-to-end testing performed:

• ✅ Backend server startup with google-adk 1.17.0
• ✅ User registration and authentication
• ✅ Chat session creation with medical roleplay scenario
• ✅ Real-time chat interaction with AI character (Sarah - Chronic Pain Patient)
• ✅ Gemini 2.5 Flash API integration confirmed working
• ✅ Token usage tracking: 411-677 tokens per message
• ✅ API performance: ~3 second response times
• ✅ Proper conversation history maintained across multiple turns

Backend Logs Confirmation

• ADK agents created successfully with ResourceLoader
• Gemini API calls returning HTTP 200 OK
• Character stayed in role with contextually appropriate responses
• No errors or warnings related to google-adk

🤖 Generated with Claude Code

[claude]

Claude encountered an error —— View job

---

I'll analyze this and get back to you.

[gemini-code-assist]

Summary of Changes

Hello @xCatG, 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 aims to enhance the stability and compatibility of the application, particularly with the Role Play System, by precisely controlling the version of a critical dependency. This ensures that the backend operates with a known, tested version of the Google ADK, preventing potential issues from future, unverified updates.

Highlights

• Dependency Pinning: The google-adk dependency has been explicitly pinned to version 1.17.0 to ensure stability and compatibility with the Role Play System.

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 pins the google-adk dependency to version 1.17.0, which is a good practice for ensuring build stability. My review focuses on extending this practice to all dependencies. I've suggested pinning all packages in requirements.txt to specific versions to guarantee reproducible builds and prevent potential conflicts or unexpected behavior across different environments. This will significantly improve the project's dependency management and overall stability.

[gemini-code-assist]

Pinning the google-adk dependency is a great step towards ensuring reproducible builds. However, other direct dependencies in this file (such as openai, pydantic, langchain, etc.) remain unpinned.

This practice can lead to non-reproducible builds, where different environments (developer machines, CI/CD, production) could install different package versions, potentially causing unexpected behavior or breakages.

To guarantee build stability, I strongly recommend pinning all dependencies in this file to specific, known-good versions. For example:

openai==x.y.z
pydantic[email]==x.y.z
langchain==x.y.z
# ... and so on for all dependencies

For more robust dependency management, consider using a tool like pip-tools. This allows you to manage your primary dependencies in a requirements.in file and automatically generate a fully-pinned requirements.txt that includes all transitive dependencies.

[claude]

Claude encountered an error —— View job

---

I'll analyze this and get back to you.