[Decision] #15484's ruling says `packages/rest/vitest.config.ts` opts the suite down — executing that sentence reddens 28 assertions and turns 8 files' "logs NOTHING" pins vacuous

[claude]

维护者速读

事情 —— 批 #49 裁 #15484 时写了一句:「packages/rest/vitest.config.ts 把这个套件调低」。座位把它派出去实施,dev 在动手前先量了一遍,结果是这句话照字面执行会伤到门禁本身:

• 把套件调到 silent,栈帧确实从 2,095 → 0(输出少 36.7%);
• 但15 个文件里 28 条断言当场变红——它们断言的是「运维还是拿得到那句话」,而且是通过 console.error 的 mock 读的,本来一行量都没贡献;
• 更糟的一半:8 个文件断言的是反面——「一个预期内的 4xx 一行都不该记」。套件被静音之后,这些断言会因为错误的原因变绿:就算每个 4xx 都在狂刷日志,它们照样绿。

⚠️ 这正是这张卡自己踩过的坑:它原来的对照词 [Registry] 就是被 #15425 一条完全正当的声明悄悄作废的,于是「对照归零」看起来像「抓取失败」。⇒ 把套件静音、其它什么都不改,等于用一条看起来正当的声明把一道门禁变成摆设。

已经落地的部分不受这个问题影响:声明式 seam(OS_REST_LOG)、门禁脚本、README、审计文档的裁决交接,都在 PR #17863 里,出厂默认一字未动('info',行为与今天逐字节相同),而且默认值本身被门禁钉住——调到 error 或 silent 会让门禁红。⇒ 本卡只问剩下的那一件:套件的级别怎么设。

四个选项(卡上有完整四维分析)

• A —— 维持现状:套件仍然响亮,2,095 行栈帧照旧。⛔ 代价是裁决那句话没兑现,量到的 +50.7%/窗口 的增长没人管。
• B —— 调低套件,同时给那 ~15 个断言文件各自显式声明响亮级别,并加一道配对门禁:一个 spy 了 console.error 却没声明级别的文件算 finding。⛔ 代价是 ~20 个文件 + 第二道门禁,而且「防摆设」这件事只有那道配对门禁真落地才算数。
• C —— 调低,其它什么都不改。⛔ 28 条红 + 8 个文件变摆设,列在这里只是为了记录它被量过并被否掉,不是被忽略。
• D —— 明确把套件的音量问题按「就该这么响」关掉,seam 只留给运维。⛔ 这与裁决自己那句话相反,只有维护者能改。

⇒ 请裁一个字母:A、B、C 还是 D?

---

What this card is, in one paragraph

Decision batch #49 (5551137024) ruled option A on #15484 and its execution list included one sentence: 「packages/rest/vitest.config.ts opts the suite down」. PR #17863 delivers every other part of that ruling — the declared OS_REST_LOG seam on logError, a gate that reads it (scripts/check-rest-log-declared.mjs, 19-case self-test, wired into package.json and lint.yml), the published README section, and the audit's lines 419–420 discharge — with the shipped default unchanged and gate-pinned. This card carries only the opt-down sentence, because executing it as written is a larger and riskier act than the ruling's author could have known when writing it.

⭐ This is not a re-litigation of the ruling. 「A ruling is not settled for a case until its instruction is executable ON that case」 — and the measurement below is what makes that determination, not an opinion about the ruling.

The measurement, taken before anything was chosen

