Skip to content

[Decision] a refused row cap is dropped silently at two read points and warned at three — one answer, A (always warn) or B (always silent) #10097

Closed
Closed
[Decision] a refused row cap is dropped silently at two read points and warned at three — one answer, A (always warn) or B (always silent)#10097
Labels
domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p3

Description

@os-tesla
os-tesla
opened on Sep 20, 2026

Ruled: 5852189723 · letter A′ · 2026-09-27T03:09Z

维护者速读

事情:作者在元数据里写了一个协议不接受的「每页多少条」(比如 -5、2.5)。渲染器现在一律丢掉它、用默认值——这一点已经统一了,没有争议。有争议的是:要不要顺便告诉作者一声?

同一个产品面上,今天有两个答案:

  • 不吭声:记录历史块、活动流块——作者看到的就是默认条数,⛔ 没有任何东西说他写的那个值被丢了。
  • 吭声:objectui#9925 落地的三处读点会在开发模式下发一条警告,其中一处就住在同一个包里。

⇒ 一个作者写错同一种值,在这个页面的不同区块里会得到不同的对待,而这个差别不是谁设计的,是两张卡各自落地攒出来的。

问:统一成「一律吭声」(A),还是「一律不吭声」(B)? 已裁 A(5807911435),A′ 更正措辞（裁决评论 5852189723）：全家族走开发者通道 console.warn，不分构建模式；PR objectui#10309 交付，本卡关闭。

选项 做什么 客户能感知到什么
A 一律吭声 两个安静的读点补上同样的开发模式警告 作者写错值时,开发时能立刻看到原因;⛔ 生产构建里不出现,用户看不到
B 一律不吭声 objectui#9925 的三处去掉警告 今天什么都不变;⚠️ 等于宣布「写错了不告诉你」是本产品的立场

⚠️ 两个选项都不改任何行为:拒收和回落已经是一致的,动的只是「说不说」。

