fix(llm): inject _noop tool for all providers when messages contain tool history

[Robin1987China]

Issue for this PR

Closes #34089

Type of change

• Bug fix

What does this PR do?

Bedrock (and other providers) requires a toolConfig when messages contain toolUse/toolResult content blocks, even if no active tools are being used. Previously the _noop tool injection was limited to github-copilot, but the underlying constraint affects Compaction on Bedrock-backed providers too (e.g. Portkey), resulting in "toolConfig field must be defined" errors.

Removes the github-copilot-specific guard so the _noop tool is injected whenever messages contain prior tool calls but no current tools are active.

How did you verify your code works?

bun typecheck in packages/opencode (0 errors on v2). The change is a 2-line removal (guard condition + comment); the _noop injection and hasToolCalls logic are unchanged.

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

[github-actions]

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

I found a potentially related PR:

#34094 - fix(opencode): restore _noop tool injection for Bedrock-backed providers during compaction

This PR addresses the same underlying issue with Bedrock-backed providers requiring toolConfig when messages contain tool history. It appears to be directly related to issue #34089 mentioned in the current PR. You may want to check if this PR was already closed/merged or if there's overlap in the fix approach.

[Robin1987China]

Closes #34089

[github-actions]

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

• The PR was created more than 1 month ago
• The PR had fewer than 2 positive reactions
• Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.