Background
Verification feedback (recurred in 3 independent sessions, 2026-07): when a pause-point marker resolves to a statement that spans multiple physical lines (typically a multi-line Debug.Assert( call), ResolvedLineText in the response contains only the first physical line. Agents reading the response see a truncated fragment like Debug.Assert( and get confused about what the marker actually landed on.
Impact
Confusion only — ResolvedMethod already provides enough context to recover, and agents do not misbehave because of this. That is why it was deferred from the Round 13-14 leftover work.
Proposed direction
Resolve the logical line: from the statement's starting line through the matching closing parenthesis/semicolon, and return that (possibly normalized to one line) as ResolvedLineText.
Why it was deferred
Implementation risk is higher than it looks: bracket matching over raw source must handle parentheses inside string literals and comments. Cost was judged heavier than the benefit relative to the other leftovers, so it was parked rather than bundled into the 2026-07-29 round.
Adjudication history: deferred as a mid/low-priority item during the pause-point verification feedback triage (Rounds 13-14 leftovers, 2026-07-29).
Background
Verification feedback (recurred in 3 independent sessions, 2026-07): when a pause-point marker resolves to a statement that spans multiple physical lines (typically a multi-line
Debug.Assert(call),ResolvedLineTextin the response contains only the first physical line. Agents reading the response see a truncated fragment likeDebug.Assert(and get confused about what the marker actually landed on.Impact
Confusion only —
ResolvedMethodalready provides enough context to recover, and agents do not misbehave because of this. That is why it was deferred from the Round 13-14 leftover work.Proposed direction
Resolve the logical line: from the statement's starting line through the matching closing parenthesis/semicolon, and return that (possibly normalized to one line) as
ResolvedLineText.Why it was deferred
Implementation risk is higher than it looks: bracket matching over raw source must handle parentheses inside string literals and comments. Cost was judged heavier than the benefit relative to the other leftovers, so it was parked rather than bundled into the 2026-07-29 round.
Adjudication history: deferred as a mid/low-priority item during the pause-point verification feedback triage (Rounds 13-14 leftovers, 2026-07-29).