Absolute-path permission rules never match (tool patterns are worktree-relative)

Permission rules written as absolute paths never take effect. Tools produce patterns via path.relative(worktree, filePath), so a path like /czk/mem/facts/me.md in a project at /czk/mem arrives as:

• inside the worktree: facts/me.md (relative)
• outside the worktree: ../../czk/... (traversal)
• no git context: czk/... (de-rooted)

So a rule like {"edit": {"/czk/**": "allow"}} can never match, and users get repeated permission prompts despite having allowed the path.

Expected: absolute rules match the actual file path. Actual: only the relative form is evaluated (packages/opencode/src/permission/index.ts, evaluate()).

Seen on v1.18.30 (dev @ f69bece).