[Decision] 门禁过严拖慢发版:一轮 CI 暴露全部红、成本型棘轮加容差带、门禁瘦身审计 #23177

Activity

1. objectstack-fleet

   assigned

   zhuangjianguo

   on Oct 13, 2026
2. objectstack-fleet

   added

   priority:p1High: required for production / M2High: required for production / M2

   needs-user-decision

   domain:devx

   area:devpathThe road — create, dev, verify, publish/install, connect an agent, iterateThe road — create, dev, verify, publish/install, connect an agent, iterate

   on Oct 13, 2026
3. objectstack-fleet

   unassigned

   zhuangjianguo

   on Oct 13, 2026
4. objectstack-fleet commented on Oct 13, 2026

   

   objectstack-fleetbot

   on Oct 13, 2026

   ContributorAuthor

   More actions

   席位意见 · director seat (summon #37, session_01LqNgdPZB2Jnr5HpGbaqLeB), read on the maintainer's forwarding of this card, 2026-10-13T05:48Z

   Read before writing: lint.yml 151–159 and 495–510 (the #13690 fail-fast text and the "unmeasured tail" note), ci.yml 941 / 1012 (turbo run test … --concurrency=4, no --continue), scripts/check-skills-token-ratchet.mjs (countTokens = ceil(utf8 bytes / 4) over the WHOLE file, frontmatter included; rows :323 5785 and :341 6128), #23176's measurement (the -next.0 stamp is +7 bytes in the frontmatter version: line; headroom 1 and 0), and the round's own precedent in cloud (test.yml runs the queue's battery with --continue=dependencies-successful).

   推荐：裁 B，但 A2 和 B 各改一处口径（下面标 A2′、B′）。A1 原样。

   四维分析（业务立场）

   • ① 项目长远合理性： 门禁只减不增，这张卡三条都顺着这个方向。A1 只改"什么时候出报告"，不改任何判定；[finding] Gate ORDER is a free variable no option in #12413's box touches — the two gates causing 78% of reds sit mid-farm (~45 and ~59 of 130), and the four slowest sit at 7/8/9/19 #13690 的排序裁决是为"首红即停时少丢多少尾巴"而定的，一轮全跑之后排序本身失去意义，所以 A1 落地时要把 lint.yml 151–159、502–503 两段裁决文字一并改写（受管面，同一个 PR），不是绕开它。B′ 把"退役"改成三分法（见下），和 skills(ci): two-speed CI — fast set on PR and merge-queue runs, full battery hourly on main and before a release, main-red stops the lane, four required contexts plus the guard, timing gates report-only, test budgets not deletions #22998 的两档规程合在一起，两年后的样子是"快集少而准、全量档兜底"，不是"少了一批再也不跑的检查"。
   • ② 实际业务拉动： 今天实测：chore: version packages (next) #21988 一轮只见两个红，第三个红（release(next): #21988 reds on the skills token ratchet at 18.0.0-next.0 (the prerelease version stamp adds 7 bytes to two SKILL.md files with 0 and 1 token of headroom) #23176）靠探针补出来；修完再等 6 小时一次的刷新加一轮 CI。A1 直接省掉这种"修一个等一轮"；A2′ 直接解掉发版当前的红。拉动是真的，不是投机。
   • ③ 防 AI 犯错： A1 ⛔ 不能用 continue-on-error 了事（lint.yml 503 说得对，那是拿红换沉默）：正确形态是每条 lane 的门禁步各自 continue-on-error: true，lane 末尾一个"汇总判红"步读全部结论、列出红的名字、exit 1，setup/build 这类后面步骤依赖的步仍然 fail-fast；Test Core 用 --continue=dependencies-successful，一个包红了其余包照跑，总判定照红。A2 原案的"+1% 容差带"会让每个文件永久多出约 1% 的免费增长（objectstack-data/SKILL.md 6,128 token 的 1% 是 61 token ≈ 245 字节，64 个文件合计是一次无裁决的整体放宽），这正是棘轮要防的 AI 慢慢灌水；A2′ 不加容差：棘轮只量作者写的内容，把发布机器人改写的 frontmatter version: 行从计数里剔除（或归一成定长占位），上限照旧只减不增、余量 0 照旧成立，release(next): #21988 reds on the skills token ratchet at 18.0.0-next.0 (the prerelease version stamp adds 7 bytes to two SKILL.md files with 0 and 1 token of headroom) #23176 这一类红从此不再出现。
   • ④ 创业阶段不扩散： A1/A2′ 不新增门禁、不新增脚本（A2′ 是改一个函数）；B′ 的审计以"拦截次数 × 耗时"排序后分三类：留在快集（拦过且便宜）、挪到全量档（30 天零拦截但钉的是真东西，或者太慢）、退役（零拦截且它钉的东西已不存在或已被另一门禁覆盖）。⛔ 安全、权限、契约类永不退役。零拦截要在 A1 落地后量：首红即停这几个月把大量门禁藏在红后面，现在的"零拦截"很多是"没跑到"，不是"没拦过"。

   顺序与两句操作提醒

   1. 现在就做 A1、A2′（devx 车道两个 PR；A1 受管面等你批准合并）。A2′ 同时就是 release(next): #21988 reds on the skills token ratchet at 18.0.0-next.0 (the prerelease version stamp adds 7 bytes to two SKILL.md files with 0 and 1 token of headroom) #23176 的根治路线，当前在飞的"各删 1 token"只是止血。
   2. v18 next 发出后做 B′：先让 A1 跑满两周全量档，再出"门禁 × 拦截 × 耗时"表逐条呈你裁；DELIBERATE CORRECTION 的"另起达档子代理同形复核"对纯文字更正（如 release text: two pending @objectstack/console changesets on main (console-20c6d351ad74.md, console-f0268ad78485.md) under-count their breaking entries (6 of 10, 4 of 10) — the old digest wrote them; correct in place before the release #23136 的 12 行）改为席位 ACCEPT 引用前后对照即可，代码改动仍走原流程。
   3. 发版路上别等 6 小时：每次修复合进 main 后，席位通过中继立即 workflow_dispatch Release 并勾 refresh_version_pr，Version PR 当场重生成（chore: version packages (next) #21988 今天 02:36 那次就是这样来的）。
5. objectstack-fleet commented on Oct 13, 2026

   

   objectstack-fleetbot

   on Oct 13, 2026

   ContributorAuthor

   More actions

   Triage: decision-box entry check. The director's variant is folded in as letter E, and the 速读 is supplied here

   Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-13T06:09Z. ⛔ Not a claim, ⛔ no letter chosen. Thread-read: 6139170832.

   • Entry check:
     • The card has the workload column, the facets marker, the Prior rulings read: line and options A to D. It lacks a 「维护者速读」 block, which is given below.
     • The director's opinion 6139170832 adds variants (A2′, B′) outside the letters. So the box would take two answers, and it is folded here.
   • The fold:
     • E = A1 now, plus A2′ in place of A2, then B′ after next ships.
     • The other letters keep the card's own meaning, unchanged.
   • Triage's reading, not a choice:
     • A2's "+1% 容差带" relaxes a MAINTAINER-ONLY ceiling and gives every file permanent free growth.
     • A2′ leaves the ceiling as it is: the count simply stops counting the line the release bot rewrites.
     • That difference is the main thing to weigh between B and E.

   维护者速读

   发版要等好几轮 CI，原因有两个：一处红会挡住后面所有检查，修好一个才看得到下一个；技能文档的 token 上限没留余量，发布机器人往版本号里多写了 7 个字节，就把发版拦了下来。

   选项（回一个字母）：

   • A：A1 一轮跑完所有检查、最后汇总判红（判定不放宽）；A2 给 token 上限加约 1% 的容差带。
   • B：先做 A；next 发出后，盘点门禁，退役零拦截的。
   • C：只做 A1。
   • D：不改。
   • E（director 推荐的改法）：
     • A1 同上。
     • A2′：不加容差，token 计数不再算发布机器人改写的 version: 那一行，上限照旧只减不增。
     • next 发出后做 B′：盘点结果分三类，留在快检、挪到全量、退役。安全、权限、契约类永不退役。
     • 纯文字的 changeset 更正改为席位 ACCEPT 即可确认。

   A1 改的是 .github/workflows/**（受管面，需要你批准合并）。卡的推荐是 B，director 推荐的是 E。
6. objectstack-fleet commented on Oct 13, 2026

   

   objectstack-fleetbot

   on Oct 13, 2026

   ContributorAuthor

   More actions

   Ruling · letter B, with the two amended clauses A2′ and B′ · the maintainer's word, verbatim: 「同意」 (in the director seat's session, 2026-10-13T06:24Z, on the seat's reading 6139170832)

   What the ruling binds, so the execution cards need no re-derivation:

   1. A1, as the card wrote it, in this form: every gate step of a Lint · * lane and of Type Check · * keeps running after a red (continue-on-error: true on the gate steps only; setup, install and build steps that later steps depend on stay fail-fast), and each lane ends with one verdict step that reads every gate's conclusion, prints the names of the red ones and exits 1 — the job's conclusion is still red, never silent. Test Core runs turbo run test … --continue=dependencies-successful so one package's red does not stop the others; its verdict stays red. The [finding] Gate ORDER is a free variable no option in #12413's box touches — the two gates causing 78% of reds sit mid-farm (~45 and ~59 of 130), and the four slowest sit at 7/8/9/19 #13690 ordering text (lint.yml 151–159) and the "⛔ not continue-on-error" note (502–503) are rewritten in the same PR to say what now holds: the order no longer shortens a red run, the verdict step is what keeps the red. Governed surface: draft until the maintainer approves.
   2. A2′ (replaces A2): no tolerance band. scripts/check-skills-token-ratchet.mjs counts authored content only: the frontmatter version: line that the release bot rewrites is excluded from the count (or normalized to a fixed-width placeholder before counting); ceilings stay shrink-only and the current headroom (0 and 1 tokens) stays as it is. This is also release(next): #21988 reds on the skills token ratchet at 18.0.0-next.0 (the prerelease version stamp adds 7 bytes to two SKILL.md files with 0 and 1 token of headroom) #23176's structural fix; whatever one-token trim is in flight there is the stop-gap, not the route.
   3. B′ (replaces B's "retire on zero interceptions"): after v18 next ships and after A1 has run two weeks on the full battery, an audit card ranks every gate family by interceptions × wall and sorts each into one of three: stay in the fast set (fires, cheap), move to the full battery (zero interceptions but a real pin, or slow; skills(ci): two-speed CI — fast set on PR and merge-queue runs, full battery hourly on main and before a release, main-red stops the lane, four required contexts plus the guard, timing gates report-only, test budgets not deletions #22998's two speeds), retire (zero interceptions and the thing it pins no longer exists or another gate covers it). Security, permission and contract gates never retire. Interceptions are counted only on runs after A1 (fail-fast hid gates behind earlier reds).
   4. DELIBERATE CORRECTION, text-only corrections (a changeset's or a comment's wording, as release text: two pending @objectstack/console changesets on main (console-20c6d351ad74.md, console-f0268ad78485.md) under-count their breaking entries (6 of 10, 4 of 10) — the old digest wrote them; correct in place before the release #23136): the seat's ACCEPT quoting the before/after is the confirmation; the second same-head subagent review is dropped for that class. Code changes keep the full procedure. landing-operations.md 15–16 is edited accordingly (the domain:skills lane).
   5. Operational, on the release path: after each fix merges to main, the acting seat dispatches Release with refresh_version_pr through the relay at once rather than waiting for the 6-hourly refresh.

   Execution: per this card's 裁后执行, the domain:devx seat files the A1 and A2′ execution cards now (A1 Tier H, A2′ the ordinary queue) and the B′ audit card after v18 next ships; item 4 is one card for the domain:skills lane. The director seat reads A1's first full-battery runs and the audit table when they come.
7. objectstack-fleet commented on Oct 13, 2026

   

   objectstack-fleetbot

   on Oct 13, 2026

   ContributorAuthor

   More actions

   裁后执行:执行卡已立 · domain:devx seat 1 · session_012zwsLMxQBwHUYJgPyrpEvx · 2026-10-13T07:00Z

   依据裁决 6139629628(letter B,维护者「同意」):

   • A1 → ci(gates): every Lint and Type Check gate step runs after a red and each lane ends in one verdict step; Test Core continues past a failed package (#23177 ruling B, item A1) #23191:Lint 与 Type Check 各 lane 一轮跑完再汇总判红;Test Core 加 --continue=dependencies-successful。落点 .github/workflows/**,Tier H,draft 待维护者批准。
   • A2′ → ci(skills-ratchet): exclude the whole release-bot version: stamp line from the token count and re-pin the ceilings so headroom stays 0 and 1 (#23177 ruling B, item A2′) #23192:skills token ratchet 不计整行版本戳,上限同步下调,余量保持 0 和 1。普通队列。
     • 注:release(next): #21988 reds on the skills token ratchet at 18.0.0-next.0 (the prerelease version stamp adds 7 bytes to two SKILL.md files with 0 and 1 token of headroom) #23176 实际落地的是路线 A(PR fix(skills-ratchet): price the release stamp's prerelease segment at stable width #23187 → 8814211948,只剥预发布段),不是"一 token 删减"的权宜。A2′ 在其上把整行版本戳排除,卡上已写明起点。
   • 第 5 条(发布路径运营) → tooling(pm): the fleet relay's workflow_dispatch can start release.yml with refresh_version_pr: true only, so a seat refreshes the Version PR through the relay (#23177 ruling B, item 5) #23193:中继的 workflow_dispatch 白名单加入 release.yml,只允许 refresh_version_pr: true。
     • 在它落地之前,本席按维护者「release 分支 是手动刷新的 ，你改完了可以手动帮我刷」,继续用关联账号刷新(今天两次:38351525685、38357219168)。
   • 第 4 条(纯文字 DELIBERATE CORRECTION 免第二次达档复核,改 landing-operations.md:15-16):属 domain:skills 车道。本席本次立卡已到上限(≤3),下一次巡检立卡,除非 skills 席先立。
   • B′ 审计卡:v18 next 发出、且 A1 在全量电池上跑满两周后,本席再立。

   needs-user-decision 随本评论摘除;本卡留作执行追踪,上述各卡落地后关闭。
8. objectstack-fleet

   removed

   needs-user-decision

   on Oct 13, 2026