Save Draft To Canonical
Changed onPromote a session draft to canonical.
Outside generation: CAS conflict detection (or force=True). During generation, save_to_canonical force-writes the live draft because the draft store is the notebook source of truth for user and agent edits. Either way the draft is preserved on success with a refreshed canonical_base_revision.
Any pending_user_edits are applied first via the same per-cell write path the notebook_cell_user_edit socket handler uses, so an explicit save inside the user edit debounce window is atomic with respect to the user's latest typing.
Autosave requests (autosave=True) no-op during generation instead of inheriting the force-write semantics above, mirroring what save_draft does for draft saves. An autosave flag wins over force — a background save must never bypass CAS.
Request
- Base URLhttps://api.quadrillion.io (the document declares no server; this is the origin it was published from)
- URLhttps://api.quadrillion.io/notebook/draft/save-to-canonical
- Authnone declared
Request body
Response
Successful Response
Changes
- info
added the optional property
//to the response with the status - info
added the optional property
//to the response with the status
- info