Update README with service verification instructions

[djarecka]

Added note about verifying Query and ML Services.

[gemini-code-assist]

Summary of Changes

Hello @djarecka, 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 improves the project's documentation by adding essential verification instructions for the Query and ML Services. The update aims to prevent user confusion by guiding them to the correct /docs endpoint to confirm the operational status of these services, rather than the base URL.

Highlights

• README Update: Added a crucial note to the readme.md file, providing specific instructions on how to verify the Query and ML Services. This clarifies that direct access to http://localhost:<port> for these services will not show anything, and users should instead navigate to http://localhost:<port>/docs.

🧠 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 updates the README.md to include instructions for verifying the Query and ML services. The addition is helpful for developers setting up the project locally. I've provided one suggestion to make the instructions even clearer by replacing the generic <port> placeholder with the specific default URLs for the service documentation pages, which enhances usability.

[gemini-code-assist]

The note is helpful, but using <port> is a bit vague. Since the default ports are listed just above, it would be more user-friendly to provide the full, direct links to the documentation pages. This avoids ambiguity and makes verification easier for users following the quick start guide.

Suggested change

	**Please note:** for the Query Service and ML Service, you won’t see anything at `http://localhost:<port>`. To verify that the services are running, open `http://localhost:<port>/docs` instead.
	**Please note:** for the Query Service and ML Service, you won’t see anything at their base URLs. To verify they are running, open their API docs at `http://localhost:8010/docs` and `http://localhost:8007/docs` respectively.