You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Decision] next codemod splits for the large hot files, in order, and whether to name a shrink-only line ceiling (hot-file card F) #33949
Filing gate ③: maintainer-directed. On 2026-11-15 the maintainer chose 「今天改规则,并立全部 6 张卡」 on the hot-file serialization decision card (consequence as shown: 取消 protocol.ts 独占、关闭 #25467 和 #24586;卡 A 到 F 交各车道立卡,大 PR 和上限门禁仍逐个等您批准). Measurements: the hot-file analysis report (project artifact), re-runnable on request. Cross-lane rule (2026-11-15): no live seat in the owning lane, so domain:server seat 5 files and builds it; the owning lane is notified.
Card F: decision for the maintainer
Which large files get the next codemod splits (the protocol.ts codemod precedent: #29998, #30687, #30954, #31177), in this proposed order:
packages/objectql/src/registry.ts
metadata-manager.ts
mcp-http-tools.ts
auth-manager.ts + auth-plugin.ts
service-automation engine.ts + plugin.ts
action-execution.ts
marketplace-install-local-plugin.ts
spec stack.zod.ts
And whether the maintainer names a shrink-only line ceiling for these files (a new gate needs the maintainer's naming).
The seat batches this with other maintainer questions behind one independent review, then puts a card in Chinese. No dev before the ruling.
stack.zod.ts, which is a published contract: bring it back for its own approval before starting.
Each split is generated by script against fresh main right before it is queued. The original file stays as a forwarding entry, so public exports are unchanged. A split waits for any open PR touching that file to merge first. Add approval-service.ts (10,697 lines) to the next round.
2. Line ceiling: yes, narrow form only.
It applies only to files already split, at their post-split line count plus a small margin.
Going over is an error that tells the author to put new code in a new module.
Raising a ceiling needs the maintainer's ruling.
Files not yet split get no ceiling, at most a warning.
Grade. p3 → p2. The splits cut merge-queue conflicts and per-seat token cost, both live constraints this week. Each split PR is large and keeps its own maintainer approval, as the hot-file ruling set.
Activity
objectstack-fleet commentedon Nov 15, 2026
triage#1 · hotlong · session_01Q4EjjMnyLqJdzuktEmRPXH
Path: none
Ruled: split order and a narrow ceiling ·
needs-user-decisioncleared →pm:queue· p2 · 2026-11-15T16:15ZThe maintainer ruled on the triage thread on 2026-11-15 (「都同意」) after an independent analysis, as set out below.
Measured on origin/main
bc6b7ffd45, last 14 days (2,504 merges repo-wide).registry.ts: 12,438 lines (was 7,610), 60 changes, 8 yesterday. It is now larger thanprotocol.ts(11,616).action-execution.ts: 6,629 lines, 41 changes.mcp-http-tools.ts: 3,893 lines (was 1,653), 53 changes.metadata-manager.ts: 4,947 lines, 31 changes.stack.zod.ts: 9,469 lines, 29 changes.protocol.tswent from 30,019 to 11,616 lines and objectql engine from 22,736 to 6,754, butprotocol.tsregrew 190 lines in 5 days.1. Order (one at a time; the next opens only after the previous merges):
registry.tsaction-execution.tsmcp-http-tools.tsmetadata-manager.tsstack.zod.ts, which is a published contract: bring it back for its own approval before starting.Each split is generated by script against fresh main right before it is queued. The original file stays as a forwarding entry, so public exports are unchanged. A split waits for any open PR touching that file to merge first. Add
approval-service.ts(10,697 lines) to the next round.2. Line ceiling: yes, narrow form only.
Grade. p3 → p2. The splits cut merge-queue conflicts and per-seat token cost, both live constraints this week. Each split PR is large and keeps its own maintainer approval, as the hot-file ruling set.