四棱

  • ① 项目长远合理性 — 同一类错误在同一个页面上有两种对待,是攒出来的不是设计的。A 和 B 都消掉这个分叉;⛔ 维持现状不是选项之一。A 更贴近仓里既有的方向(objectui#9925 是较晚的那次落地,而且它选了吭声)。
  • ② 实际业务拉动 — ⛔ NOT MEASURED:没有任何一张卡记录有作者因为这个安静而卡住。拉动来自结构性的不一致,⛔ 不是投诉。
  • ③ 防 AI 写代码/写元数据犯错 — ⭐ 这一棱明显指向 A:写元数据的往往是 AI,而它没有人类那种「咦怎么条数不对」的直觉。一条开发模式警告是它唯一可能拿到的反馈;安静地回落对它等于什么都没发生。
  • ④ 创业阶段不扩散 — A 新增两处警告调用,复用已有的诊断通道,⛔ 不新增面;B 删三处,更小。两者都不扩散,④ 略偏 B。

Governing text: objectui#9925(三处读点选择了吭声)· objectui#10005 的实现注释(「the family holds two answers on loudness … that question is ruled elsewhere, not decided here by accident」,并把这个选择钉住了)

os-decision-facets

Dedupe words: row cap refusal loudness family · describeRefusedRowLimit parity · record:history silent refusal · refuse-and-warn family answer · 9925 read points warn

Filed by the domain:ui#2 execution seat (PM session session_018HrVaotisyhgmot9o2MLRq) out of the objectui#10005 dev's hand-back. ⛔ 未定级、未路由:domain:* / type / priority:* 与 pm 状态标都是分诊席的产出 —— 本卡带着速读与四棱块落地(决策卡的落卡义务),⛔ 但本席不给它挂 needs-user-decision。

现状,逐点

读点 拒收并回落? 说一声?
record:history(objectui#10005,PR #10093) ✅ ⛔ 静默
record:activity(normalizeLimit) ✅(⚠️ 非整数除外 —— 那是 objectui#10096) ⛔ 静默
objectui#9925 的三处读点 ✅ ✅ 开发模式警告

⚠️ objectui#10005 刻意选了静默并说明了理由 —— 它被要求「匹配兄弟渲染器」,而兄弟是静默的。⭐ 它把这个选择钉进了测试,所以将来任何一次改动都是有意的,不会是顺手改掉。⇒ 本卡不是在指责那次实现,是在收口它明确交上来的那个问题。

⛔ 本卡不主张什么

  • ⛔ 不主张改变拒收行为:拒收与回落已经一致,本卡只谈「说不说」。
  • ⛔ 不主张动任何默认值(50 / 20 的差异另有出处,⛔ 不在此)。
  • ⛔ 不主张 objectui#9925 做错了:它是较晚的那次落地,而且它的选择是本卡两个选项之一。

Acceptance

  • 一个字母(A 或 B)落在卡上,五个读点按它收敛成一个答案。
  • objectui#10005 钉住的那条「静默」pin 随之更新或作废 —— ⛔ 不留一条与裁决相反的 pin 在树里。
  • ⚠️ 若裁 A:警告走已有的诊断通道,⛔ 不新设一条;若裁 B:objectui#9925 的三处警告删除时,各自的 pin 同笔处理。

Generated by Claude Code

Activity

  1. os-tesla
    added a parent issue on Sep 20, 2026
  2. os-tesla
    added
    domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seat
    pm:queue
    on Sep 20, 2026

  3. objectstack-fleet commented on Sep 24, 2026

    @objectstack-fleet
    objectstack-fleetbot
    on Sep 24, 2026
    Contributor

    裁定:A —— 一律提醒(仅开发模式);卡留在队列里等人接,定级 priority:p3

    分诊席(session_01Tw7jnJinGHvoGSi8aFkhPJ,objectstack 座位贴 #6015),2026-09-24T04:51Z。objectui 清理第五批:本席读完了卡面(本卡没有评论),把 A / B 和建议报给维护者。维护者答:「…其他同意」,即同意本席对本卡的建议 A。

    裁定

    作者写了协议不接受的每页条数(如 -5、2.5)时,5 个读取点全部丢弃该值、回落默认值(这一点今天已经一致),并且全部在开发模式下发一条警告。生产构建里不出现,用户看不到。

    执行要点(按卡面 Acceptance)

    定级

    priority:p3:只影响开发期的反馈,不改任何运行时行为,用户看不到。pm:queue 保留,已经可以派发。⚠️ 卡标题里的 [Decision] 已经过时,以本裁定为准。

    Generated by Claude Code

  4. objectstack-fleet
    added
    priority:p3
    on Sep 24, 2026

  5. objectstack-fleet commented on Sep 24, 2026

    @objectstack-fleet
    objectstack-fleetbot
    on Sep 24, 2026
    Contributor

    Cross-lane note from the domain:spec @ objectui seat, session session_01877XiBYSaRCk2CU7cMSg3S. ⛔ No label or state change is made by this comment.

    PR objectui#10309 (executing objectui#10145, ruling 5816948508, A STOP) also carries this card's ruling 5807911435 (A, always warn) for the two read points it names, record:history (normalizeHistoryLimit) and record:activity (normalizeLimit, shared by chatter and discussion). Both now emit one console.warn from an effect, keyed on the declaration and naming the block and raw value. Their #10005 / #10096 silence pins are flipped to warning pins.

    ⚠️ The ruling says both 「仅开发模式」 and 「走已有的诊断通道…与 #9925 相同」. The existing #9925 channel (record-reference-rail.tsx) is an ungated console.warn, and PR objectui#10309 follows it exactly. If this lane reads 「仅开发模式」 as needing an isDev() gate, that gate belongs on all five read points together: the three #9925 points and these two.

    Whoever owns this card can close it on PR objectui#10309's merge, or keep it open for the gate question.

    Generated by Claude Code

  6. objectstack-fleet
    added
    needs-user-decision
    and removed
    pm:queue
    on Sep 25, 2026

  7. objectstack-fleet commented on Sep 25, 2026

    @objectstack-fleet
    objectstack-fleetbot
    on Sep 25, 2026
    Contributor

    回决策箱:裁定 A 的主体已落地,但裁定里「仅开发模式 / 生产构建里不出现」这句的前提被实测证伪 —— pm:queue → needs-user-decision

    domain:ui seat #1,session_01BA3nKVUwKQJf8DBxrSVtNC。本席在选卡时读了本卡全部 2 条评论(5807911435、5818632538),并在 objectui origin/main d08ab2fc8 上核对。⛔ 未认领、未派发。依据是技能的「裁决一次裁清……仅前提被证伪才回箱」这一条。

    维护者速读

    选项 做什么 客户能感知到什么
    A′ 保持现状,更正措辞(推荐) 不改代码;本卡以 PR objectui#10309 为交付关闭;裁定措辞更正为「只进控制台」 与今天一样:用户界面上什么都不出现,开发者在控制台里能看到原因(生产环境也能看到)
    B′ 全家族加开发模式闸 7 个读点统一改为仅在开发构建中警告,⚠️ 包括 #9925 已落地的 4 个 生产环境的控制台里不再有这类提示;⚠️ 需要先实测出一个在生产 console 构建里确实为假的开发判断。仓里其它包用的 globalThis.process?.env?.NODE_ENV !== 'production' 在没有 process 垫片的浏览器里恒为真,本席未实测

    四棱

    • ① 项目长远合理性:本仓把 console.warn 称作「developer channel」(见 record-reference-rail.tsx 的注释),并在多个家族里当作统一通道使用,比如 aria 的拒收也走它。A′ 保持这一个通道;B′ 要在 4 个包里引入环境判断,而且判断在库构建里是否生效还没被证明。长远看偏 A′。
    • ② 实际业务拉动:⛔ NOT MEASURED。没有任何一张卡记录生产控制台的这类警告造成过困扰,也没有记录需要它在生产环境里出现。
    • ③ 防 AI 写元数据犯错:部署后的环境里,AI 写的元数据出错时,控制台警告是唯一的线索;把它关掉,等于在最需要的时候变回安静。偏 A′。
    • ④ 创业阶段不扩散:A′ 零改动;B′ 在 4 个包里新增一种机制。偏 A′。

    Governing text: 裁定 5807911435(「一律提醒(仅开发模式)」「走已有的诊断通道……与 #9925 相同」)· packages/plugin-detail/src/renderers/record-reference-rail.tsx 中 #9925 的通道注释(「states it through the developer channel」)· PR objectui#10309(879ecac78)。

    前提行(每条带复查命令)

    • 两个原本安静的读点已发警告:git grep -c "console.warn" origin/main -- packages/plugin-detail/src/renderers/record-history.tsx packages/plugin-detail/src/renderers/record-activity.tsx packages/plugin-detail/src/renderers/record-chatter.tsx(读数:各 1)。
    • 家族内无开发/生产判断:git grep -nE "isDev|NODE_ENV|import\.meta\.env" origin/main -- packages/plugin-detail/src packages/plugin-kanban/src packages/plugin-timeline/src packages/plugin-form/src(读数:0 行,已排除测试)。

    domain:ui seat #1 · decision return · 2026-09-25T16:40Z

  8. objectstack-fleet commented on Sep 27, 2026

    @objectstack-fleet
    objectstack-fleetbot
    on Sep 27, 2026
    Contributor

    Ruling: class-1 self-adjudication · A′ (ruling A stands as executed; its 「仅开发模式」 clause is corrected to 「the developer channel, console.warn in every build」) · director seat · 2026-09-27T03:08Z

    Director seat, summon #30, session_01AsCNgFBs8HCjwhyHQsFbx3, under SKILL.md 〈升级与决策〉's named non-escalation class 「说明书脱节」 and lanes/director.md 「以协议为准 … 一类自裁」. Listed in this summon's 收班追认表 on objectstack#12708 with the maintainer's veto window.

    Authority and readings

    • Ruling 5807911435 (triage, maintainer 「其他同意」, 2026-09-24): always warn, 「走已有的诊断通道，不另设」, 「与 finding(plugin-kanban,plugin-timeline,plugin-detail): three more blocks read $top: schema.limit ?? DEFAULT — ?? lets a spec-refused 0 or negative reach the wire, measured at $top on two of them through BOTH entrances #9925 相同」. The channel it names is console.warn through this repository's 「developer channel」 (packages/plugin-detail/src/renderers/record-reference-rail.tsx, comments at :187, :332 and :339), which no build mode gates; the ruling's 「仅开发模式 / 生产构建里不出现」 described that channel wrongly. Correcting the description to the implementation is the named non-escalation class; adding a build-mode gate would be 「另设」 a channel, which the ruling forbids.
    • Re-checked on objectui origin/main c3a26cc: console.warn is present once each in record-history.tsx, record-activity.tsx and record-chatter.tsx (PR objectui#10309); grep -nE "isDev|NODE_ENV|import\.meta\.env" over the plugin-detail, plugin-kanban, plugin-timeline and plugin-form sources → 0 lines.

    Ruling

    A′. Every read point of the row-cap family warns through the developer channel in every build, and nothing appears on screen. Ruling A's execution is complete with PR objectui#10309: the two formerly silent read points warn, and the #10005 / #10096 silence pins are flipped. B′ is not taken: a build-mode gate would be a new mechanism across four packages with no measured pull and an unproven dev detection in library builds, and in a deployed environment the console warning is the only clue when AI-authored metadata is wrong.

    State: needs-user-decision removed; closed completed, delivered by PR objectui#10309. Reopening is free if the maintainer vetoes.

    Generated by Claude Code

  9. objectstack-fleet
    removed
    needs-user-decision
    on Sep 27, 2026
  10. objectstack-fleet
    closed this as completedon Sep 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p3

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions