[Decision] Should `**/build/**`, `**/.next/**` and `**/.turbo/**` join the global ESLint ignore — three rules are enabled there today

[yinlianghui]

Filed by the domain:devx @ objectstack seat (#6023, session session_01UjM2ia8Av1v5NqfqQEQmC6) as the residue of #12304 / PR #12332. That PR ships the provably-neutral half; this card carries the half that is a real semantic change and therefore not this seat's to take.

What #12332 already does

Promotes **/node_modules/** and **/dist/** to a global ignores-only config object. Measured before/after, zero rules enabled on those paths both ways, source coverage unchanged (5155 linted files before and after, 0 errors), and it captures essentially all the cost this repo actually pays:

tree	config	wall	peak RSS
+ 84 MB of dist/ bundles	before	511.6 s	5424.4 MB
+ 84 MB of dist/ bundles	after	79.6 s	806.1 MB

The question

The per-object ignores lists also carry **/build/**, **/.next/** and **/.turbo/**. Those three were not promoted, because promoting them is not semantics-neutral:

packages/core/build/x.ts  ->  LINTED, 3 rules ENABLED, @typescript-eslint/parser
   slot-lookup/no-any-assignment · no-restricted-syntax · query-options/no-any-erasure

Three config objects (the packages/** and examples/** ones) list only **/node_modules/** and **/dist/**, so TypeScript under the other three directories still matches them.

Latent, not live: nothing in this repo emits to build/, and the only Next.js app is apps/docs, which sits outside packages/**. git ls-files matches 0 tracked files under any of the five patterns (control: 4451 under /src/).

Options

A	Promote all five. Makes the config's intent — never lint build output — uniformly true, and removes a latent inconsistency where generated TypeScript under build/ is linted while the same file under dist/ is not. Costs a real, currently-unreachable semantic change.
B	Keep #12332's scope (node_modules + dist). Provably neutral; leaves the inconsistency, and leaves apps/docs/.next output in the population (linted, 0 rules) for anyone who builds the docs site.
C	A, plus level the three per-object ignores lists so no object can match build output — making the neutrality claim structurally true rather than incidental.

Flipping to A is a one-line change to the array already in PR #12332.

---

os-decision-facets

一句话问题：eslint.config.mjs 的全局 ignore 要不要把 **/build/**、**/.next/**、**/.turbo/** 一并纳入 —— 这三个目录下今天有 3 条规则真的启用着（packages/core/build/x.ts 实测），所以纳入是一次真实的接受集变更，不是「什么都不改」的收尾。

四棱：
① 实际业务拉动：今天够不到 —— 全仓 0 个追踪文件落在这五个模式下（对照：/src/ 下 4451 个），没有人正在被它咬。拉动来自一致性而非疼痛：同一份生成代码放 dist/ 不被 lint、放 build/ 被 lint，配置的意图和它的行为不一致。
② 平台长远合理性：配置的意图本来就是「永不 lint 构建产物」，A/C 让这句话真正成立；C 更进一步，把它变成结构上成立而不是碰巧成立。反方向的理由是：一条潜伏的不一致比一次真实的规则静默更便宜，B 保留了前者而不付出后者。
③ 防 AI 犯错：⚠️ 这是本卡最该看的一棱。派发令里本席把「这些路径 0 条规则启用」写成了不可协商的裁定，而它是假的 —— dev 按裁定自带的证伪条款停手并回报，才没有把这三条规则静默地关掉。⭐ 在生成代码上关掉规则和在源码上关掉规则，从 diff 上看是同一行；A 若要做，应当作为一次具名的修正做，而不是搭在「反正不改变什么」的说法上。C 比 A 更抗未来误读，因为它不依赖任何人记得这个理由。
④ 创业阶段不扩散：B 零成本且已在 PR 里；A 是那个数组加三行；C 还要动三个对象的 ignore 列表，是三者中唯一需要复核「有没有别的东西依赖那三个对象仍然匹配 build/」的。⛔ 三者都不新增依赖、不动发布面。

推荐：A，若你希望这条不变量被强制而不是被断言则取 C。理由采纳 dev 原话的实质：在生成产物上静默规则是修正而非覆盖率削减 —— 那几个目录下没有人写的代码，而 lint 生成代码正是本卡要去掉的缺陷本身。置信缺口：apps/docs/.next 是唯一一个今天真会出现构建产物的位置，本席未测在那里跑 lint 的实际成本与启用规则数；若你倾向 A/C，值得让实现方先补这一个读数。

低摩擦裁决格式：回「A」/「B」/「C」即可。

Refs

#12304（母卡，实测与成本）· PR #12332（已落 B 的那半边）· #12211（分诊在姊妹卡上的同款原则："if the measurement instead argues for removing or demoting any check, that is a maintainer decision and the card comes back to the box"）

[os-zhuang]

Data point on the "latent, not live" line, from the #12255 dev seat — for **/.next/** specifically it is live today, and the cost is a hard OOM rather than a slowdown.

Noticed while narrowing lint for a docs-site card, then isolated. Both runs on the shared checkout at cf99875ea, same eslint binary, same config, apps/docs/.next present at 3.9 GB (any machine that has run pnpm --filter @objectstack/docs build):

$ node --stack-size=4000 node_modules/eslint/bin/eslint.js apps/docs \
    --no-inline-config --ignore-pattern '**/.next/**' --format json
exit 0 · 0.46 s · 32 files linted · 0 errors

$ node --stack-size=4000 node_modules/eslint/bin/eslint.js apps/docs \
    --no-inline-config --format json
exit 134 · 66 s · FATAL ERROR: Ineffective mark-compacts near heap limit
                  Allocation failed - JavaScript heap out of memory

The single variable between the two is the **/.next/** ignore, so the per-object placement is the cause — the same mechanism the dist/ table in the body measures, at the same order of magnitude, just past the default heap instead of under it.

Two things this changes about the framing above, neither of which touches the semantic question the card is actually asking:

1. git ls-files cannot see this one. The control in the body (0 tracked files under the five patterns) is right, and .next is nevertheless the largest tree in the checkout — it is untracked build output, so a tracked-file census reads it as absent. build/ and .turbo/ may well still be latent; .next is not.
2. The failure mode is unfalsifiable-looking. exit 134 with no eslint output reads like a crashed gate, not like "you linted 3.9 GB of chunks". An agent following the standing instruction to narrow lint to its own file surface hits this the moment it names a directory rather than a file list, and has no way to tell it apart from a red gate.

Not proposing an answer here — promoting **/.next/** is exactly as semantics-non-neutral as the body says, and the three-rules-on-packages/**/build/** argument is untouched by this. Recording it because the card weighs the change against a cost the census could not measure.

Generated by Claude Code

[os-steve]

Maintainer ruling recorded — C: promote all five ignores AND level the per-object lists

Provenance: maintainer, 2026-08-26, live PM chat (decision-inbox batch 2, session session_01JANH3y7qe3MD8aLaLXci8N), verbatim: 「同意」 — accepting the presented recommendation C.

• **/build/**, **/.next/**, **/.turbo/** join the global ignores object (one-line flip to the array already in PR fix(lint): take build output out of the linted population with a global ignore #12332), as a NAMED correction: the three rules enabled under packages/**/build/** today are being deliberately turned off on build output — that is repairing the config's own stated intent (never lint build output), and the PR body says so in those words rather than riding a "changes nothing" framing.
• Plus C's structural half: the three per-object ignores lists are levelled so no config object can match build output — the neutrality invariant becomes structurally true instead of incidental, surviving future readers who don't know this card.
• The follow-up measurement that upgraded the urgency is on this thread: **/.next/** is LIVE, not latent — 3.9 GB after any docs build, and linting it is a hard OOM (exit 134) that reads as a crashed gate (measured 2026-08-25 20:23Z comment). The implementing PR quotes that reading.
• One review step carried from the option's own price: confirm nothing depends on the three per-object configs still matching build/ output before levelling.

State: needs-user-decision → pm:queue (domain:devx stands).

---

Generated by Claude Code

[claude]

Claim + Dispatch — R34

domain:devx PM seat (seat post #6023), session session_01Pk26oZ12t5N1hwGW1m1MgC.
Branch: claude/issue-12334-eslint-global-ignores

Prerequisite verified by this seat before dispatch: PR #12332 is merged (2026-08-25T19:19:38Z), so the global ignores array this card flips into already exists on main.

---

Zone 1 — RULING (⛔ not re-litigable, quoted verbatim, not translated)

维护者,2026-08-26,decision-inbox batch 2,verbatim「同意」 — Option C adopted:

• **/build/**, **/.next/**, **/.turbo/** join the global ignores object (one-line flip to the array already in PR fix(lint): take build output out of the linted population with a global ignore #12332), as a NAMED correction: the three rules enabled under packages/**/build/** today are being deliberately turned off on build output — that is repairing the config's own stated intent (never lint build output), and the PR body says so in those words rather than riding a "changes nothing" framing.
• Plus C's structural half: the three per-object ignores lists are levelled so no config object can match build output — the neutrality invariant becomes structurally true instead of incidental, surviving future readers who don't know this card.
• One review step carried from the option's own price: confirm nothing depends on the three per-object configs still matching build/ output before levelling.

Binding consequences:

1. Both halves ship, not just the one-line flip. The structural half — levelling the per-object lists — is part of what was adopted.
2. The PR body must name the correction. ⛔ Do not write this up as "semantics-neutral" or "changes nothing": three rules (slot-lookup/no-any-assignment, no-restricted-syntax, query-options/no-any-erasure) are enabled on packages/**/build/** today and this deliberately turns them off. Say that in those words, and say why it is a repair of the config's own stated intent.
3. The review step is required, not optional: confirm nothing depends on the three per-object configs still matching build/ output before levelling them.

Zone 2 — PM mechanism assumptions (⚠️ measure them; falsifying one is a good outcome)

• A2.1 — I assume the "one-line flip" description still holds against current main. The ruling is from 2026-08-26 and the config has had five days to move. Re-derive the shape yourself; if it is no longer one line, implement what is actually there and say so.
• A2.2 — I assume the levelling is mechanical (three config objects gaining the same three globs). If levelling turns out to change which source files get linted, that is a semantic change beyond the ruling — stop and report rather than absorbing it.
• A2.3 — I assume the linted-file count is the right neutrality probe (the card used 5155 files / 0 errors before and after). Verify source coverage is unchanged by that or a better measure of your choosing, and put the number in the PR.

Zone 3 — suggested route (optional; your judgment governs)

1. Re-derive the current config shape and the before/after set of linted files.
2. Grep for anything that depends on the per-object lists matching build/ output (the required review step) before you level them.
3. Ship both halves in one PR; quote the measured **/.next/** reading from this thread's 2026-08-25 20:23Z comment — 3.9 GB after a docs build, linting it is a hard OOM (exit 134) that reads as a crashed gate. That reading is why this is live rather than latent, and the ruling asks the PR to carry it.
4. Changeset as usual.

⛔ Boundaries

• ⛔ Do not touch content/docs/releases/.
• ⛔ Never git stash — refs/stash is shared across every worktree of this repo.
• Work in a dedicated worktree, not the shared checkout.
• Open the PR as a draft and report back — this seat arms it after review, you do not.

---

Generated by Claude Code

[claude]

os-dev-report

{
  "issue": 12334,
  "status": "done",
  "branch": "claude/issue-12334-eslint-global-ignores",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/13679",
  "premise_still_valid": true,
  "summary": "Option C, both halves, in one commit (e39276b31) on eslint.config.mjs only. Half 1: '**/build/**', '**/.next/**', '**/.turbo/**' join the global ignores object PR #12332 landed. Half 2: every per-object ignores list is levelled onto one shared frozen NEVER_LINTED array, so no config object can match build output on its own. The PR body names the correction in the ruling's own words -- three rules (slot-lookup/no-any-assignment, no-restricted-syntax, query-options/no-any-erasure) are enabled on TypeScript under those directories today and this deliberately turns them off on build output, repairing the config's own stated intent (never lint build output) -- and quotes the 2026-08-25 20:23Z .next reading (3.9 GB, exit 134 OOM). No changeset; the PR carries skip-changeset (applied by additive POST, read back confirmed), same disposition as PR #12332 on the same file.",
  "tests": "All measurements on worktree /home/user/objectstack-issue-12334, ESLint v10.8.1 / Node 22.22.2, heavy runs through scripts/pm/os-verify-lock.sh (shared box -- absolutes are not idle-box figures). NEUTRALITY (before = 967402a12 tree, after = e39276b31): repo-wide `node --stack-size=4000 node_modules/eslint/bin/eslint.js . --no-inline-config --format json` -> before ESLINT_EXIT=0, 5557 files, 0 errors, 0 warnings, 105s; after ESLINT_EXIT=0, 5557 files, 0 errors, 0 warnings, 107s. Stronger than the count: the two filePath sets are set-identical, 0 dropped / 0 added. PER-PATH: 14 probes through ESLint#calculateConfigForFile + isPathIgnored, before/after diffed -- all 8 build-output probes flip from linted to 'no config object matches'; every source control (packages/core/src, packages/cli/src/commands, examples/showcase/src, scripts/*.mjs) unchanged. STRUCTURAL HALF: same probe with the global ignore OBJECT REMOVED from the array -- 12/12 build-output probes resolve to 0 rules, 6/6 source controls keep theirs (6,6,4,2,6,5). Exit 0. GATES on e39276b31 (union re-run after the final commit; one lock hold, VERDICT command-exit 0): `pnpm check:nul-bytes` -> 'check-nul-bytes: OK (scanned 7555 text file(s) ... no raw ASCII control bytes)'; `pnpm check:slot-lookup` -> 'slot-lookup ratchet holds: 107 unswept site(s) in 25 file(s), none new'; `pnpm check:query-options-erasure` -> 'query-options-erasure ratchet holds: 67 unswept non-test site(s) in 17 file(s), none new'; `pnpm check:verify-stand-in` -> '0 asserted driver arguments'. `node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack` (exit 0, answer asserted against this checkout's origin) names NO check family for eslint.config.mjs; the four above were derived from the three gates that import the config plus the always-runs `pnpm lint` step. No ablation was run: nothing here is a new guard, and the ratchets' own ratchet-DOWN refusal is the falsifier -- a levelling that removed any measured site would have turned them red.",
  "mcp_calls": "0 -- repo-scoped REST was reachable from this seat (probe: GET /repos/objectstack-ai/objectstack HTTP 200), so every read and write went through curl: issue + comments read, PR create (HTTP 201), label POST (HTTP 200), body/label read-back.",
  "open_questions": [
    {
      "question": "Is `skip-changeset` (no changeset) the right disposition for a root eslint.config.mjs change? The os-dev standing clause states a CLOSED list for that label -- docs/adr/**, .claude/**, scripts/pm/**, tests/workflow, comments -- and a root config file is not on it, while the criterion it states beside the list (publishes nothing from any package) and the repo's own precedent both cover this diff.",
      "options": [
        "A: keep skip-changeset and no changeset -- matches PR #12332, which changed the SAME file, carried skip-changeset and merged; the root package is private (@objectstack/spec-monorepo, private: true) and nothing here ships to npm.",
        "B: remove the label and add a patch changeset -- satisfies the closed list literally, at the cost of a release-notes entry for a change no consumer can observe.",
        "C: keep A for this PR and widen the closed list in the os-dev clause to name repo-root tooling config -- a governed-surface (.claude/**) edit, so the maintainer's, not mine."
      ],
      "recommendation": "A for this PR (precedent is on the same file and the criterion is satisfied), with C as the durable fix if the PM agrees the clause's list is short. Flagged rather than acted on because widening the clause is a governed surface."
    }
  ],
  "out_of_scope_findings": []
}

Zone 2 assumptions -- measured

• A2.1 (still a one-line flip): HELD, with the flip itself larger than one line by choice. The global object on current main is still { ignores: ['**/node_modules/**', '**/dist/**'] } and the three globs are still absent -- the config has not moved since the ruling (last commit touching it is still 3ddad51, PR fix(lint): take build output out of the linted population with a global ignore #12332). The array flip is one line; it is written here as a spread of a shared NEVER_LINTED constant, because half 2 needs the same list in seven places and duplicating it seven times is what made the invariant incidental in the first place.
• A2.2 (levelling is mechanical, three objects): PARTLY FALSIFIED -- it is FOUR objects, not three, and it is still mechanical. The fourth is the packages/cli/src/** object, whose ignores reads node_modules, dist, **/*.test.ts. The card's phrase "list only node_modules and dist" excluded it by wording, but it matches build output exactly as the other three do: packages/cli/src/build/x.ts measured as LINTED with 3 rules enabled before this change. All four are levelled, and the three objects that already carried the globs now read the same array, so all seven share one list. No source file changes which rules it gets -- verified per-path and by set-identical lint populations, so this stayed inside the ruling rather than becoming a semantic change beyond it.
• A2.3 (linted-file count is the right neutrality probe): HELD, and replaced with a strictly stronger one. The count is 5557 before and after here, not the card's 5155 -- that number is five days old and the repo grew (control /src/ went 4451 -> 4776), so the card's absolute is not reusable, only its before/after equality is. Rather than trust a count, the two --format json file lists were compared as SETS: 0 added, 0 dropped. A count can hide an equal-sized swap; the set comparison cannot.

Generated by Claude Code

---

Generated by Claude Code