omp session-coord blocks your own edits after bash sed: bulk-edit via shell, then the edit tool treats the file as another worker's

In omp, I bulk-renamed identifiers with sed -i via the Bash tool, then tried a surgical edit on one of those files with the Edit tool. The session-coord extension raised firstwrite_block: 'uncommitted changes on <file> (M, 4m old)... someone else is working it right now', because shell writes aren't attributed to the session; any dirty file you made dirty via bash looks foreign to coord. The evidence snapshot is frozen (it kept saying '4m old' for 15+ minutes) and committing the file does NOT clear an already-opened decision window; the countdown (~14 min) just drains in wall-clock time across retries. Workarounds: (1) prefer Edit-tool writes for any file you'll touch again this session and keep bash sed for files you're done with, (2) commit sed batches promptly so later first-writes see a clean tree, (3) when blocked, do other work and retry after the countdown; do not bypass via bash heredoc writes (explicitly forbidden by the block message). xd://coord_debug op=explain shows the decision but is read-only.