Skip to content

Commit 4e175a6

Browse files
committed
docs(changeset): the 26303 changeset describes the 3.6 exit-0 caveat as it now reads
The patch round changed 3.6 to say the stored-pass exit 0 counts only on the release being left; the changeset's Now bullet still described the earlier wording. Claude-Session: https://claude.ai/code/session_01J8VVAkD2h5o5cmhTRa3bsF Co-authored-by: Claude <noreply@anthropic.com>
1 parent 43d397d commit 4e175a6

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎.changeset/26303-upgrade-skill-stored-rows-before-18-3.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,5 +8,5 @@ Clause-②: no
88
Metadata-protocol: none
99

1010
- **Before.** § "Stored rows" said every stored-row rehydration replays the conversion chain including entries retired from the load path, so "a row written under protocol 16 therefore rehydrates in its protocol-17 shape without anybody editing it", and offered `os migrate meta --stored --apply` only as a way to make that durable. § 3.6 called the read-time rehydration "still the guarantee", the report template marked the stored pass optional ("rows rehydrate correctly today"), and eval 4 expected the same answer. On 18.3, which drops every conversion retired at or below 16.x, that advice leaves such a row unconverted for good.
11-
- **Now.** The section says rehydration replays only the conversions the installed release still carries, that 18.3 drops those retired at or below 16.x, and to run the stored pass on the release being left (18.2 or earlier for such a row) before moving; § 3.6 says to get exit `0` from `os migrate meta --stored --json` before the move; the report template's stored-pass line says it is owed before any release that drops the rows' conversions. Eval 4's expected answer says the same, and new eval 5 asks the 18.1 → 18.3 question directly.
11+
- **Now.** The section says rehydration replays only the conversions the installed release still carries, that 18.3 drops those retired at or below 16.x, and to run the stored pass on the release being left (18.2 or earlier for such a row) before moving; § 3.6 says the `os migrate meta --stored --json` exit `0` counts only on the release being left, because one that dropped a row's conversions answers `0` without recognising the row; the report template's stored-pass line says it is owed before any release that drops the rows' conversions. Eval 4's expected answer says the same, and new eval 5 asks the 18.1 → 18.3 question directly.
1212
- `SKILL.md` and `references/examples-upgrade.md` stay under their token ceilings (no ceiling moves). No schema, key, command or behaviour changes.

0 commit comments

Comments
 (0)