Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/claude-code-plugin/__tests__/rdpath-find-integration.test.ts`:
- Around line 42-44: The current proc.on('close', (code) => resolve({ stdout,
stderr, exitCode: code ?? 0 })) masks signal-based termination by treating null
code as success; update the handler in the test to use a non-zero default (e.g.,
exitCode: code ?? 1) and/or accept the second parameter (signal) from
proc.on('close', (code, signal) => ...) and include that signal in the resolved
object so tests can distinguish normal exits from killed processes.

In `@packages/claude-code-plugin/src/rdpath.ts`:
- Around line 12-18: The import/command block (symbols assemblePath, findFiles,
RdPathFindOptions, RdPathOptions, getErrorMessage, Command, program, pathCmd) is
misformatted according to the project's formatter; run the project's formatter
(npm run format) or apply the repo's formatting rules to this section so the
import lines and Command setup follow the configured style (fix spacing,
semicolons/newlines as needed) and commit the formatted file to resolve the CI
pipeline failure.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/claude-code-plugin/src/rdpath-core.ts`:
- Around line 114-140: findings: findFiles() currently allows absolute glob
patterns (which bypass cwd scoping) and includes directories in results,
violating the JSDoc that promises "matching file paths". Fix: first reject
absolute patterns (use path.isAbsolute(pattern) and throw a clear error) in
addition to the existing TRAVERSAL_PATTERN check; then when iterating glob
results from fs.glob(pattern, { cwd: absoluteDir }), ensure only files are
returned by either passing a nodir-like option to fs.glob if available or by
stat-ing each absoluteMatch (using fs.stat or fs.lstat) and skipping entries
where stat.isDirectory() is true; keep the isPathInside(absoluteDir,
absoluteMatch) validation and push path.join(resolvedDir, match) only for
verified file matches so matches[] contains only files.

---

Duplicate comments:
In `@packages/claude-code-plugin/__tests__/rdpath-find-integration.test.ts`:
- Around line 42-44: The test harness currently maps a null exit code to 0 in
the proc.on('close', (code) => resolve({ stdout, stderr, exitCode: code ?? 0 }))
callback, which treats signal-terminated processes as successful; change the
logic in runRdpath (the proc.on('close' handler) to treat code === null as
failure by setting exitCode to a non-zero value (e.g., 1) and include the signal
in the resolved object (resolve({ stdout, stderr, exitCode: code !== null ? code
: 1, signal })) so signal terminations are not masked as success.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/claude-code-plugin/__tests__/rdpath-core.test.ts`:
- Around line 203-233: Add a new test in rdpath-core.test.ts that creates a
dangling symlink inside testDir (symlink pointing to a non-existent target),
calls findFiles({ dir: testDir }, '*.md'), and asserts the expected behavior
(either that the dangling symlink is excluded or included according to project
convention); use the same pattern as the existing symlink tests (create files
with fs.writeFile / fs.symlink, call findFiles, and use
expect(results).toEqual(...) or expect(...).not.toContainEqual(...)) and
reference testDir and findFiles so the regression for broken links is pinned.

In `@packages/claude-code-plugin/src/rdpath-core.ts`:
- Around line 141-146: The glob loop that calls fs.realpath and fs.lstat (inside
the for-await over fs.glob with pattern/absoluteDir and using variables
absoluteMatch, realMatch, stat) needs a try-catch so a single FS error doesn't
abort findFiles; wrap the fs.realpath(realMatch) and fs.lstat(realMatch) calls
in a try block, catch errors and use the existing isNodeError(err) helper to
check err.code and continue the loop for expected recoverable codes (ENOENT,
EACCES, EPERM, ELOOP), but re-throw the error for anything else so unexpected
failures still surface.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/claude-code-plugin/__tests__/rdpath-core.test.ts`:
- Around line 108-112: Add a new test in rdpath-core.test.ts that exercises the
"existing path but not a directory" branch by calling findFiles with dir set to
a path that exists as a file (e.g., path.join(testDir, 'someFile.txt')) and
asserting the promise rejects with the "Not a directory" error; locate the
existing test named 'throws for nonexistent directory' and add a sibling it(...)
that uses await expect(findFiles({ dir: path.join(testDir, '<filename>' ) },
'*.md')).rejects.toThrow('Not a directory') to pin the Not a directory branch in
the findFiles codepath.

In `@packages/claude-code-plugin/src/rdpath-core.ts`:
- Around line 104-108: The TSDoc for findFiles omits the error case where the
provided dir exists but is not a directory; update the findFiles docblock to add
a `@throws` entry describing that an Error is thrown when the path specified by
options.dir exists but is not a directory (e.g., "When dir exists but is not a
directory"). Locate the JSDoc/TSDoc immediately above the findFiles function
declaration and add the concise `@throws` clause alongside the existing throws
about invalid ctx, traversal patterns, and missing directories so the exported
API contract accurately documents all failure paths.