refactor: move web_fetch tool name to tool-names.ts

[abhipatel12]

TLDR

This PR moves the hardcoded 'web_fetch' string used for the Web Fetch tool name into the centralized packages/core/src/tools/tool-names.ts file as WEB_FETCH_TOOL_NAME. It updates the tool implementation, policy configuration, and tests to use this exported constant.

This should be a no-op

Reviewer Test Plan

This is a refactor with no functional changes. Verification relies on the build and test suite.

1. Checkout this branch.
2. Run npm run build to verify there are no TypeScript errors related to imports or variable usage.
3. Run npm run test to ensure all tests pass, specifically packages/cli/src/config/policy.test.ts which was modified.
4. (Optional) Run npm run preflight for a comprehensive check.

Testing Matrix

	🍏	🪟	🐧
npm run	✅	❓	❓
npx	❓	❓	❓
Docker	❓	❓	❓
Podman	❓	-	-
Seatbelt	✅	-	-

[gemini-code-assist]

Summary of Changes

Hello @abhipatel12, 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 focuses on improving code maintainability and consistency by centralizing the definition of the 'web_fetch' tool name. By replacing a hardcoded string with an exported constant, it ensures that all references to this tool name are consistent and easily manageable from a single source, reducing the risk of typos and simplifying future updates.

Highlights

• Centralized Tool Name Definition: The hardcoded string 'web_fetch' has been moved into a new constant, WEB_FETCH_TOOL_NAME, defined in packages/core/src/tools/tool-names.ts.
• Consistent Usage Across Files: The newly defined WEB_FETCH_TOOL_NAME constant is now used consistently across the Web Fetch tool implementation, policy configuration, and related test files.
• No Functional Change: This pull request is a pure refactor and is expected to be a no-op, meaning it introduces no functional changes to the application's behavior.

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 successfully refactors the hardcoded 'web_fetch' tool name into a centralized constant, WEB_FETCH_TOOL_NAME. The changes are applied consistently across the tool implementation, policy configuration, and related tests. This is a good practice that improves maintainability by eliminating magic strings. The implementation is correct and I have no issues to report.

[github-actions]

Size Change: +141 B (0%)

Total Size: 17.8 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	17.8 MB	+141 B (0%)
./bundle/sandbox-macos-permissive-closed.sb	1.03 kB	0 B
./bundle/sandbox-macos-permissive-open.sb	830 B	0 B
./bundle/sandbox-macos-permissive-proxied.sb	1.31 kB	0 B
./bundle/sandbox-macos-restrictive-closed.sb	3.29 kB	0 B
./bundle/sandbox-macos-restrictive-open.sb	3.36 kB	0 B
./bundle/sandbox-macos-restrictive-proxied.sb	3.56 kB	0 B

_{compressed-size-action}