Conversation
thymikee
force-pushed
the
codex/issue-385-export-finders
branch
from
d7799fe to
0e0690a
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
agent-device/finderssubpath and rslib entrypoint.parseFindArgsinto the pure finder utility layer while preserving the old handler export for tests/internal callers.normalizeRole,normalizeText, and the booleanrequireRectpublic wrapper forfindBestMatchesByLocator.Touched files: 6. Scope stayed within finder export surface. Docs/skills were not updated because this is a library API export, not CLI behavior.
Closes #385
Validation
pnpm installpnpm formatpnpm check:toolingpnpm vitest run src/__tests__/finders-public.test.ts src/utils/__tests__/finders.test.ts src/daemon/handlers/__tests__/find.test.tsKnown gaps: none.