skills(objectstack-upgrade): the upgrade skill says `os migrate meta` "writes nothing but `--out`", which `--write` (PR #22108) now makes incomplete

[objectstack-fleet]

Filed by the triage seat (objectstack-wide, seat post #6015, session_01AavokzJ5DndAwitDXvKy4U) as the skills half of #9591's remainders (release 6044979380). ⛔ Not a claim.

What is now incomplete (read on main f2a45db2ad)

• skills/objectstack-upgrade/SKILL.md:62: "# 1 · mechanical — replay the chain (reads the config, writes nothing but --out)".
• skills/objectstack-upgrade/SKILL.md:469, the troubleshooting row: "Working as designed — the command writes nothing but --out."
• Both are true of the default invocation. Since PR feat(cli): os migrate meta --write — write the chain's mechanical edits into the authored sources #22108 (a959493cdf), os migrate meta --write also rewrites authored sources. An AI author reading the skill is never told that the flag exists.

Direction

• Name --write at both sites. It writes only the sites it can prove, and lists every other site with a refusal kind. It restores every file and exits 1 on any disagreement.
• Say the default run still only lists.
• Keep the skill line ratchet: net 0 lines where the ratchet requires it.
• Word it consistently with the retirement sentence that feat(cli): os migrate meta --write — the AST codemod that rewrites authored sources for the mechanical applied set (v18) #9591 restores in packages/spec/src/shared/retired-key.ts (spec lane). Neither waits on the other.

Landing

skills/** is Tier H. The PR lands on an authorized approval or the maintainer's hand.

Clause-②: no. No changeset (skill text).

Dedupe: objectstack-upgrade skill migrate meta writes nothing but --out · --write codemod skill text.

[objectstack-fleet]

Claim: PM loop round 2
Session: session_0181E4ZeZmWyknawnauxD2CE
Account: os-steve (the seat's linked user as GET /user answers it; always the card's assignee)
Branch: claude/issue-22120-upgrade-skill-migrate-meta-write
Worktree: objectstack-issue-22120
Domain: domain:skills
Seat: domain:skills#2
File surface: skills/objectstack-upgrade/SKILL.md — the whole published skill read as one package: the two sites the card names (:62 and :469 on origin/main db4c45b8c3) plus every other sentence in the file that states what os migrate meta writes (:130, :151-153, :156, :160-162 at the same ref), re-derived by the dev on the tree. skills/objectstack-upgrade/references/examples-upgrade.md (:57) and skills/objectstack-upgrade/evals/protocol-major-upgrade.json (must_contain includes --out) only if their wording turns false under --write — at this reading both stay true of the default run and are expected untouched. ⛔ No other skills/** file; ⛔ no content/docs/** (the devx lane carries content/docs/upgrading.mdx under #22108's cross-lane declaration); ⛔ no generated listing (skills/README.md and content/docs/ai/skills-reference.mdx regenerate from frontmatter, which does not change); ⛔ no packages/spec/** (the retirement sentence in retired-key.ts is #9591's spec-lane remainder); stop on breach; explain in the report
Container & model: S (one published skill, text only) handled as M — the judgment is in the wording and in paying the ratchet, not in a gate — mode:subagent, model: CONTRACT_REVIEW_TIER — dispatch-gates --tier --repo objectstack-ai/objectstack skills/objectstack-upgrade/SKILL.md on db4c45b8c3 prints "Model tier — MANDATORY … skills/objectstack-upgrade/SKILL.md ⇢ 'skills/**' — clause ① (2026-09-10 ruling, verbatim 「必须 fable的还包括对外发布的skills」) … no one-line exemption applies under this root"; no downgrade exit: the one-line mechanical-edit exit is closed for skills/** and the quota exemption is not in effect. The governed-text face owes an at-tier ## Contract review in seat after delivery
Clause-②: no
Responsibility: n/a — not a defect card (documentation: the published skill's text fell behind a landed CLI flag)
Thread-read: none
Serial constraints cleared: none — 8 open PRs in the repo at this reading, every file list read through REST: none touches skills/** or .claude/**; the two on packages/cli/src/commands/migrate/meta.ts (#22121 head 0bd4955e85, #22115 head 5104a5d745) are disjoint in files and are named to the dev as in-flight semantic neighbours of the --out sentences; git ls-remote shows no claude/issue-22120-* branch; the last touch of skills/objectstack-upgrade/SKILL.md on origin/main is 595621d3 (2026-09-23), not same-day; meta.ts was touched today by a959493c (PR #22108, merged), which is this card's premise; seat 1 (#7623) has nothing in flight; #9591's spec-lane half runs in parallel on packages/spec/src/shared/retired-key.ts, disjoint, and the card says neither waits on the other; the lane's hot-file table holds no entry for this file; verify lock state: lock is free, queue: empty — arrival depth 1 (this dev), below LOCK_DEPTH_HOLD; shared checkout at origin/main db4c45b8c3. Readings taken at 2026-10-07T20:12Z.

[objectstack-fleet]

Correction to claim 6045983531, line Serial constraints cleared: — of the 8 open PRs read, one does touch skills/**: #22103 (skills/objectstack-data/rules/indexing.md, another skill root, disjoint from skills/objectstack-upgrade/**). None touches .claude/** or this card's file surface; the clearance stands. Appended rather than edited so the claim's shape and timestamp stay as written.

[objectstack-fleet]

os-dev-report
{
"issue": 22120,
"status": "done",
"branch": "claude/issue-22120-upgrade-skill-migrate-meta-write",
"pr": "#22122",
"session": "session_0181E4ZeZmWyknawnauxD2CE",
"premise_still_valid": true,
"summary": "Premise verified on origin/main db4c45b: packages/cli/src/commands/migrate/meta.ts carries the --write flag (description; exclusive: [stored]), WriteOutcome.status written | restored | unwritten, printWriteOutcome listing each unwritten site as not written [kind]: reason, and this.exit(1) whenever write.status is not written; the proof rule and the closed CodemodRefusalKind set are in packages/cli/src/utils/authored-source-codemod.ts. Edited skills/objectstack-upgrade/SKILL.md only (one commit, 9bb1001): the Quickstart step-1 comment names both routes; the §1 flag table gains one --write example line; the §1 one-fact paragraph opens By default … rewrites no source file — lists the mechanical edits and writes only the --out snapshot — then one sentence for --write (rewrites in place each edit traced to one literal in one project file, lists every other with the reason it was not written, never writes a semantic change, restores every file and exits 1 when the re-run disagrees); the failure-mode row says the default run only lists and its fix names --write or the by-hand port; the stored-only-flag row tail now mirrors the CLI refusal text (writes only --out and, with --write, the sources). Neither --out on a no-op run nor the semantic-notice list is described (#22121 / #22115 in flight). Draft PR #22122 opened through the relay, assignee os-steve, label skip-changeset (no package files[] ships skills/). Tier H surface: left draft; the at-tier Contract review is the seat's.",
"ratchet": {
"gate": "node scripts/check-skills-token-ratchet.mjs (tokens = ceil(utf8 bytes / 4); ceiling 6193 for this file)",
"before_db4c45b8c3": {
"lines": 488,
"bytes": 24772,
"tokens": 6193,
"headroom": 0
},
"after_9bb10014": {
"lines": 484,
"bytes": 24748,
"tokens": 6187,
"headroom": 6
},
"diff_lines": "+13 / -17",
"gate_line_after": "✓ check-skills-token-ratchet: skills/objectstack-upgrade/SKILL.md is 6187 tokens (ceiling 6193; headroom 6).",
"paid_with": "content deletions only, no re-wrap counted as payment: (1) the §1 --out recheck code block, whose first line was byte-identical to Quickstart step 1 and whose recheck is carried by Quickstart step 3, the §3.3 callout and the failure-mode row; (2) the clause It rewrites the loaded stack in memory and reports the diff, restated by the mechanism paragraph three lines above; (3) the --stored subsection sentence The authored-source flags and the stored-only flags are mutually exclusive …, carried by the failure-mode row --apply refused / stored-only flag rejected (the preceding --stored takes no --from keeps the other direction). No rule, failure-mode row or command removed."
},
"tests": "Docs-only diff: no package touched, so no ① dependency-closure build and no ② package test/typecheck are owed (stated, not skipped). ③/④ gate families derived with node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack, once with the path and once from the changeset at 9bb1001: identical lists, 24 commands (16 path-matched, 8 whole-tree). Each run with its printed command recorded byte-for-byte beside its exit code (cmd :: exit N, captured before any pipe); logs in the issue-22120 scratchpad. First sweep: 23 exit 0, 1 exit 3 — pnpm --filter @objectstack/lint run check:doc-formula-expressions, PREREQUISITE NOT MET (@objectstack/lint not built; its own text: Nothing was measured). Its prescribed fix run under the shared verify lock (OS_VERIFY_LOCK_SLOT=issue-22120-dev; pnpm exec turbo run build --filter=@objectstack/formula --filter=@objectstack/lint --concurrency=2; os-verify-lock VERDICT command-exit 0, held 125 s, waited 0 s; 4 tasks successful), gate re-run: exit 0. Reconciliation: node scripts/pm/dispatch-gates.mjs --ran ran.list --repo objectstack-ai/objectstack → ✓ 24 derived families accounted for — 24 run, 0 NOT-MEASURED. Verdict lines read: check:skill-docs ✅ Skill docs in sync (skills/README.md and content/docs/ai/skills-reference.mdx unchanged; frontmatter untouched); check:skill-identifier-liveness OK — Leg 1: 457 citations over 53 published files; check:nul-bytes exit 0 plus own grep -naP control-byte scan of the file: no hits; the diff adds no angle-bracket fragment. Repo-wide pnpm lint is CI's run, not run here. PR body: relay read-back 7746 bytes sent = 7746 stored, identical; independent REST read-back of .body byte-compared to the sent file: identical (7745 bytes with the trailing newline trimmed on both), exactly one footer, first line Fixes #22120, draft true.",
"gates": [
{
"command": "node scripts/check-ci-filter-parity.mjs",
"exit": 0
},
{
"command": "node scripts/check-closing-keyword-parity.mjs",
"exit": 0
},
{
"command": "node scripts/check-closing-keyword-parity.mjs --self-test",
"exit": 0
},
{
"command": "node scripts/check-comment-mask-corpus.mjs",
"exit": 0
},
{
"command": "node scripts/check-doc-route-spelling.mjs --advisory",
"exit": 0
},
{
"command": "node scripts/check-doc-route-spelling.mjs --self-test",
"exit": 0
},
{
"command": "node scripts/check-skills-token-ratchet.mjs",
"exit": 0
},
{
"command": "node scripts/check-skills-token-ratchet.mjs --self-test",
"exit": 0
},
{
"command": "pnpm --filter @objectstack/lint run check:doc-formula-expressions",
"exit": 0
},
{
"command": "pnpm --filter @objectstack/spec run check:skill-docs",
"exit": 0
},
{
"command": "pnpm check:agent-test-spelling",
"exit": 0
},
{
"command": "pnpm check:corpus-claim-drift",
"exit": 0
},
{
"command": "pnpm check:cross-package-test-inputs",
"exit": 0
},
{
"command": "pnpm check:doc-authoring",
"exit": 0
},
{
"command": "pnpm check:driver-memory-census",
"exit": 0
},
{
"command": "pnpm check:gitlink-declared",
"exit": 0
},
{
"command": "pnpm check:nul-bytes",
"exit": 0
},
{
"command": "pnpm check:pm-governed-merges",
"exit": 0
},
{
"command": "pnpm check:refd-timer-probe",
"exit": 0
},
{
"command": "pnpm check:role-word",
"exit": 0
},
{
"command": "pnpm check:skill-compatibility",
"exit": 0
},
{
"command": "pnpm check:skill-frame-sync",
"exit": 0
},
{
"command": "pnpm check:skill-identifier-liveness",
"exit": 0
},
{
"command": "pnpm check:watch-hint-literal",
"exit": 0
}
],
"ci_at_report": "head 9bb1001, one REST read of check-runs after the label write: success — Check Changeset (skip-changeset honoured), Governed Surface Queue Guard, Dogfood Regression Gate, Type Check · workspace, Type Check · debt ledger, the card-claims-branch / part-of / single-writer-path / same-issue guards, Test Core 4/6 and 5/6; in_progress — Lint & Repo Gates, Type Check · source gates, Type Check · consumer gates, Test Core 1/6 2/6 3/6 6/6. Not waited on (CI convergence is the PM's).",
"mcp_calls": "0 — no MCP GitHub tool called (reads via gh api GET; writes via the scripts/pm relay only)",
"api_writes": "3 relay dispatches (each one POST /repos/objectstack-ai/objectstack/dispatches, executed by fleet-write as objectstack-fleet[bot]) carrying 4 REST writes: [1] pr_create → POST /repos/objectstack-ai/objectstack/pulls (draft forced) = #22122, run 37683531052, read-back identical; [2] label-write → POST /repos//issues/22122/labels (skip-changeset) + POST /repos//issues/22122/assignees (os-steve), run 37683680835, read-back MATCHES (labels documentation, size/s, skip-changeset; assignee os-steve); [3] this os-dev-report comment → POST /repos//issues/22120/comments via post-stamped.mjs. Plus 2 git push (the empty-branch probe, then the commit) — not REST. No PATCH on the PR body, no card assignee write, no POST /issues.",
"open_questions": [],
"out_of_scope_findings": [
"class: b · reach: the skill prints a command the CLI refuses — SKILL.md:103-105 at db4c45b says Arriving several majors late is the designed-for case. os migrate meta --from 10 replays every step in order; MIGRATION_SUPPORT_FLOOR = 16 (packages/spec/src/migrations/registry.ts:79). Executed one layer below the door against the spec dist built in this worktree: applyMetaMigrations({}, 10, 17) throws MigrationFloorError — Cannot migrate from protocol 10: the chain's support floor is 16 (ADR-0087 D3). Upgrade to protocol 16 by another path first, then re-run. — while applyMetaMigrations({}, 16, 17) is the passing control; meta.ts maps it to exit 1 / --json error unsupported_from_major, and the skill's own failure-mode row MigrationFloorError already says so. Not fixed here: the sentence's point (lateness is designed-for) cannot be re-exampled truthfully on a 16 → 17 chain, so the fix is a rewording, which fails the bounded in-place exemption's mechanical-form clause; the same 6-token headroom applies. dedupe: objectstack-upgrade skill --from 10 · MigrationFloorError skill lateness example · MIGRATION_SUPPORT_FLOOR 16 skill text stale · carrier: a skills-lane card on skills/objectstack-upgrade/SKILL.md (seat to file)",
"carrier: #9591 spec lane · noted, not filed — packages/spec/src/shared/retired-key.ts docblock still says os migrate meta has never written an authored source file and names #9591 as the commissioned codemod; false since a959493, owned by the spec-lane remainder the card names (packages/spec/** not touched here)",
"carrier: none · noted, not filed — skills/objectstack-upgrade/evals/protocol-major-upgrade.json eval 1 expected_output says the command rewrites nothing on disk: true of the default route it describes (no --write); whether an eval should exercise --write is a product choice, not drift. must_contain --out still satisfied by SKILL.md; references/examples-upgrade.md:57 (Ported into sources from os migrate meta --out) still true of the by-hand route. Both untouched, as the claim expected."
],
"deviations": [
"check:doc-formula-expressions first exited 3 (prerequisite, not a finding); the prescribed build was run under the verify lock and the gate re-run green; ran.list line 9 replaced with the re-run's exit 0 before the final --ran reconciliation (first reconciliation read: 24 derived, 23 run, 1 NOT-MEASURED derived from exit 3).",
"label-write made in ONE call carrying both the assignee and the label (one dispatch, two REST writes), per the budget line label-write (incl. PR assignee).",
"Commit trailer pair written model-free (Co-authored-by: Claude; Claude-Session URL) per AGENTS.md; the harness reminder's model-named Co-Authored-By line was not used. No card trailer in the commit; the card relation lives in the PR body (Fixes #22120).",
"No ## Contract review posted: the at-tier record is the seat's after delivery (claim: the governed-text face owes it in seat)."
],
"files_changed": [
"skills/objectstack-upgrade/SKILL.md"
]
}

---

Generated by Claude Code

[objectstack-fleet]

ACCEPT — PR #22122 (draft, head 9bb10014, one file skills/objectstack-upgrade/SKILL.md +13/−17), verified against GitHub, not against the report.

• Checklist: draft PR to main; first line Fixes #22120, Clause-②: no at a line start, no other closing keyword in the body; the file set equals the claimed surface (no sibling, no content/docs/**, no packages/spec/**); skip-changeset holds (no package files[] ships skills/) and Check Changeset concluded success; ## 维护者速读(草稿) present; the two ratchet readings in the body agree with the blob (24,748 bytes ⇒ 6187 tokens, ceiling 6193).
• Spot-check readings: the five --write claims each traced to meta.ts / authored-source-codemod.ts on db4c45b8c3; the three deletions each have a surviving home, one with a partial home judged acceptable — the record is the ## Contract review PASS on the PR (comment 6046687007); eval must_contain anchors all present; frontmatter unchanged.
• Gates: the 24 derived families ran with exit codes and a --ran reconciliation (report 6046525169). CI on 9bb10014 at this read: Lint & Repo Gates, every Type Check job, Governed Surface Queue Guard, Dogfood Regression Gate and Test Core 2–5/6 success; Test Core 1/6 and 6/6 in progress — convergence belongs to the landing window.
• Deviations accepted: check:doc-formula-expressions first exited 3 on an unbuilt @objectstack/lint (prerequisite, not a finding) and re-ran green after the prescribed build under the verify lock.
• Acceptance notes: filed skills(objectstack-upgrade): the "several majors late" paragraph still examples os migrate meta --from 10, which the chain refuses below MIGRATION_SUPPORT_FLOOR = 16 (MigrationFloorError) #22123 (class b — SKILL.md:103 examples --from 10 below the floor of 16; same file, pm:blocked behind this card); retired-key.ts docblock → carrier feat(cli): os migrate meta --write — the AST codemod that rewrites authored sources for the mechanical applied set (v18) #9591 remainder 1 (spec lane), noted, not filed; eval 1 wording → Acceptance notes, no carrier.
• Tier H (skills/**): check-governed-merges --pr 22122 exit 3, "landing tier: H(人合)", 30 changed lines ≤ 5000. The PR stays draft; needs-user-decision goes on the PR with the final 维护者速读 in this write, review is requested from os-zhuang and hotlong, and the seat lands it (expected-skip reading on the final head → ready → auto-merge → queue) once an authorized APPROVED is on the PR.

[objectstack-fleet]

Hand-over note — seat domain:skills#2 (session_0181E4ZeZmWyknawnauxD2CE, os-steve) signs off at 2026-10-08T01:56Z on the maintainer's instruction 「你可以下班了」. ⛔ Not a release of the claim: the card stays assigned to the claim's account and pm:dispatched stays until MERGED.

State at sign-off: PR #22122 (draft, head 9bb10014, one file skills/objectstack-upgrade/SKILL.md +13/−17) is ACCEPTED (6046697178) with the at-tier ## Contract review PASS 6046687007 on that head; Tier H (skills/**) — it waits on an authorized APPROVED from os-zhuang or hotlong (review requested) or the maintainer's hand. CI on the head: 24 check-runs success, 15 expected skips (check-expected-skips --pr 22122 exit 0), mergeable_state clean at the last read.

Caretaker = the next seated skills PM (seat 1 huangyiirene / session_01CXydFDyiQwNbGFkmwrcRQq while it is the only seated skills PM, else seat 2's successor; seat post #19287 carries the same registration). Landing steps once an authorized APPROVED is on the PR, nothing else:

1. node scripts/pm/check-governed-merges.mjs --pr 22122 (expect exit 3, "landing tier: H") and node scripts/pm/check-expected-skips.mjs --pr 22122 exit 0 on the FINAL head; if the head moved, a new ## Contract review is owed before any flip — the review judgment is not delegated by this note.
2. Relay ops pr_ready + automerge_enable (merge origin/main first only if mergeable_state reads dirty); then follow to MERGED.
3. Close-out in one act: strip pm:dispatched from this card (it closes by Fixes), strip needs-user-decision from the PR, release the hot-file entry on the seat post; skills(objectstack-upgrade): the "several majors late" paragraph still examples os migrate meta --from 10, which the chain refuses below MIGRATION_SUPPORT_FLOOR = 16 (MigrationFloorError) #22123 (Blocked-by: #22120) returns to the queue by the unlock scan.
   A human merge is itself the review record; only step 3 remains in that case.

[objectstack-fleet]

Hand-over update (same seat, session_0181E4ZeZmWyknawnauxD2CE, before signing off): the Tier H terminal is already past. os-zhuang APPROVED PR #22122 at 2026-10-08T01:53Z (review 5450496025 on head 9bb10014), flipped it ready, armed auto-merge and enqueued it at 2026-10-08T01:54Z (queue branch gh-readonly-queue/main/pr-22122-… on main 8fc50b76 at this read). What remains for the caretaker is step 3 of the note above only: confirm MERGED (read the queue branch and origin/main together), then strip pm:dispatched from this card (it closes by Fixes), strip needs-user-decision from the PR, release the hot-file entry on seat post #19287; #22123 returns to the queue by the unlock scan. If the queue kicks the PR out, the kick-out comment of the merge-queue triage workflow is the input and landing-operations.md 〈入队与落地〉 applies (re-enqueue is the approving human's or the next seat's act; the contract review PASS covers this head only).