fix(resolve-file-uri): remove project boundary check for prompt file:// URIs

[nerored]

Summary

Remove the isWithinProject boundary restriction from resolvePromptAppend() so that file:// prompt URIs behave as documented — supporting absolute, home-relative (~/), and project-relative paths — instead of being silently rejected with a [WARNING: Path rejected: ...] placeholder.

Root Cause

Since commit 9865978 ("fix(security): confine file resolution to project roots"), resolvePromptAppend() has called isWithinProject(filePath, configDir ?? process.cwd()) and rejected any path that resolves outside the current working directory or config directory.

This contradicts the configuration reference which explicitly documents support for all three forms:

Paths can be absolute (file:///abs/path), relative to project root (file://./rel/path), or home-relative (file://~/home/path).

The same documentation also describes cross-project prompt sharing as a primary motivation for file:// support. The boundary check makes this impossible when the prompt file lives in a shared global directory (e.g. ~/.config/opencode/prompts/).

The check was added for security, but prompt and prompt_append are user-configured fields — the user is deliberately pointing to a file they want loaded into the agent prompt. Other parts of the codebase (skill loader, config discovery) already have their own isWithinProject guards where project isolation is genuinely needed.

Changes

File	Change
src/agents/builtin-agents/resolve-file-uri.ts	Remove isWithinProject import, log import, and the boundary check block.
src/agents/builtin-agents/resolve-file-uri.test.ts	Remove 3 rejection tests, add 1 cross-boundary test, update home-directory test.

Verification

bun test src/agents/builtin-agents/resolve-file-uri.test.ts  → 8 pass / 0 fail
bun test src/agents/sisyphus-junior/index.test.ts             → 47 pass / 0 fail
bun run typecheck                                              → clean

Related

• [Bug]: file:// prompt and prompt_append paths are documented as supporting absolute/home paths, but are rejected outside the current project boundary #3554 — bug report describing the docs-vs-implementation gap
• fix(resolve-file-uri): explain project boundary restriction in rejection warning (fixes #3554) #3679 — improved the rejection warning but preserved the restriction
• Configuration Reference — documents file:// support for absolute / ~/ / relative paths

---

^{Need help on this PR? Tag @codesmith with what you need.}

• Let Codesmith autofix CI failures and bot reviews

---

Summary by cubic

Remove the project boundary check from resolvePromptAppend() so file:// prompt URIs can load absolute, home (~/), and project‑relative files as documented. This removes false “[WARNING: Path rejected]” and enables cross‑project prompt sharing.

• Bug Fixes
  • Removed project-root restriction in resolvePromptAppend() so absolute paths load regardless of configDir.
  • Kept warnings for malformed URIs and missing files; updated tests to remove boundary‑rejection cases and add cross‑boundary/home‑dir success cases.

^{Written for commit 0152818. Summary will update on new commits.}

[github-actions]

All contributors have signed the CLA. Thank you! ✅
_{Posted by the CLA Assistant Lite bot.}

[nerored]

I have read the CLA Document and I hereby sign the CLA

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Requires human review: Removing a security boundary check (isWithinProject) previously added to prevent arbitrary file access is a security regression, even if it aligns with documentation.}