Repository navigation
Commit ef0e7f9
fix(docs): the retirement guide's own
Both "where the record goes" snippets in verified-by-retirement.md write `"notes"` BARE.
Canonical JSON reserves exactly eight structural keys (name/package/extends/abstract/
overlay/isArray/children/value); everything else is an inline attribute and must carry the
sigil. So the loader rejects it:
Unknown key 'notes' on requirement.functional 'BeatProgression' — must be reserved or
@-prefixed
Verified against a real strict load: bare `notes` errors, `@notes` loads and reads back.
This is the worst possible place for it. Those two snippets ARE the answer FR-038 gives to
the one objection adopters actually raise — "deleting the node destroys the history" — and
the answer is "put it in notes, here is how". An adopter who follows the example literally
gets a load failure while doing the migration the guide told them to do, which reads as the
retirement being half-baked rather than as a typo in a sample.
Found by testing the example rather than reading it, after being asked where notes had
gone. The two other bare-`notes` hits in the tree are tool config
(conformance-expected-failures.json), not metadata, and are correct as written.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>notes examples do not load1 parent eae94b3 commit ef0e7f9
1 file changed
Lines changed: 2 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
68 | 68 | | |
69 | 69 | | |
70 | 70 | | |
71 | | - | |
| 71 | + | |
72 | 72 | | |
73 | 73 | | |
74 | 74 | | |
| |||
92 | 92 | | |
93 | 93 | | |
94 | 94 | | |
95 | | - | |
| 95 | + | |
96 | 96 | | |
97 | 97 | | |
98 | 98 | | |
| |||
0 commit comments