A stray end after an earlier statement was reported with the span of the previous payload (position-1) and a confusing 'ends outside its owning function segment' message. Report it on the end payload itself with the standard sem.unmatched_end wording, and pin the span with a unit test. Verified: clippy -D warnings clean and cargo test --workspace --locked green (62 targets).