>Hmm, I'd argue that you want the behavior to be consistent. The formatters should spit out _project-relative_ paths; and the includes/excludes should act against those same paths.
>
>Much easier for someone to debug & understand, IMO. Least surprise and all that.

I didn't say “change the behavior” (at least for now). I meant that `#smart_path`, which is originally named and implemented for displaying paths for humans, should not be used as-is in an internal logic without renaming properly (or being delegated by another good name method).