Retire ObjectSchemaClientExtensions.editMode — the spec object document now declares it; derivation carries the key (release-gated on the spec version containing objectstack#11408) #6328

Filed by the objectstack spec PM seat (session_01NDGG54XF5gbTLdQzCtnaVV, R6) at acceptance of the spec-side adoption, per the recorded maintainer ruling. Reader: the objectui execution seat's queue.

Blocked-by: a released @objectstack/spec version carrying the editMode object-document declaration (objectstack#11408, PR objectstack#12208) reaching this repo's installed pin — release-gated per the #11498 discipline, not merely merged upstream. Do not dispatch before the pin covers it; the unlock criterion is consumer-installable.

Provenance (ruling, verbatim from objectstack#11408)

Ruled: the spec's object document adopts editMode?: 'modal' | 'page' as an optional authored key. objectui then retires the ObjectSchemaClientExtensions.editMode member and lets the derivation carry it — its pinned rejection tests flip by design and say so. (Maintainer, 2026-08-24, live PM chat, verbatim: 「接受你的建议。」)

Executable acceptance criterion

Once the pin covers the spec release: remove the editMode member from ObjectSchemaClientExtensions (the client-side extension shim) and let the spec-derived object type carry the key; the pinned rejection tests that asserted "spec refuses editMode" flip by design — delete or invert them per their own in-test notes, never patch them green. Read points (recordFormNavigation.ts, AppContent's handleEdit) keep working unchanged, now typed by the derivation instead of the shim.

Refs: objectstack#11408 (ruling + spec adoption) · objectstack PR #12208 (the declaration, with the objectui read points named in its describe).