docs(changeset): name 18.0.0-next.0 only for the shapes it refuses; a second table for the three it still accepts

`view.data.provider: 'api'`, the page action rows' `'navigation'` executor and
the controlled-by-parent one-required-master rule are accepted by both
17.7.0 and the published 18.0.0-next.0, so the first release that refuses
them is the one after next.0. They get their own table, and the first
table's sentence names next.0 for its own rows only.

Claude-Session: https://claude.ai/code/session_012uFegdfR6K6uqvLzt7XsdZ
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.changeset/23145-tombstone-removal-version.md

@@ -6,7 +6,7 @@ Retirement prescriptions for shapes `@objectstack/spec` 17.7.0 still accepts now
 
 Clause-②: no
 
-17.7.0, the newest 17.x release (npm `latest`), still accepts every shape below, and `18.0.0-next.0` is the first release that refuses them. No 17.x release removes them: the 18 line does. Their refusals, and their `[REMOVED]` JSON Schema descriptions, named a different release:
+17.7.0, the newest 17.x release (npm `latest`), still accepts every shape in the two tables below. No 17.x release removes them: the 18 line does. `18.0.0-next.0` is the first release that refuses the shapes in this first table. Their refusals, and their `[REMOVED]` JSON Schema descriptions, named a different release:
 
 | Surface | Was | Now |
 | --- | --- | --- |
@@ -19,6 +19,14 @@ Clause-②: no
 
 The `18.0.0-next.0` release notes quoted the two `email_template` prescriptions with the earlier version, 17; from this release on they name 18.
 
+`18.0.0-next.0` still accepts the shapes in this second table, so the first release that refuses them is the one after it. Their refusals named 17, or no release at all:
+
+| Surface | Was | Now |
+| --- | --- | --- |
+| `view.data.provider: 'api'` | removed in @objectstack/spec 17 | removed in @objectstack/spec 18 |
+| `'navigation'` as a page action row's executor (`actionType` on `action:button` / `action:icon`, member `type` on `action:group` / `action:menu`) | no release named | refused on page action rows since @objectstack/spec 18 |
+| a `controlled_by_parent` object with no `master_detail` declared `required: true` | no release named | the one-required-master rule holds since @objectstack/spec 18 |
+
 One prescription was wrong the other way. 17.4.0 accepts the sub-day `TimeUpdateInterval` members `second`, `minute` and `hour`, and 17.5.0 refuses them, but the refusal said "retired in protocol 18". It now says "removed in @objectstack/spec 17.5.0".
 
 The `os migrate meta --from 17` sentence in each prescription is unchanged and was already right: `--from 17` replays the protocol-18 conversions. A prescription for a key that a 17.x release already refuses keeps naming 17. Text only: no key, value or shape is accepted or refused differently.