chore(changeset): record the ADR-0105 spec removals as minor, not major

Every publishable package is in the Changesets `fixed` (lockstep) group, so a
single `major` promotes the ENTIRE monorepo to a new major version. The repo
ships breaking changes as `minor` during the launch window (enforced by
scripts/check-changeset-no-major.mjs); #3494's spec prune set the precedent.

The FROM → TO migration notes are unchanged — they are what reaches consumers in
CHANGELOG.md, and they carry the breaking-ness regardless of the bump level.

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

Author: claude

.changeset/adr-0105-group-tenancy-phase-0-1.md

@@ -1,5 +1,5 @@
 ---
-'@objectstack/spec': major
+'@objectstack/spec': minor
 '@objectstack/plugin-security': minor
 '@objectstack/plugin-auth': minor
 '@objectstack/core': minor
@@ -17,6 +17,12 @@
 ADR-0105 Phase 0 + Phase 1: group tenancy posture; organization scope as a
 first-class authorization dimension.
 
+> This release carries BREAKING spec removals (see "Enforce-or-remove" below)
+> but is recorded as `minor`: every publishable package is in the Changesets
+> lockstep group, so one `major` would promote the whole monorepo. Breaking
+> changes ship as `minor` during the launch window — the migration notes below
+> are what reach consumers in `CHANGELOG.md`.
+
 ## Tenancy is now a spectrum (D1)
 
 `single | group | isolated`, resolved by the `tenancy` service and selected with