refactor(tool): name webfetch execute effect

[Astro-Han]

Summary

Names the webfetch tool execute Effect boundary with Effect.fn("WebFetchTool.execute").

Why

This continues the #936 non-UI backend Effect migration slices by aligning webfetch.ts with the already-merged tool execute tracing pattern used by grep, write, and edit. The tool behavior stays unchanged.

Related Issue

Part of #936.

Human Review Status

Pending

Review Focus

Please verify that the Effect.fn("WebFetchTool.execute") wrapper preserves the existing webfetch validation, permission, header, fallback, size-limit, output, and error semantics.

Risk Notes

No behavior change intended. The diff only names the execute trace boundary. Skipped conditional checklist items: no visible UI or copy changed; no platform, packaging, updater, signing, path, shell, or permission surface changed; no docs, release notes, dependencies, credentials, deletion behavior, generated content, or local file changes were introduced.

How To Verify

Baseline focused test: bun test test/tool/webfetch.test.ts — 7 pass on origin/dev before the change
Focused test: bun test test/tool/webfetch.test.ts — 7 pass after the change
Typecheck: bun run typecheck — passed in packages/opencode
Diff check: git diff --check — passed
Fresh-eye review: no findings; recommended proceed
Claude read-only review: no findings; confirmed the change is the simplest safe pattern

Screenshots or Recordings

Not applicable: no visible UI or copy changes.

Checklist

How to use this checklist:

• Tick a box by replacing [ ] with [x]. Do not edit, add, or remove items.
• The bot-applied label items can only be honestly ticked AFTER the PR is opened and the labeler / priority-triage bots have run — return to the PR description and tick them then.
• Most items are required. The few that are conditional are explicitly marked (conditional); for those, leave unticked if they truly do not apply and explain why in Risk Notes. All other items must be ticked before requesting human review.

• Type label — this PR carries exactly one of bug, enhancement, task, documentation. Type labels are author-added; the labeler bot does NOT assign them. Add the label in the GitHub UI, then tick this.
• Routing labels — this PR carries at least one of app, ui, platform, harness, ci. The labeler bot assigns these on PR open based on changed paths. Confirm the bot's choice (or override if wrong), then tick this.
• Priority label — this PR carries exactly one of P0, P1, P2, P3. The priority-triage bot suggests one on PR open. Confirm or override, then tick this.
• Human Review Status above is set to Pending, Approved by @<reviewer>, or Not required: <reason> (default is Pending; "not required" is restricted to bot-authored low-risk PRs).
• I linked the related issue, or stated in Summary why there is no issue.
• I described the review focus and any meaningful risks.
• I replaced the example block in How To Verify with the real verification steps and the key result for each.
• I did not introduce unrelated refactors, dependencies, generated files, or file changes beyond the stated scope.
• (conditional) I manually checked visible UI or copy changes when needed, with screenshots or recordings. Leave unticked only if no visible UI or copy changed.
• (conditional) I considered macOS and Windows impact for platform, packaging, updater, signing, paths, shell, or permissions changes. Leave unticked only if no platform/packaging surface was touched.
• (conditional) I called out docs, release notes, dependencies, permissions, credentials, deletion behavior, generated content, or local file changes when relevant. Leave unticked only if none of those surfaces was touched.
• I reviewed the final diff for unrelated changes and suspicious dependency changes.
• I am targeting dev, and my PR title and commit messages use Conventional Commits in English.

Summary by CodeRabbit

• Refactor
  • Updated internal implementation of the web fetch tool to improve code organization and maintainability.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: c9da5608-e6e9-48c4-899d-d4231cd60714

📥 Commits

Reviewing files that changed from the base of the PR and between 3571ee3 and 702bda4.

📒 Files selected for processing (1)

• packages/opencode/src/tool/webfetch.ts

---

📝 Walkthrough

Walkthrough

This change wraps WebFetchTool.execute in Effect.fn("WebFetchTool.execute") and adjusts the surrounding closure syntax in the same file, while keeping the existing handler body and behavior intact.

Changes

WebFetch execute wrapper

Layer / File(s)	Summary
Named execute wrapper packages/opencode/src/tool/webfetch.ts	WebFetchTool.execute is now declared through Effect.fn("WebFetchTool.execute"), with the wrapper opening and closing added around the existing handler implementation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

Possibly related PRs

• Astro-Han/pawwork#1288: Also wraps a tool execute handler in a named Effect.fn("<Tool>.execute") pattern in another tool module.

Suggested labels

task, tech-debt

Poem

🐇 I wrapped a web-fetch spell just so,
With Effect.fn to help it glow.
The hopping code still runs the same,
But now it bears a clearer name.
Carrot cheers for tidy trails!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately describes the main change: naming the webfetch execute Effect boundary.
Description check	✅ Passed	The description matches the required template and includes summary, rationale, issue link, review focus, risks, verification, and checklist.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/i936-tool-webfetch-effect

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint install failed. For unrecoverable errors, disable the tool in CodeRabbit configuration.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Suggested priority: P2 (includes non-doc, non-test paths outside the low-risk bucket).

P1/P0 are reserved for maintainer confirmation. Please relabel manually if this is a release blocker, security issue, data-loss risk, or updater/runtime failure.

[gemini-code-assist]

Code Review

This pull request updates the WebFetchTool in packages/opencode/src/tool/webfetch.ts by wrapping its execute function with Effect.fn("WebFetchTool.execute"). This change integrates the execution logic with Effect's function wrapper, likely for improved telemetry, debugging, or error handling. No review comments were provided, and there is no additional feedback to address.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.