fix(core): break circular import between filesystem and filesystem/search

[winter765]

filesystem.ts reads FileSystemSearch.node while it initializes, while filesystem/search.ts imported FileSystem back from ../filesystem at runtime for the Entry/Match constructors.

A bundler is free to emit either module first. When filesystem.ts wins, FileSystemSearch.node is still undefined and is stored in its layer dependencies, so LayerNode.hoist throws TypeError: undefined is not an object (evaluating 'a.name') on every startup.

Repro: bun run script/build.ts --single on bun 1.4.2 produces a binary that fails at init for every prompt. bun 1.3.14 happens to emit the modules in the other order, which is why this is currently latent.

Entry/Match are re-exports of @opencode-ai/schema/filesystem, so importing them from there removes the runtime edge. The remaining ../filesystem import is type-only.

[github-actions]

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

• PR description is missing required template sections. Please use the PR template.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

[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:

Based on the search results, I found a potential duplicate:

• PR fix(core): break filesystem/search import cycle #48877 - fix(core): break filesystem/search import cycle
  • fix(core): break filesystem/search import cycle #48877

This PR appears to address the exact same issue: breaking the circular import cycle between filesystem.ts and filesystem/search.ts. Since PR #49118 (the current PR) has nearly identical scope and title, you should check if #48877 is still open and whether it has already been merged or closed. If it's open, one of these PRs may be redundant.

[github-actions]

This pull request has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new pull request that follows our guidelines.