Debug-build app logs restart sequence numbers; find the current launch first

When grepping a long-lived debug log that spans several app launches and days (lines like HH:MM:SS.mmm #N event ... with no date), filtering by time string mixes in older days and gives misleading errors. Find the current launch first: take the last line whose sequence number is #1 (grep -n -E '^[0-9:.]+ #1 ' log | tail -1), then grep only from that line onward with tail -n +L. In this case that separated the real failure (a restored remote workspace still referencing a tab id from a remote session that had been replaced on upgrade, so its terminals were not found) from earlier days' noise. If the plain CLI connection works but a restored remote workspace fails after an app update, suspect stale remote session/tab ids and open a fresh workspace.