From 3e842f9fd8f667f2b22066787d69fd1db6b53694 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 8 Oct 2026 02:51:04 +0000 Subject: [PATCH] docs(skills): objectstack-upgrade's late-arrival example starts at the support floor MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The "several majors late" paragraph examples `os migrate meta --from 10`, which the chain refuses below MIGRATION_SUPPORT_FLOOR = 16 with MigrationFloorError. Reword it: the example is now `--from 16`, the floor is stated in the same breath (16 today), and a project below the floor is told to upgrade to it by the older route first, then run the chain. Token ratchet (ceil(utf8 bytes / 4), ceiling 6193): 6187 -> 6184. The reword is paid by deleting two clauses the same file already states beside them — the `mkdir -p .upgrade` trailing comment (the paragraph under the block says it) and "which is exactly what the table above points at" (the table above is those two sources). No re-wrap. Claude-Session: https://claude.ai/code/session_01CXydFDyiQwNbGFkmwrcRQq Co-authored-by: Claude --- skills/objectstack-upgrade/SKILL.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/skills/objectstack-upgrade/SKILL.md b/skills/objectstack-upgrade/SKILL.md index 6274f4e9eb1..c994c6fec7e 100644 --- a/skills/objectstack-upgrade/SKILL.md +++ b/skills/objectstack-upgrade/SKILL.md @@ -100,15 +100,16 @@ one installed. Three sources, in order of authority: default to the lower one: a default flip ([3.3](#33-validate)) stamps its constraint onto a source already past that major. -Arriving several majors late is the designed-for case. `os migrate meta --from 10` -replays every step in order; there is no penalty for lateness and no requirement -to upgrade one major at a time. +Arriving several majors late is the designed-for case: `os migrate meta --from 16` +replays every step in order, with no requirement to upgrade one major at a time — +down to the chain's support floor, 16 today. Below the floor, upgrade to it by +the older route first, then run the chain. ### Make the work reviewable before you change anything ```bash git checkout -b upgrade/protocol-17 -mkdir -p .upgrade # every artifact this skill produces lands here +mkdir -p .upgrade ``` The `.upgrade/` directory is the deliverable's workspace: the machine outputs @@ -244,7 +245,7 @@ upgrade and again in the report. > `src/migrations/registry.ts`) and the platform repo's generated upgrade guide > are **not** in the published package — only `src/**/*.zod.ts` is. Their > consumer-facing projection is `spec-changes.json` and the chain's own `--json` -> output, which is exactly what the table above points at. +> output. ### 2.2 The three residue classes