docs: remove development language from python server SDK

[jenna-winkler]

Summary

Goal: to use language that clearly separates concerns of building agents (not our focus) and enabling the packaging of any agent for platform deployment (our focus)

Linked Issues

Documentation

• No Docs Needed: Docs were adjusted

If this PR adds new feature or changes existing. Make sure documentation is adjusted accordingly. If the docs is not needed, please explain why.

[gemini-code-assist]

Summary of Changes

Hello @jenna-winkler, 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 refines the documentation for the Python Server SDK by updating its language and directory structure. The primary goal is to clearly differentiate between building agents and integrating them into the platform. This is achieved by renaming documentation paths and updating terminology to emphasize the SDK's role in enabling the packaging and deployment of any agent, rather than focusing on agent development itself.

Highlights

• Documentation Structure Refinement: The documentation directories for both development and stable versions have been renamed from agent-development to agent-integration to better reflect the focus on integrating existing agents rather than developing them from scratch.
• Terminology Update: Key terms within the documentation, specifically in the overview.mdx files, have been updated from 'Agent Development SDK (Python)' to 'Server SDK (Python)' and 'Agent Stack SDK' to 'Server SDK' to align with the new emphasis on integration.
• Configuration File Adjustment: The docs.json configuration file has been modified to update all internal references to the documentation pages, ensuring they point to the newly renamed agent-integration paths.

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 refactors the documentation to align with the new naming convention, changing 'Agent Development SDK' and 'Agent Stack SDK' to 'Server SDK'. It also renames the agent-development documentation directories to agent-integration. The changes in the modified files are correct and consistent with this goal.

However, to ensure full consistency, several occurrences of the old 'Agent Stack SDK' name should be updated to 'Server SDK' in the following files:

• docs/development/agent-integration/agent-settings.mdx: line 18
• docs/stable/agent-integration/agent-settings.mdx: line 18
• docs/development/agent-integration/env-variables.mdx: line 22
• docs/stable/agent-integration/env-variables.mdx: line 22
• docs/development/agent-integration/error.mdx: line 8
• docs/stable/agent-integration/error.mdx: line 8
• docs/development/agent-integration/forms.mdx: lines 21, 97
• docs/stable/agent-integration/forms.mdx: lines 21, 97
• docs/development/agent-integration/messages.mdx: lines 12, 14
• docs/stable/agent-integration/messages.mdx: lines 12, 14
• docs/development/agent-integration/secrets.mdx: line 22
• docs/stable/agent-integration/secrets.mdx: line 22

Applying these changes will complete the refactoring and make the documentation fully consistent with the new terminology.