Editor: Creating new object in array of objects fails to trigger review/commit. Silent data loss.

[TribeWeb]

Environment

Operating system	macOS 25.4.0
CPU	Apple M4 (10 cores)
Node.js version	v22.22.1
nuxt/cli version	3.34.0
Package manager	pnpm@10.30.2
Nuxt version	4.4.2
Nitro version	2.13.1
Builder	vite@7.3.1
Config	alias, compatibilityDate, css, devtools, eslint, fonts, icon, image, modules, nitro, ogImage, runtimeConfig, site, sitemap, studio, vite
Modules	@nuxt/eslint@1.15.2, @nuxt/ui@4.6.0, @nuxtjs/seo@4.0.2, @nuxt/content@3.12.0, @nuxt/image@2.0.0, @nuxt/scripts@1.0.0-beta.1, @vueuse/nuxt@14.2.1, nuxt-studio@1.5.1, @nuxtjs/mdc@0.20.2, @nuxt/fonts@0.14.0

Version

1.5.1

Reproduction

Steps

1. Create a collection in content.config.ts which includes an array of objects in the schema (Zod)
2. Create a page in the relevant collection
3. In production, login to studio
4. Navigate to the relevant page
5. Using either the notion or code editor, create or add a new object in the array of objects

Observe that the Review button does not update to register any changes. Therefore the changes cannot be committed unless another item on the page is edited too.

Description

When editing in Studio in production, adding a new object in an array of objects fails to trigger a review or commit.

Data loss occurs when editing a number of pages at once as it is not obvious that not all edits have been captured.

Both the code editor and notion editor exhibit the same behaviour.

Workaround: Make another edit to the page that does a trigger a review and then all edits are captured and committed.

Additional context

No response

Logs