GitHub issue closeout race-safe pattern Use when: - closing issues after verification or implementation - multiple agents/terminals may act on the same issue - the closeout comment is important evidence and must not be lost Problem is convenient, but in live multi-agent use the comment can be lost if the issue becomes closed before the command lands cleanly. Safe pattern 1. Post the evidence comment first. 2. Close the issue as a separate command. Why this works - The closeout evidence becomes durable even if a separate process closes the issue moments later. - It avoids silent loss of the mo…