enable-pause-point: state which source basis (edited file vs last-compiled source) resolved --line

[hatayama]

Background

Usability-feedback round 24 (2026-08-24, revision 9cefd73). Reported at 4/10 with 2 wasted round trips.

Problem

After a hot reload, line targeting has a documented dual basis: methods patched in the last reload resolve --line against the edited file, while unpatched methods resolve against the last compiled source. The hot-reload response warns about this ("line count differs from the last compiled source ..."), but the enable-pause-point response itself never says which basis it actually used. The user must remember the warning from an earlier command and re-derive which case applies, re-grepping line numbers (2 round trips observed).

Proposal

Add a field (or extend an existing note) in the enable-pause-point response stating the resolution basis explicitly, e.g. LineBasis: "edited file (method is hot-reload patched)" vs "last compiled source". This makes each response self-explanatory and removes the need to carry the hot-reload warning across commands.

Severity

4/10 (correct guidance exists, but it lives in a different command's response).

[hatayama]

Additional field report (verification round R25, block-breaker project, severity 4/10 self-scored by the tester):

After hot-reloading GameManager.cs (edited 234 lines vs compiled 233), targeting the un-patched method OnBlockDestroyed required mentally subtracting 1 from the editor-visible line number (edited line 89 -> compiled line 88; the edited file's line 88 was blank). The warnings were accurate and the shot landed first try, but the tester had to decide the coordinate system themselves — the editor-visible line number matched neither basis directly.

Tester proposals worth considering for this issue:

• --line-basis edited|compiled to state the coordinate system explicitly
• a line-number-free anchor such as --statement "hud.Render("
• minimal option: when a --line on an un-patched method resolves against the compiled source, return SuggestedLine (the line in the edited file carrying the same statement) so the mental arithmetic disappears

The tester also noted the practical workaround that emerged: run uloop compile once before entering a fine-grained pause-point phase to collapse the two coordinate systems back into one.

[hatayama]

Resolved by PR #2409 (squash ea30b1e on v3-beta).

Successful --file/--line enables now report LineBasis: EditedFile when the line was resolved against the edited file (inside a hot-reload patched method), LastCompiledSource when it was resolved against the last compiled source — including when no hot reload has run. The field also propagates through --await hit responses and Expired error Details. It is intentionally absent from id-path enables and from the pause-point-status contract.