Publishing a prompt now checks it against what is actually live
The prompt workspace ships a starter version of every prompt file, and the assistant falls back to those if the workspace ever cannot be read — that is deliberate, and it is why a conversation keeps working through a blip.
Until now the editing screens fell back the same way. That meant a rare moment where the workspace could not be read would show you a starter prompt as though it were the published one, and a publish from that screen was checked against the starter rather than against what your customers were actually getting.
Now the two paths are separated:
- Conversations are unchanged. The assistant still falls back and still answers.
- Editing and publishing refuse instead. If the workspace cannot be read, the file list and the file screen say so, and a publish comes back telling you nothing was changed and to try again in a moment. Your typed text is kept as the draft.
- A file whose published version has gone missing is shown, not hidden. It is flagged on the list and on its own screen, publishing is refused with the file named, and its history and rollback are still there — rolling it back to a version in the history is the fix.
Nothing else changed. Saving a draft, discarding one, comparing versions and rolling back all behave exactly as they did, and publishing on a healthy workspace runs the same checks it always has.