docs(cli): drop phantom os codemod v2-to-v3 and stale projects/ tree node

[os-elon]

Fixes#10881

What changed

packages/cli/README.md is this package's published README, and it carried two false claims in the same block.

1. The phantom os codemod v2-to-v3 command. Removed the whole ### Code Transforms table (its one row) and the matching codemod/v2-to-v3.ts node from the Architecture source-tree listing. Neither the command nor the file has ever existed: packages/cli/src/commands/ has no codemod/ directory, and probed against the built binary:

$ node packages/cli/bin/run.js codemod v2-to-v3
› Error: command codemod:v2-to-v3 not found # exit 2

Chose removal over "not yet available" — the one judgement call the card left open, and I want to be explicit about why: the only concrete plan in this space is #9591 (os migrate meta --write, pm:on-hold, targeting v18), and it is a differently-named, differently-scoped command over the mechanical retired-key set, not a "v2 config to v3 format" transform. So there is no accurate future command to point a kept row at — a row that plainly said "not available yet" would still misdescribe what eventually ships. The "not yet available" information already lives in content/docs/protocol/backward-compatibility.mdx:134 and docs/DX_ROADMAP.md:127, so nothing is lost by dropping it here; this brings the package README in line with the tool itself, which lost the same false prescription in #10882.

2. Stale projects/ tree node. The same tree listing showed a projects/ directory under src/commands/ with list.ts / show.ts / create.ts / switch.ts / bind.ts. Renamed to environments/, matching the v5.0 project → environment rename (ADR-0006, no aliases) and the real directory — the subcommand file list itself was already accurate and is unchanged.

Changeset

.changeset/cli-readme-drop-phantom-codemod.md — @objectstack/cli patch. Precedent for a README-only doc fix getting a patch changeset: .changeset/published-readme-relative-target-existence.md, .changeset/hono-server-readme-kernel-bootstrap.md.

Out of scope (filed separately)

While sanity-checking the tree listing against the real directory, found three more os projects mentions in this same README outside the tree listing (:75 alias claim, :98 "legacy path" claim, :278 Typical Workflow step) — none backed by a registered oclif alias. Filed as #10927 rather than swept into this PR, per the card's fence against expanding into a full listing audit.

Tests

Docs-only; no packages/cli/src/** touched. Gate set re-derived with node scripts/pm/dispatch-gates.mjs (no path args) against this diff — commands and pass/fail evidence in the PR-report comment on #10881.

Generated by Claude Code

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 1 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• 1 changed file(s) yielded no anchor (packages/cli/README.md) — pages documenting those are invisible to this run

Coarse fallback — 23 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 3d7deb70005ce2297b5b1a311b629106c3c39bb8 → packageMentionDocs.

[github-actions]

⛔ merge queue 构建失败 — 先分诊，再决定要不要重排

队列构建 32514159360 红了。队列跑的是全量套件（PR 侧 CI 只跑 affected 子集），
所以失败的测试可能在本 PR 没碰过的包里 —— 那不是重排能修的。每次盲目重排都会让排在后面的所有 PR 重建一轮。

失败的 job（日志抽取，best effort）：

• Console Pin Gate — 失败步骤: Build the Console SPA at the pinned objectui SHA

  ✗ Build failed in 6.14s
  

↳ 失败原因 是判读的关键：超时（Test timed out in … / Hook timed out in …）多半是负载/时序，不是本 PR 的回归；
断言（AssertionError: …）才指向真实的行为改变。两者的 FAIL 行长得一模一样，只有这一行能区分。

跨 PR 相同签名（24h，按失败测试文件聚合）：

• ⚠️本次没有可用的聚合签名（日志里没有能解析出测试文件名的 FAIL 行）—— 这不是「没有同签名的其他 PR」，是这一轮没测到。跨 PR 聚合本次不可用，请手工比对其他 PR 的同类评论。
• ⚠️ 24h 评论账本没读完（超过 5 页仍未读到窗口尽头），所以上面的「不同 PR 数」是下界，不是全量。

历史信号：

• 本 PR 过去 24h 无队列失败记录（首次）。
• 过去 24h 队列共有 44 个失败构建（不含本次）。

分诊清单：

1. 失败测试在本 PR 改动的包里 → 真回归，修 PR。
2. 失败测试与本 PR 无关 → 看上面的「跨 PR 相同签名」；已有汇总 issue ⇒ flaky/环境问题实锤，去那张 issue 上谈，修好前重排只会再烧一轮全队列。
3. 两者都不是 → 可能与同组 PR 语义冲突；等前面的 PR 落地或失败出队后再重排一次即可，不要连续重排。

---

Generated by Claude Code · merge-queue-triage workflow (#4859)