ADR-004: Working directory and default scope

[UltraBob]

Summary

• HostWorkingDir: true on every command; config discovery follows each tool's stock behavior
• Position-aware default scope: project root scans custom directories, anywhere else scans cwd
• --stdin-path gating prevents IDE linting from triggering full-project scans
• Absorbs the host-path alias idea from PR Add host-path alias symlink startup hook and validation coverage #21 as a separate deliverable with cross-platform testing as a prerequisite
• PR Add host-path alias symlink startup hook and validation coverage #21's path-map.sh rewrite deferred until alias is verified on macOS, Linux, and Windows/WSL2
• Missing-config error messages from PR Add host-path alias symlink startup hook and validation coverage #21 can land independently

Relationship to PR #21

PR #21 bundles the host-path alias with several unrelated changes. This ADR recommends absorbing its ideas as separate 2.x changes rather than merging the PR as-is. See the "What to absorb from PR #21" and "Risks of the alias approach" sections.

Review checklist

• Does the position-aware default scope (root = custom dirs, elsewhere = cwd) match your expectations?
• Is the --stdin-path gating clear?
• Are the four prerequisites reasonable before enabling HostWorkingDir?
• Is the phased approach for the host-path alias (keep path-map.sh fallback, test cross-platform first) acceptable?
• Any concerns about the risks listed for the alias approach?

[UltraBob]

@mandclu #4/10

[mandclu]

At a high level I think scanning the custom directories when called from the root, and the cwd anywhere else makes perfect sense.

I'm not sure I understand the alias risks.