impact / path: a file:line past the end of the file (or line 0) answers as the file's top-level code #1601

What happens

A file:line whose line number is outside the file answers as the file's top-level code, as if the line existed:

$ wc -l src/services/userService.js
4
$ axiomcode impact src/services/userService.js:99
change: userService.<module> (at src/services/userService.js:99)   [method]
$ axiomcode path '*' src/services/userService.js:0
everything that can reach userService.<module> (top-level code at src/services/userService.js:0): 0 method(s)

This happens for line 0 and for any line past the end, with impact and path and with dotted and undotted file names. A stale line number is common: the file was edited after the number was copied, or the number came from an old stack trace. The answer looks like a real result about module-level code, so nothing tells the reader that the target was wrong.

Expected

For a line below 1 or past the file's last line, refuse and give the file's length, e.g. src/services/userService.js has 4 lines; line 99 is not in it.