Skip to content

Commit fa949a8

Browse files
committed
chore(changeset): @objectstack/spec patch for the last migration-guidance references
Claude-Session: https://claude.ai/code/session_014EJ1ED8X4MMrT18BhVx4tx Co-authored-by: Claude <noreply@anthropic.com>
1 parent 2114942 commit fa949a8

1 file changed

Lines changed: 23 additions & 0 deletions

File tree

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
'@objectstack/spec': patch
3+
---
4+
5+
fix(spec): `os migrate meta` guidance for the two padded list-view field-name entries states the contract-first rule in words, and the notification/embed retirement drops a sweep batch ordinal
6+
7+
Clause-②: no
8+
9+
The ADR-0087 semantic entries are printed by `os migrate meta` as the header, `why:` and
10+
`verify:` lines of a manual change. Two of them —
11+
`ui-list-view-grouping-field-padded-refused` and `ui-list-view-groupbyfield-padded-refused` —
12+
explained why a padded field name is refused rather than trimmed by pointing at a rule number
13+
in a contributor guide, a number that names nothing in this repository's guide. Their `why:`
14+
text now states the rule itself: fix the metadata, not the renderer — off-spec metadata is
15+
refused where it is authored, never coerced into working.
16+
17+
`ui-notification-action-embed-config-retired` named the batch of the v17 unknown-key
18+
strictness sweep that measured the two retired shapes by its ordinal. The sentence already
19+
says what that batch measured and decided, so the ordinal is dropped.
20+
21+
Text only: no entry id, `surface`, `from` / `to`, conversion or matching logic changes, and the
22+
chain rewrites exactly what it rewrote before. The generated migration registry,
23+
`spec-changes.json` and the protocol upgrade guide carry the same text.

0 commit comments

Comments
 (0)