chore: correct the affirmed consequent in this changeset's semver note (#14683)

I wrote that `minor` "means breaking" here, and that claiming it would
signal an incompatibility. That affirms the consequent: breaking => minor
holds, minor => breaking does not. check-changeset-no-major.mjs says so in
the header I cited — during the window the bump level "tells a consumer
nothing about whether the release breaks them", and the carriers are the
banner and the ADR-0087 disposition, "the only signal there is".

The landed record carries the other half: 87ad30c ('@objectstack/types':
minor) and 3c1bbd2 ("@objectstack/metadata": minor) are new-export bumps
with zero banner tokens. So `minor` is the union, not a breaking marker.

Corrected to what the gate actually says: the level carries nothing either
way, this change owes neither carrier, and `patch` follows from the lineage
and from no export being added. Lines 54-58 unchanged.

⛔ No code, test or pin changes.

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

Author: claude

.changeset/getmetaitems-org-read-gate.md

@@ -56,8 +56,20 @@ choice. `scripts/check-changeset-no-major.mjs` refuses `major` outright, so
 during the launch window a genuinely breaking change ships as `minor` (pre-1.0,
 whole-stack lockstep) — #13925 is exactly that, `"@objectstack/core": minor`
 carrying a bolded incompatibility banner and an `adr-0087:` marker for a
-narrowed published accept set. `minor` therefore *means* "breaking" here, and
-claiming it for this change would signal an incompatibility that does not exist.
+narrowed published accept set. But the implication runs ONE WAY ONLY, and the
+gate's own header is explicit that it does: during the window `minor` is the
+union of ordinary new-functionality bumps and banner-marked breaking ones
+(`87ad30c10`, `3c1bbd2a8` are new-export `minor`s carrying no banner at all),
+so the bump level "tells a consumer nothing about whether the release breaks
+them". The carriers of breaking-ness are the bolded banner in the body and the
+ADR-0087 disposition — "during the window they are the only signal there is".
+
+⇒ So `minor` here would not claim an incompatibility; it would claim NOTHING
+about compatibility, which is precisely the cost the header names. This change
+carries neither carrier because it owes neither — nothing is retired, no accept
+set narrows, and `check-adr-0087-registration` reads it as non-breaking. The
+level is `patch` because the lineage above is `patch` and no export is added,
+not because `patch` rebuts something `minor` would have asserted.
 
 **Nothing here is incompatible, and the reason is what the withheld rows are.**
 They are the #6190 phantoms: org-scoped rows of types with no per-org read