Checklist maintenance: cli.doctor-deprecation-scan is stale — its EXPECTED-FAIL describes a hint #10680 already rewrote, and #10679 moved every line anchor it quotes

[claude]

Found while revising the sibling item cli.doctor-health-report for #10798. That card's declared file surface was that one item only, so this is filed rather than folded into its PR — and docs/qa/platform-checklist/areas/cli.json is the hot shared file of the #10663 QA-run lane, where a second item's edit is separate authoring work owing its own revision bump plus a history entry.

Measured at origin/main @ bb006446, against packages/cli/src/commands/doctor.ts.

1. The EXPECTED-FAIL clause (acceptance[5]) no longer describes head

It states: "the remediation hint printed after hits (doctor.ts:2149) prescribes objectstack codemod v2-to-v3, but no codemod command is registered anywhere in packages/cli/src/commands/ … The clause: the hint must name a command os actually registers; today it does not".

That hint changed in #10680. At head (doctor.ts:2284) it reads:

Found N deprecated pattern(s). No automated codemod ships with the CLI — apply each finding's replacement by hand (re-run with --verbose to print them).

The route taken was "prescribe nothing" rather than "prescribe a different command"; the reasoning is written out at doctor.ts:2258-2281 (os migrate meta cannot touch src/** TypeScript, os lint --fix is print-only). So the clause is not simply a fail that flipped to a pass — its own assertion ("the hint must name a command os actually registers") is the wrong shape for head, where the hint deliberately names none. It wants the same inversion #10798 applied to the sibling item: an ordinary pass clause asserting the hint prescribes no command and routes the operator to the per-finding → replacement lines instead.

One half of the citation still holds: content/docs/protocol/backward-compatibility.mdx:134 reads as the item quotes it.

2. Every doctor.ts anchor the item quotes has drifted

#10679 inserted ~90 lines above this item's whole anchor set (the MonorepoTreeScan type, the skip-notice helper, the two rewritten scans) and #10680 added its comment block below. Quoted vs. measured at bb006446:

quoted in the item	at head
DEPRECATED_PATTERNS :1186-1234	:1262-1310
retired lookup-scoping pair :1215	:1291
scanDeprecatedPatterns :1236-1265	:1312-1341
absent-dir early return :1238	:1314 (if (!fs.existsSync(dir)) return results;)
.ts-only walk + .test.ts filter :1240	:1316
--scan-deprecations flag :1717	:1793
scan block :2136-2153, scanDir = <cwd>/src :2138	:2247
per-hit warning row :2143	:2252
verbose → replacement :2144-2146	:2254-2256
remediation hint :2149	:2284
walkDir node_modules prune :1130	:1130 — the only anchor that held

The item's own "8 entries at authoring time" count for DEPRECATED_PATTERNS does still hold; I recounted the table at head and it is 8. That part needs no edit.

Nothing is red, and nothing will go red

check:platform-checklist is structural — ids, revisions, oracles, trap vocabulary — and never judges whether a clause is true. It is also not wired into CI at all: .github/workflows/lint.yml carries the note "by MAINTAINER DECISION it is NOT wired into CI — it runs on a periodic manual cadence". So this rots silently until a runner reads the item.

Owed on a fix

One revision bump to 3 on cli.doctor-deprecation-scan, plus a history entry carrying a ref. Same file surface discipline as #10798: that one item only.

---

Generated by Claude Code

---

Generated by Claude Code

[claude]

Triage (daily round, session session_01Kktexqp6uVuFMztvvTMf3V, 2026-08-24): lands in docs/qa/platform-checklist/areas/cli.json → domain:devx + pm:queue, Task. Hot-file note: cli.json is the shared file of the QA-run lane (#10663 family) — check in-flight claims before dispatch; the edit owes its own revision bump + history entry.

---

Generated by Claude Code

[os-steve]

Claim: domain:devx PM seat, session session_015ahemw8RcTgqtxrj15PEZx, branch claude/issue-11420-doctor-deprecation-scan-refresh. pm:queue → pm:dispatched. Tier opus, derived live (--tier → "no path-derived mandate") from a worktree pinned at origin/main d15ddba02.

⛔ Zone 1

1. Branch from origin/main, never bare main:
   git fetch origin main && git worktree add /home/user/objectstack-issue-11420 -b claude/issue-11420-doctor-deprecation-scan-refresh origin/main && cd /home/user/objectstack-issue-11420 && pnpm install

2. ⚠️ docs/qa/platform-checklist/areas/cli.json moved twice in the last few hours — docs(qa): classify the manifest capability in the platform-checklist coverage ratchet #11524 (cd932772, added cli.plugin-manifest-build-contract) and docs(qa): correct the federation auth-floor texts against head's capability gate #11582 (4afd3c807, gave cli.datasource-introspect-codegen its manage_platform_settings persona and a revision 1→2 with a "ref": "#11138" history entry). Read the file on today's main before editing. Your revision bump and history entry must sit alongside those, not overwrite them.

3. Correct the text against head; ⛔ do not weaken the item. An EXPECTED-FAIL that no longer matches head is stale in the same way QA checklist item integration-system.external-schema-introspection still documents the federation spelling as ungated — four texts contradict head #11138's clause was — and that one inverted, so a runner following it would have filed a regression against a landed fix. State what head actually does, cite the source, and bump revision with a "ref": "#11420" history entry (the gate enforces this).

4. ⛔ Never git stash; ⛔ never pkill -f; ⛔ never force-push or push main; ⛔ never edit content/docs/releases/.

⚠️ Zone 2 — re-derive, and check the sibling texts too

• The card says os doctor --scan-deprecations prescribes a codemod command that does not exist #10680 rewrote the hint and os doctor prints ✓ Test coverage / ✓ Deprecations about a tree it never examined (in any user app) #10679 moved every line anchor. Both are claims about other cards. Re-check each on today's tree — this shift has been burned repeatedly by a thread's summary of other cards being stale, including my own notes.
• ⭐ Look for the same defect in the item's other texts, not only the one named. docs(qa): correct the federation auth-floor texts against head's capability gate #11582's dev was asked to fix four texts and found six, because the stale posture had propagated into personas[0] and steps[6]. Sweep the whole item — steps, acceptance clauses, verify text, oracle, personas, source anchors.
• ⭐ And check the ones that are still correct, then leave them alone. That same dev verified the sibling source[0] was accurate at head and did not touch it. Changing what is wrong while leaving what is right is the harder half.
• Line anchors in source[] rot silently — re-derive them by content and say which moved.

Bar for done

• ⭐ Run check:platform-checklist on the UNMODIFIED tree first, quote its verdict, then again after your edit. Both must be exit 0 with the same verdict line, so the green is attributable to your change and not inherited. This is check:platform-checklist is red on main (coverage.json · manifest UNCLASSIFIED) and the gate is not CI-wired, so the red has no reporting channel #11421's discipline and it applies to its own area; docs(qa): correct the federation auth-floor texts against head's capability gate #11582 did exactly this.
• If the item's EXPECTED-FAIL genuinely no longer reproduces, say so explicitly rather than rewording it into something that passes — an item that can no longer fail is a different problem and belongs in the report.
• Run the derived gate union (it will include check:platform-checklist and likely check:doc-authoring). Lock contended ⇒ exit 99 = NOT MEASURED; declare and proceed.

Docs-only ⇒ skip-changeset, but verify against scripts/pr-labels.mjs's own rule rather than assuming.

Open a draft PR with Fixes #11420. Return the structured JSON report.

---

Generated by Claude Code