chore: regenerate the authorable surface on the merged tree; the released 24298 note is left as main has it

Claude-Session: https://claude.ai/code/session_01Q3mCs3NX4GshNUCh7Fr1b9
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.changeset/24395-draft-changes-surface.md

@@ -8,4 +8,4 @@ Clause-②: yes (widening)
 
 - **One closed set, one name.** `MetadataAuthoringSurfaceSchema` (`copilot | studio | api`) is exported from `@objectstack/spec/api`, with its type `MetadataAuthoringSurface`. `GetMetaItemResponseSchema.draftChanges[].by` now reads it instead of an inline enum: the accepted values are unchanged.
 - **The save states its surface.** `SaveMetaItemRequestSchema` gains an optional `surface` from that set. A draft save stamps it as `by` on each key path it changes; an absent `surface` stamps `api`. On the REST door and the runtime dispatcher it is the `?surface=` query parameter, which takes `studio` or `api` only: `copilot` is stated by an in-process AI tool, never over HTTP.
-- **The writer exists.** The `draftChanges` describe no longer says no server writes it: it states the writer's rules (the first draft save is compared with the stored published row, an item with no stored published row is recorded as `[]`, and a `migrate-stored` rewrite records nothing).
+- **The writer exists.** The `draftChanges` describe no longer says no server writes it: it states the writer's rules (the first draft save is compared with the stored published row, an item with no stored published row is recorded as `[]`, and a `migrate-stored` rewrite records nothing). `18.0.0-next.4`'s note said no server writes `draftChanges` yet; from this release the draft save writes it.

.changeset/pre/24298-draft-key-provenance.md

@@ -8,5 +8,5 @@ Clause-②: yes (widening)
 
 - **The key.** `GetMetaItemResponseSchema` gains an optional `draftChanges` beside `item`: one entry per changed key path of the pending draft body, each `{ path, by, actor, at }`. `path` is an array of the keys from the body root to the deepest key the write changed (`["fields", "renewal_count"]`, `["fields", "renewal_count", "label"]`); an array value is one leaf, so a change to a view's columns is `["columns"]` and never carries an index (which elements differ is read by comparing the array with the published body's; the entry says who last changed the array); `[]` is the whole body of an item created as a draft. `by` is a closed set: `copilot` (an AI assistant's tool writing on a person's behalf), `studio` (a person editing in Studio) or `api` (any other caller of the save door). `actor` is the write's recorded identity or `null`, and `at` its ISO-8601 instant.
 - **Where it is served.** Only on the strict draft read (`GET /meta/:type/:name?state=draft`), the read Studio's editor loads an item from, so the marks always describe the body that read returned. It is absent on the active read, the cached branch and the `?preview=draft` read. `ListDraftsResponseSchema` (`GET /meta/_drafts`) is unchanged.
-- **Absent means "not recorded".** For a draft row whose saves recorded nothing (one saved before a server recorded the key), the key is absent rather than `[]`, so a reader never takes "not recorded" for "nothing changed".
+- **Absent means "not recorded".** No server writes the key yet; until one does, and for a draft row saved before it did, the key is absent rather than `[]`, so a reader never takes "not recorded" for "nothing changed".
 - **Nothing breaks.** Every response that parsed before still parses, and no runtime behaviour changes in this release of the spec.

packages/spec/authorable-surface/api.json

@@ -1701,6 +1701,7 @@
     "api/TriggerFlowResponse:success",
     "api/UndoImportJobResponse:deleted",
     "api/UndoImportJobResponse:failed",
+    "api/UndoImportJobResponse:failures",
     "api/UndoImportJobResponse:jobId",
     "api/UndoImportJobResponse:object",
     "api/UndoImportJobResponse:restored",