fix(config): load directory tool sources on Windows (#150)

[ajshedivy]

Summary

Fixes #150 — on Windows, --tools <directory> discovered no tool YAML files, so no tools loaded.

Root cause

ToolConfigBuilder.resolveDirectoryPaths built its glob pattern with path.join():

const pattern = join(resolvedDir, "**/*.{yaml,yml}");
// Windows → c:\users\...\tools\**\*.{yaml,yml}   (backslashes!)
return glob.sync(pattern, { absolute: true });

glob (v10) requires forward-slash-only patterns. On Windows it treats backslashes as escape characters, not path separators, so the pattern matched nothing and no tools were registered.

Fix

Pass the resolved directory through glob's cwd option (a filesystem path, where native separators are fine) and keep the pattern forward-slash only:

return glob.sync("**/*.{yaml,yml}", { cwd: resolvedDir, absolute: true });

The same join()-into-pattern bug existed in resolveGlobPaths when baseDir was set, so it gets the same cwd-based treatment. Behavior is unchanged on macOS/Linux and when baseDir is omitted (glob defaults cwd to process.cwd()).

Testing

• New toolConfigBuilder.pathResolution.test.ts covering directory + glob source resolution (nested files, non-YAML exclusion, missing-directory and no-match error paths).
• End-to-end check: resolveDirectoryPaths/resolveGlobPaths both discover all 9 YAML files across the repo's nested tools/ subdirectories.
• npm run typecheck, npm run lint, and the full npm test suite (543 tests) pass.