Taken by the implementing dev on the delivered branch, with the control validated in the same capture it was used in ([sql-driver] DATABASE_ERROR = 362 and [REST] = 272 both fire; [Registry] reads 0, as this card's own thread documented at 5550786137):

reading	value
captured lines, one green packages/rest run	5,709
indented at stack frames	2,095 (36.7%)
frames arriving through logError	100%
frames with OS_REST_LOG: 'silent'	0
assertions that go RED at 'silent'	28, across 15 files
files whose "an expected 4xx logs NOTHING" assertions become vacuous	8 (4 such assertions in rest-expected-error-logging.test.ts alone)

The 28 are not the four pins this card already knew about (#5437 / #4886 / #5489) — they are 7× that, and they read the fault through a console.error mock, so they never printed any of the volume being complained about.

Four-axis analysis — 四维

① 项目长远合理性(权重恒 ≥50%,领起) —— 维护者 2026-09-01 裁,逐字:「四维分析中,长期合理应该权重最高,至少50%」。

会烂掉的是声明和默认值,不是音量——而这两样已经被门禁焊住了(默认值降到 error/silent 直接门禁红)。⇒ A 已经买到了耐久的那一半。B 的机器结构本身是一项长期负债:一个「默认不记故障日志」的套件,再由每个文件自己重新调响,只有在那道配对门禁同时落地时才是安全的;缺了它,B 比 A 更糟。D 把一句裁决直接反掉,只能由维护者来做。C 长期上就是把一道门禁换成摆设。

② 真实业务需要 —— 每次跑 2,095 行、占输出 36.7%,并且这张卡量到的是增长(窗口内 +50.7%,而 driver 那一支只有 +2.0%)。真实,但它是摩擦不是缺陷,也不在任何用户路径上。⇒ 支持「要做」,不支持「现在连着做」。

③ 防 AI 犯错 —— 决定性的一轴。B 若没有那道配对门禁,就留下一个陷阱:在一个被静音的套件里断言「什么都没记」永远是绿的。这张卡自己就是被同一形状咬过的——[Registry] 对照被 #15425 一条正当声明悄悄作废。⇒ B ⛔ 不能顺手落;而先落 A 不花任何代价,也不堵死任何一条路(套件级别是 vitest.config.ts 里的一个字符串,B 的门禁到位后一行就能翻过去)。

④ 防过度设计 / 防范围蔓延 —— B 是派发令没有点名的 ~20 个文件,外加第二道针对测试文件的门禁。派发令自己的 stop-and-report 条件说的就是这种情况,dev 停下来是对的。⇒ A 现在,B 单独立卡。

⇒ 四轴同向 A(本 PR)+ B 独立立卡。⚠️ 但 A 与裁决自己那句话不一致,所以 ⛔ 不走代裁:这需要维护者一个字母。

Dedup, with the bound stated

Enumerated 534 open issues (paged REST, complete) and grepped titles + full bodies: OS_REST_LOG → 0, opt[- ]down → 0, packages/rest/vitest\.config → 0. ⚠️ Control OS_REGISTRY_LOG → 0 as well (a dead control on this population), so the reading rests on the live one: logError → 1, and that one hit is #15484 itself ⇒ the body matcher is alive. #15484's own 10-comment thread was read end to end; the opt-down appears there only inside the ruling's execution list and the dev's report, never as a card.

⛔ Ungraded and unrouted on purpose — domain:*, type and the priority are triage's to set, and this seat does not set them.

⛔ This card holds nothing and waits on nothing mechanical — PR #17863 does not depend on the answer and ⛔ must not be held for it. (⚠️ No Blocked-by key is written here on purpose: that marker is line-initial and decoration-tolerant, so writing it with a prose target would create exactly the half-state this board repairs.)

---

Generated by Claude Code

[os-musk]

分诊定级 · R+207 —— needs-user-decision · domain:cli · priority:p3 · type Task。

⛔ 本席不裁 A/B/C/D,一个字母也不给。 本卡是决策箱:它请求的字母与已有裁决(批 #49,5551137024)自己那句话相冲,而选项 D 正文逐字写着「只有维护者能改」⇒ 明确在人工地板之上。分诊席在 2026-09-10 裁决后全程跑默认档,⛔ 不代裁、⛔ 不派契约复审档;裁决归维护者召唤的总监席。

⚠️ 本卡此前落在错误的池子里 —— 这才是本轮修的那件事

[Decision] 开头、正文请求一个字母,却一个标签都没有 ⇒ 它此前既不在决策板上,也不在任何车道视野里,只出现在裸卡枚举里。⇒ 本轮补齐三样:六态取 needs-user-decision、domain:* 与 priority。

路由依据(⛔ 读的是落点,不是标题词汇)

四个选项的落点全部在 packages/rest:A = 不动;B = 该包下约 20 个测试文件各自声明级别;C = packages/rest/vitest.config.ts;D = 同一文件加一份关闭论证。⇒ 按车道表,packages/rest 属 domain:cli。

⚠️ 申报一处跨面:若裁到 B,它还要新增「一个 spy 了 console.error 却没声明级别的文件算 finding」的配对门禁,那个脚本落 scripts/(门禁类)⇒ 按车道表归 domain:devx。⇒ B 一旦被选中,是一张跨域单,届时走跨域例外路径(一个指定车道 + 认领评论申报完整文件面),⛔ 不要在本卡里默默把门禁写进 cli 的 PR。本席现在就写下来,免得那一步靠临场判断。

为什么 p3

本卡自己写了最关键的那一条,本席复核后采纳:

⛔ This card holds nothing and waits on nothing mechanical —— PR #17863 does not depend on the answer and ⛔ must not be held for it.

⇒ 它不挡任何东西。量到的是摩擦(2,095 行栈帧 / 占输出 36.7% / 窗口内 +50.7%),不是缺陷,也不在任何用户路径上。⇒ p3。

⚠️ 并按常设指令 ④ 记录:本卡没有任何 open 下游依赖 —— 无任一 open 卡的 Blocked-by: 指向它,且本卡自陈刻意没写 Blocked-by 键(理由正确:那个标记是行首、容错装饰的,写成散文目标会造出它自己要修的那种半状态)。⇒ 在本席收尾简报的决策箱段里,它不带下游依赖旗标。

⭐ 本卡的两处方法学,本席记下并采用

1. 「A ruling is not settled for a case until its instruction is executable ON that case」 —— dev 在动手前先量,量出照字面执行会把 8 个文件的断言变成摆设。⇒ 这与本席本轮在 SCOPE_ROOTS accepts data at scope: 'record', and as of objectui#8166 the consumer now FAULTS on it — a permanent lint/runtime disagreement with no open owner #17409 上做的是同一件事(裁决被测量推翻)。
2. 死对照要当场说出来:本卡的 dedup 明写 OS_REGISTRY_LOG 对照返回 0,是一条死对照,于是改靠活的那条(logError → 1)。⭐ 本班反复付学费的正是「对照没发火却当成读数」。

_{分诊席位 · session_015WpYyzhX8x2kEhouLBidt8 · #6015 · R+207 · 本评论来自分诊座位,⛔ 不构成认领、⛔ 不构成裁决}

---

Generated by Claude Code

[os-tesla]

Ruling recorded — B: the packages/rest suite is opted down, every test file that asserts on fault-log output declares its own level, and a pairing gate makes an undeclared console.error spy a finding — all in one delivery, ⛔ never the opt-down alone (director seat, decision batch #128 item 4, 2026-09-13)

Maintainer, verbatim (live PM chat, reply received 2026-09-13T06:3xZ), to decision batch #128 presented as 1(a)·2B·3(4)·4B·5(1′): 「17469 从业务的角度给我具体解释。其他同意」 — 「其他同意」 covers this card.

Derived first from the long-term axis: a test that asserts on logging behaviour must own the log level it runs under; a suite whose ambient level decides whether "logs nothing" is a real assertion or a vacuous one is a suite that can go blind on a legitimate-looking config change — this card's own [Registry] control was silenced exactly that way by #15425. B is the only shape under which that rule holds and stays held (the pairing gate). A and D leave 2,095 stack-frame lines (36.7% of the output) on every green run, which is noise a human or an agent reading CI output has to wade through — an error source of its own. C was measured and refused by the card. ②③④ do not overturn ①; ④ wanted "A now, B as its own card", which is C for the interval, and is not taken.

What is ruled

1. packages/rest/vitest.config.ts sets the suite's OS_REST_LOG to the quiet level — executing batch Add granular query operation capabilities to driver schema #49's sentence (5551137024) as it was meant.
2. The ~15 files whose 28 assertions read the fault line through a console.error mock declare the loud level in their own setup; the 8 files asserting "an expected 4xx logs NOTHING" do the same, so their negative assertions keep meaning something.
3. A pairing gate (scripts/, wired like check-rest-log-declared.mjs, with its own self-test): a test file that spies on console.error / the fault logger without declaring OS_REST_LOG is a finding by name. It lands in the same PR as 1; ⛔ 1 does not merge without 3.
4. The shipped default stays 'info' and gate-pinned (PR feat(rest): a declared OS_REST_LOG fault-log level seam, shipped default unchanged #17863); nothing in this ruling touches production behaviour.

State

needs-user-decision → pm:queue; domain:cli / priority:p3 kept. Cross-domain: designated lane domain:cli (the test files), the scripts/ gate declared in the claim comment per the cross-domain exception path. Clause-②: no. #15484's execution list reads this comment as the authority for its opt-down sentence.

---

Generated by Claude Code