chore(changeset): declare the enum-shrink bump as minor per lockstep policy

The repo's fixed (lockstep) Changesets group versions every publishable
package together, and the launch-window CI gate (check-changeset-no-major)
rejects majors — breaking changes ship as minor with the ! marker as the
record, matching every pending breaking changeset on main (GraphQL-surface
removal, ADR-0104 write cutover). The changeset body still carries the full
BREAKING migration guide.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018V7nzG1x7nuqkwZQTowtBo

Author: claude

.changeset/apimethod-enum-shrink.md

@@ -1,12 +1,15 @@
 ---
-"@objectstack/spec": major
+"@objectstack/spec": minor
 "@objectstack/objectql": patch
 "@objectstack/platform-objects": patch
 ---
 
 feat(spec)!: shrink the `ApiMethod` enum to the six primitives — legacy values are stripped at parse, never honored (#3543, P2 of #3391)
 
-**BREAKING:** the authored `enable.apiMethods` enum is now exactly the six
+**BREAKING** (ships as `minor` per the lockstep launch-window policy — every
+package versions together, so a `major` here would promote the entire
+monorepo; the `!` marker and this changeset are the breaking-change record):
+the authored `enable.apiMethods` enum is now exactly the six
 primitives (`get`, `list`, `create`, `update`, `delete`, `bulk`). The eight
 legacy values (`upsert`, `aggregate`, `history`, `search`, `restore`, `purge`,
 `import`, `export`) are no longer authorable — they are DERIVED effective