codeSplitters: a line edit in a dug repo never landed, with no error shown #659

Seen by the owner while testing #609, on the live site at edd5c23.

What happened: two accounts had quinn/rustybuns README.md open side by side (@quinn, and @theqntbr as crew). @theqntbr double-clicked line 3, typed asdasd, and pressed Enter. @quinn's window never showed the change. Reading the file from the server afterwards (read_file) gave rev 146, line 3 unchanged, and every line still by: upstream, so the edit never reached the file's Durable Object. @theqntbr's window gave no error; the line stayed open in its edit box ("limbo").

Other live updates in the same windows worked: toggling the repo between private and public showed up in the other window right away, and earlier typing in a small new repo (pulse-test) landed (Pulse counted it).

Suspects: rustybuns is a dig of the GitHub repo (digs last 24 hours) with a large tree; the edit may have been refused (a 409 on a stale rev, a crew or dig write rule) or sent on a socket that had dropped, and the client swallowed it.

Fix:

• find why the save didn't land (try a crew edit on a dug repo against a local build)
• a save that fails or gets no ack must say so on the line (and offer to retry), never sit silently in the edit box

🤖 Generated with Claude Code