fix(permission): use absolute paths for external file permission matching

[kevinWangSheng]

Issue for this PR

Closes #18441

Type of change

• Bug fix

What does this PR do?

The edit, write, and apply_patch tools send permission check patterns as relative paths from the worktree (e.g. ../../.config/opencode/file.txt). Meanwhile, user-defined permission rules in config are expanded to absolute paths (e.g. /Users/x/.config/opencode/** after ~/ expansion in Permission.fromConfig()).

Wildcard.match() compares these two different formats and never matches, so edit/write rules for external files silently fall through to the default { permission: "*", pattern: "*", action: "allow" } rule — bypassing any user-specified "ask" or "deny" restrictions.

The fix checks whether the target file is inside the worktree via Instance.containsPath():

• Internal files: keep relative paths (preserves existing behavior and matches relative config patterns like "src/**")
• External files: use absolute paths (correctly matches expanded config rules like "/Users/x/.config/**")

This is consistent with how assertExternalDirectory() already sends absolute glob patterns for the external_directory permission check.

How did you verify your code works?

• bun run typecheck passes (all 13 packages)
• Traced the permission evaluation flow: with this fix, an external file path like /Users/x/.config/opencode/settings.json now correctly matches a config rule { "edit": { "~/.config/opencode/**": "ask" } } (expanded to /Users/x/.config/opencode/**)
• Internal files (inside worktree) remain unchanged — relative paths still match relative config patterns

Screenshots / recordings

N/A

Checklist

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

[rekram1-node]

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.