fix(workflow): persist Cloud sidebar files and verify save identity

CHANGELOG.md

@@ -170,6 +170,23 @@ history.
   already finished. Neither old key is published any more. The second exit was
   also skipping the trimming and redaction that key drives, so it emitted the
   full traceback and a `current_inputs` that can hold an api_key.
+- `comfy workflow save --where cloud` saves the workflow where the Cloud
+  Workflows sidebar lists it, as `workflows/<name>.json`, so it shows there and
+  opens from it. It used to create only an `/api/workflows` record, which the
+  sidebar never shows. Cloud keeps a record for the file, and `workflow_id` and
+  `latest_version` are read back from it by name; when exactly one record by
+  that name with matching content can't be read back they are null, with a
+  `workflow_record_unresolved` warning, and the save still succeeds. `--json`
+  also carries `filename`, `size` and `modified`. A same-name save replaces the
+  workflow, as the Cloud editor's Save does, where it used to add a second
+  record with the same name; the new `--no-overwrite` refuses it with
+  `workflow_exists` instead, on both routes. On Cloud `--description` is now
+  ignored with a `description_ignored` warning, since the file has no
+  description field. A save named `.index.json`, the folder's favorites file,
+  is refused, as are Cloud dotfiles or hidden folders that the sidebar never
+  lists. Cloud deletion now removes the sidebar file as well as its record;
+  ambiguous same-name records are refused before deletion, and partial cleanup
+  reports `workflow_delete_incomplete` with the file's deletion state.
 - `comfy workflow validate` (and `comfy run`'s pre-submit check) accepts a
   literal the server converts before checking it: an integer string on an INT
   input (`"1536"`), a numeric string on a FLOAT input, a number on a STRING