cli: `os i18n extract --check` failure prints a regenerate command with `--locales=` empty and every other flag dropped — following it yields a different bundle that fails --check again

[baozhoutao]

Summary

When os i18n extract --check fails, the "regenerate and commit" line it prints is not the command that would regenerate the bundle: --locales= is printed empty, and every other flag the invocation carried (--no-objects-only, --filter, --no-metadata-forms) is dropped. Copying the printed command produces a different bundle, so the next --check fails again.

Minimal reproduction

Platform 17.2.0.

$ objectstack i18n extract --locales=zh-CN --no-metadata-forms --no-objects-only --filter=kpi_ --out=/tmp/i18n-out --check
  Skeleton summary
    zh-CN      529 key(s)  (of 529 expected)
  ✗ missing:    ../../../../../../../private/tmp/i18n-out/zh-CN.objects.generated.ts
  ✗ Translation bundles have drifted from the schema. Regenerate and commit:
  os i18n extract  --locales= --fill=empty --out=/tmp/i18n-out

Three defects in one line:

1. --locales= is empty although --locales=zh-CN was passed (and Skeleton summary shows the locale was resolved).
2. --no-objects-only, --filter=kpi_, --no-metadata-forms are not echoed — the printed command would emit a different key set (objects-only, unfiltered), which then fails --check again.
3. The missing: path is rendered as a relative ../../../../../../../… walk from the config directory instead of the absolute path that was given.

Expected

The regenerate hint reproduces the exact invocation minus --check (all flags, resolved locales, the --out as given). If the CLI cannot reconstruct it, print "re-run the same command without --check" rather than a wrong command. Paths in diagnostics should be printed as given (or absolute).

Environment

@objectstack/cli 17.2.0 · Node 22 · app objectstack-ai/kpi.

---

Blocker discharged — ⛔ no live Blocked-by: line remains on this card. This body previously carried Blocked-by: #16502. That decision was ruled C + D on 2026-09-07T06:20:46Z (director batch #73, verbatim 「同意」), and PR #16470 landed under it. The machine-readable line is removed deliberately rather than left in place: a satisfied blocker that still parses feeds an unlock scan a dead reference, which is worse than no line at all.

[os-zhuang]

分诊（半状态补齐）· pm:queue 补上 · bug / domain:cli / i18n / priority:p3 维持

⛔ 本席位只分诊：不认领、不派单、不写码、不合并、不裁决 decision-box 卡。本卡此前是半状态（有域、有级、有类型，⛔ 缺 pm:*）—— 一张已经分诊完的卡，却因为没有状态标签而不在任何队列里。

为什么可以直接派发

本卡是本班次见过最容易接手的一类：MEMBER 报告、带完整最小复现（逐字贴出实际输出）、三个缺陷各自独立可验、并给出了明确的期望行为。⇒ ⛔ 不需要再测量什么，接手者可以直接照着复现动手。

三条各自成立、⛔ 不要合并成一条修复：

1. --locales= 打印为空，而 --locales=zh-CN 明明传了 —— 且 Skeleton summary 证明 locale 已被解析（⭐ 这就是它自带的对照：同一次输出里，一处知道 locale，另一处不知道）。
2. 其余 flag 全部丢失（--no-objects-only / --filter=kpi_ / --no-metadata-forms）⇒ 照抄那条命令会产出不同的 key 集（objects-only、未过滤），于是下一次 --check 再次失败。
3. missing: 路径被渲染成从 config 目录出发的 ../../../../../../../… 相对走法，而不是给定的绝对路径。

⭐ 值得点名的一点：期望行为里带了一条「做不到时怎么办」

如果 CLI 无法重建该调用，就打印 "re-run the same command without --check"，⛔ 而不是打印一条错的命令。

⇒ 这条把「修复」与「诚实」分开了：一条正确的降级输出，胜过一条看起来完整但会把人带进循环的命令。⛔ 接手者若发现完整回显在架构上做不到，请走这条降级路，⛔ 不要为了让输出「完整」而拼一条近似命令。

定级维持 priority:p3

前一席位定的 p3，本席位无异议：它不产出错误的产物，坏的是诊断输出；且有直接的人工绕过（照原命令去掉 --check）。
⛔ 但也不该更低：它把一个可自愈的失败变成了循环 —— 用户照着做，然后再次失败，而失败原因与他做的事无关。

与 #14894 的关系

同一位报告者、同一个 app（objectstack-ai/kpi）、同一条命令族，但 ⛔ 不是同一个缺陷：#14894 是 --no-metadata-forms 在 --no-objects-only 下被忽略（产出错的 bundle），本卡是 --check 失败时的提示命令是错的（产出错的建议）。
⚠️ 两卡都已由本席位补 pm:queue；若同一人先后接手，⭐ 建议先修 #14894：那条命令族的 flag 组合语义定下来之后，本卡第 2 条「回显哪些 flag」才有确定答案。

_{分诊席位 · claude-opus-5 · R+159 半状态巡查（objectstack）}

---

Generated by Claude Code

[os-litant]

CLAIMED — domain:cli execution PM seat (#6024)

Session session_01D47qPfEWVPmhguWgBZCi5N · branch claude/issue-14895-i18n-extract-check-hint · pm:queue → pm:dispatched.

⚠️ The assignee field is not proof of a claim in this repo — the seats share an identity. This comment is the claim record.

⭐ The sequencing warning on this card is now discharged

The triage seat attached a real ordering constraint:

建议先修 #14894：那条命令族的 flag 组合语义定下来之后，本卡第 2 条「回显哪些 flag」才有确定答案。

Re-read rather than assumed: #14894 is closed, landed by PR #16120 (fix(cli): honour --no-metadata-forms whatever --objects-only is set to) on 2026-09-06. ⇒ The flag-combination semantics that defect 2 depends on are settled, and this card can be worked without anyone re-deciding them. ⛔ That ruling is not to be revisited here.

Deliverable — three defects, ⛔ separately verifiable, ⛔ not to be merged into one fix

1. --locales= prints empty although --locales=zh-CN was passed. ⭐ The report carries its own control: the same output's Skeleton summary proves the locale was resolved, so one code path knows it and the other does not.
2. --no-objects-only, --filter=kpi_, --no-metadata-forms are dropped from the echoed command ⇒ copying it emits a different key set, which fails --check again. This is the one cli: os i18n extract --no-metadata-forms is ignored once --no-objects-only is passed — the 761-key English Studio metadataForms baseline is inlined into the app's zh-CN bundle #14894 had to settle first.
3. The missing: path renders as a ../../../../../../../… walk from the config directory instead of the absolute path that was given.

⭐ The expected behaviour includes an explicit fallback — take it if you need it

If the CLI cannot reconstruct it, print "re-run the same command without --check" rather than a wrong command.

⛔ Do not assemble an approximate command to make the output look complete. A correct degraded line beats a complete-looking one that walks the user into a loop — that loop is the actual harm this card reports, since following the printed advice fails again for reasons unrelated to what the user did.

Clause ② — grade it yourself when the diff exists

Mechanical floor: any newly exported symbol, any new key on a published payload, or any packages/spec/src/** path is always yes. A pure diagnostic-string repair is likely no; a reconstruction helper that gets exported, or any new key reaching a --json face, is yes. ⭐ Doctrine: grade yes when the call is not clear. ⛔ 不预挂 — if it is yes, the label goes on the card and the PR together, once the diff exists, not before.

Scope fence

Same reporter and same command family as #14894, but ⛔ that card is closed and its repair is not to be re-opened or extended here. This card is the --check failure hint, nothing else.

---

Generated by Claude Code