fix: handle paths outside repository

[Totoro-qaq]

Fixes #5620

Summary

• treat paths that cannot be normalized relative to the repository as untracked
• prevent path_in_repo() and its is_dirty(path) caller from propagating ValueError
• add a cross-platform regression test using an absolute path outside the temporary repository

Tests

• pytest -q tests/basic/test_repo.py::TestRepo::test_path_outside_repo_is_not_tracked
• pytest -q tests/basic/test_repo.py
• pre-commit run --files aider/repo.py tests/basic/test_repo.py

[kvnloo]

Live check on main 5dc9490: aider/repo.py normalize_path does Path(self.root)/path then relative_to(self.root), which raises ValueError for an absolute path outside the repo. ignored_file already catches that (returns True). path_in_repo at 574 does not. is_dirty(path) calls path_in_repo first, so an outside path never reaches "untracked => dirty"; it crashes.

PR head ef446b9 wraps normalize_path in path_in_repo, returns False on ValueError. is_dirty then returns True. TestPathOutsideRepoIsNotTracked uses Path.cwd().parent/"outside.txt" under GitTemporaryDirectory. That is the right pin.

I would merge. Optional follow-up, not blocking: the same relative_to hole is still live in whatever other callers skip the try (abs_root_path does not use relative_to).

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ Totoro-qaq
❌ impartshadow
_{You have signed the CLA already but the status is still pending? Let us recheck it.}