impact: next: says the change is local while the answer lists [by name] callers #1573

Symptom

impact ends with next: nothing resolved depends on it, so the change is local — read <decl> and edit there on an answer that lists [by name] callers of the declaration. Reproduction (TypeScript):

export class Store { lonely(): number { return 1; } }
export function use(s: any): number { return s.lonely(); }

$ axiomcode impact Store.lonely
reads or uses it (2 callable(s): 1 by name, 1 alongside):
    [by name] use   src/store.ts:8   — calls a method of this name (receiver not typed)
next: nothing resolved depends on it, so the change is local — read src/store.ts:2 and edit there; the 1 [by name]/[text] row(s) are leads ...

For the same pair, path use Store.lonely gets it right: "would connect in 1 hop if the unresolved call resolves the way its name suggests — look at src/store.ts:8".

This was seen in JavaScript as well (a method with three [by name] callers, and a module constant read in an object literal), in agent sessions that took "local" at its word. The same next: line also appears in #1552 (Python, tests counted), #1467 and #1468 (Java, entry point and remote caller). This issue covers the language-neutral case: the answer lists callers, even untyped ones, and still calls the change local.

Expected

When the only users are [by name] / [text], next: says that no resolved user was found and names the leads to check (1 by-name caller at src/store.ts:8 — check it before calling the change local), as path does.