objectui 的 eslint 没开 no-console:模块作用域遗留调试输出没有任何自动化拦网(#7139 靠人工发现)

[os-zhuang]

Migrated from objectstack-ai/objectstack#7146 under the file-at-destination ruling (objectstack-ai/objectstack#7167, maintainer 2026-08-10). Originally filed 2026-08-09T23:18:02Z. The full prior thread — including triage rulings and hold/restart conditions — remains on the source issue and MUST be read before acting on this card.

---

观察类(不影响当前用户:唯一已知实例已由 objectstack#7139 / objectui PR objectstack-ai/objectstack#4007 删除)。发现于 objectstack#7139 的实施过程。

事实

objectui 仓根 eslint.config.js 没有配置 no-console 规则(全仓 grep no-console 零命中)。因此 objectstack#7139 那句位于模块作用域、加载即打印的 console.log('Registering object-map...') 从落库到被发现,一路没有任何自动化环节报过它 —— pnpm lint 对它完全沉默,是靠人工阅读发现的。

修 objectstack-ai/objectstack#7139 时顺带核实过:packages/plugin-*/src/index.tsx 19 个文件里,这类会执行的遗留调试输出目前只有那一处(plugin-editor 的命中是 defaultProps.value 示例代码字符串)。也就是说现在仓库是干净的,这条单纯粹是「拦网缺失」,不是「有 bug 待修」。

为什么不在 objectstack-ai/objectstack#7139 的 PR 里顺手开

开 no-console 是影响多个包的策略决定,不是 XS 单能顺带夹带的改动,至少要先答三个问题:

1. 有意保留的诊断怎么豁免。 仓里存在大量刻意的 console.warn / console.error 运行时诊断,例如 packages/plugin-map/src/ObjectMap.tsx 三处(无效 map 配置、API provider 未实现、取 schema 失败),以及 packages/core/src/registry/Registry.ts 里 register() 按设计发的缺 namespace / 裸名 fallback 冲突告警。合理形态大概是 no-console: ['error', { allow: ['warn', 'error'] }],但这需要确认「debug 噪音走 log/info/debug、诊断走 warn/error」是否就是本仓想要的约定。
2. 是否该有 debug 通道。 plugin-map 在模块作用域 console.log('Registering object-map...'):每次加载该 plugin 都往控制台打一行 objectstack#7139 原文提过「或按需换成 debug 通道」。如果仓里应有统一的 debug 输出设施(packages/core/src/utils/debug-collector.ts 似乎已有相关设施,未细看),规则应该配合它一起定,而不是只堵不疏。
3. 落地成本与噪音量未测。 开启前需要跑一遍全仓看现存命中数,决定是 error 一次性清干净,还是先 warn 逐步收敛。示例代码、脚本(scripts/**)、测试文件通常要单独 override。

建议

由 PM 分诊决定要不要做、以什么范围做。若要做,建议独立 PR:先统计全仓命中,再定 allow 列表与 overrides,附一条针对「模块作用域 debug 输出」的说明。真正想守的不变量是「import 一个包不该往使用者控制台写噪音」—— PR objectstack-ai/objectstack#4007 已用 packages/plugin-map/src/index.registration.test.tsx 把这条钉在 plugin-map 上(spy log/info/debug 后 vi.resetModules() 再 import,断言零输出),那个测试形态可以直接复制到其他 plugin,是比 lint 规则更贴近意图的另一条路,两者不互斥。

相关:objectstack#7139(缺陷本体)、objectui PR objectstack-ai/objectstack#4007(修复 + 单包钉子)。

[yinlianghui]

Claiming — PM dispatch, with a delegated adjudication (veto window open). Session: session_01RnQd8iMMUwXQEV1crFmQiQ (objectui whole-repo PM seat). Branch: claude/issue-4029-no-console-rule.

Adjudicated (within delegation gates — a gate ADDITION on repo tooling, no contract surface): adopt the card's own suggested shape — no-console: ['error', { allow: ['warn', 'error'] }] at the repo root, with overrides exempting scripts/**, test files, and examples/** — under the card's stated invariant ("importing a package must not write noise to the consumer's console") and the measured house convention (deliberate diagnostics already use warn/error; the one known debug leak used log). Measure-first discipline: the dev counts full-repo hits before enabling; a small mechanical residue (≤ ~20 log/info/debug hits) is cleaned in the same PR, a larger one is reported as a fork instead of absorbed. The debug-channel question (card's Q2) is deliberately NOT bundled — the rule does not block a future channel, and 只堵不疏 is acceptable when the measured leak count is near zero. Maintainer may veto/adjust on this card; dispatch proceeds meanwhile.

Precondition carried to the dev: the migrated card requires reading the source thread (objectstack#7146) before acting — stop and report if it holds a contrary ruling.

PR will be Fixes #4029.

---

Generated by Claude Code

[yinlianghui]

<!-- os-dev-report -->

{
 "issue": 4029,
 "status": "needs_decision",
 "branch": "claude/issue-4029-no-console-rule",
 "pr": null,
 "pr_number": null,
 "pr_url": null,
 "head_sha": null,
 "changed_files": [],
 "premise_still_valid": true,
 "summary": "Confirmed the issue's core claim (root eslint.config.js has zero no-console configuration; grep hits: 0) and re-read the full objectstack#7146 source thread end to end -- it was promoted finding-to-pm:queue then migrated to this card under the file-at-destination ruling, with no hold/restart condition and no contrary ruling. Implemented the delegated shape (no-console: ['error', {allow: ['warn','error']}] plus overrides for root scripts/**, examples/**, and test files) in a worktree solely to run the mandated pre-change census. That literal exemption list leaves 235 real violations once the rule actually runs as 'error' -- far past the ~20-hit ceiling the delegated ruling set for absorbing cleanup into this PR -- so per the ruling's own instruction (more hits = stop and report the fork) I did not land the change. eslint.config.js was reverted with git checkout and the worktree was torn down; nothing is committed or pushed.",
 "tests": "Both runs executed under the shared lock: flock -E 99 -w 300..540 /tmp/os-heavy-verify.lock -c '...'. (1) Upper-bound sanity check: NODE_OPTIONS=--max-old-space-size=4096 pnpm exec eslint . --rule '{\"no-console\":[\"error\",{\"allow\":[\"warn\",\"error\"]}]}' --format json -- 423 raw hits, but this CLI-override run lints beyond eslint.config.js's own **/*.{ts,tsx} file selection (it also caught .mjs files such as root lazy-test.mjs and per-package plugin-gantt/scripts/*.mjs that the real config never lints), so it is superseded by (2). (2) After literally implementing the delegated eslint.config.js shape (no-console rule in the main ts/tsx block + a new override block turning it off for scripts/**, examples/**, **/*.test.{ts,tsx}, **/__tests__/**) and running plain `pnpm exec eslint . --format json`: 235 real violations remain -- see hit_census. Mechanism assumptions from the dispatch prompt were both confirmed: (1) 0 no-console hits in eslint.config.js before this work (grep); (2) packages/plugin-map/src/ObjectMap.tsx's 3 warn/error diagnostic sites and packages/core/src/registry/Registry.ts's register() warning show 0 hits against the no-console rule in both census runs, confirming allow:['warn','error'] correctly passes the house convention. `pnpm lint` was never run to green because the rule cannot go green under the literally-delegated scope without either breaking legitimate CLI/logger-infrastructure code or downgrading to 'warn' -- and this repo's .github/workflows/lint.yml deliberately never sets --max-warnings (documented reason: warning counts already run into the thousands), so a 'warn'-level no-console would provide zero real CI enforcement, which defeats the issue's stated purpose.",
 "hit_census": {
 "before_rule_existed": "0 (grep no-console in eslint.config.js, matches mechanism assumption #1)",
 "raw_repo_wide_no_overrides_upper_bound": 423,
 "raw_upper_bound_caveat": "measured via the --rule CLI flag, which is not scoped by eslint.config.js's files:['**/*.{ts,tsx}'] matcher and picked up .mjs files the real config never lints -- sanity-check only",
 "after_literal_delegated_overrides_root_scripts_examples_tests": 235,
 "breakdown": {
 "cli_family_packages_packages_cli_and_create_plugin_src": 193,
 "cli_family_pct_of_total": "82%",
 "cli_family_note": "packages/cli's src/index.ts re-exports serve/init 'for programmatic use', so it is not purely a standalone bin -- it has a real library-import surface too",
 "per_package_examples_dirs_not_reached_by_root_anchored_examples_glob": 18,
 "per_package_examples_example": "packages/types/examples/*.ts (18 of the 18)",
 "everything_else": 24,
 "everything_else_by_file": {
 "apps/site/app/components/ObjectUIProvider.tsx": 1,
 "packages/app-shell/src/views/ObjectDataPage.tsx": 1,
 "packages/core/src/utils/debug.ts": 3,
 "packages/data-objectstack/src/index.ts": 4,
 "packages/fields/src/widgets/MasterDetailField.tsx": 1,
 "packages/plugin-detail/src/DetailView.tsx": 2,
 "packages/plugin-gantt/demo/main.tsx": 2,
 "packages/runner/src/App.tsx": 2,
 "packages/runner/src/LayoutRenderer.tsx": 1,
 "packages/runner/src/lib/mockDataSource.ts": 3,
 "packages/sdui-parser/scripts/gen-manifest.ts": 1,
 "packages/sdui-parser/verify.ts": 2,
 "packages/vscode-extension/src/extension.ts": 1
 },
 "everything_else_notable": "packages/core/src/utils/debug.ts (debugLog/debugTime/debugTimeEnd, gated behind globalThis.OBJECTUI_DEBUG) and packages/data-objectstack/src/index.ts's createQuietHttpLogger (a Logger-interface implementation whose methods deliberately wrap console.debug/info/warn/error/log) are the repo's actual debug-channel infrastructure -- exactly the surface the card's own Q2 said not to bundle, yet the blanket rule as literally specified flags them without a new carve-out. packages/app-shell/src/views/ObjectDataPage.tsx:142 uses console.debug for a genuine diagnostic (explains why a URL filter was dropped) -- a candidate to promote to console.warn rather than delete, since 'debug' is not in the allow list."
 }
 },
 "gates": "not run -- no config change was committed and no PR was opened, so there is no HEAD to gate. The census commands above are the verification performed; see `tests`.",
 "changesets": "none -- no code landed, so no changeset is needed at this checkpoint.",
 "notes": "No positive-control add-a-console.log-then-revert check was run: since nothing is being landed, there is no green baseline to prove was flipped red by a real mutation. The mechanism was validated instead by the fact that the census's 235 hits are real, named files/lines the rule is correctly catching, and by the plugin-map/Registry 0-hit confirmation above -- the rule construct itself (no-console + allow:['warn','error']) works exactly as intended; the open question is purely about exemption boundaries, not mechanism.",
 "open_questions": [
 {
 "question": "The delegated exemption list (root scripts/**, examples/**, test files) leaves 235 no-console violations once the rule actually runs as 'error' -- 193 of them (82%) in packages/cli and packages/create-plugin (CLI tools whose job is terminal stdout; packages/cli also re-exports serve/init for programmatic import, so it has a real library surface too), 18 in per-package examples/ dirs the root-anchored glob does not reach, and 24 more including two files (packages/core/src/utils/debug.ts, packages/data-objectstack/src/index.ts's createQuietHttpLogger) that are deliberately-designed debug/logger infrastructure whose entire job is calling console.* -- exactly the debug-channel surface the card's own Q2 said not to bundle, yet the blanket rule as specified breaks it without a new carve-out. This is the more-than-~20-hit fork the delegated ruling told the dev to stop and report instead of absorbing. How should scope be resolved?",
 "options": [
 "A. Extend the override list with three additive, invariant-preserving carve-outs -- packages/cli/src/** + packages/create-plugin/src/** (CLI stdout is not 'a package a consumer imports and gets noise from'), examples/** widened to any depth (**/examples/**) so per-package example dirs match the same treatment root examples/** already gets, and named eslint-disable-line comments on the debug.ts / createQuietHttpLogger console.* calls (they ARE the debug/logger channel, not leaked debris) -- then clean the remaining ~22 genuine-residue sites in this PR (delete stubs like MasterDetailField.tsx:46, or promote diagnostics like ObjectDataPage.tsx:142's console.debug to console.warn to match the house convention) and land no-console as 'error'.",
 "B. Land only the literally-delegated override list and accept the rule cannot go green as 'error' without either (B1) breaking CLI/logger-infra code that has nothing to do with the #7139 bug class, or (B2) downgrading to 'warn' repo-wide -- but this repo's lint.yml deliberately never fails CI on warnings (no --max-warnings; documented reason: warning counts already run into the thousands), so 'warn' ships zero real enforcement and does not close the gap #4029 exists to close.",
 "C. Invert the rule to an explicit allow-list of guarded packages (files: ['packages/{core,components,fields,...}/src/**']) instead of a root rule with excludes -- the most conservative boundary, but needs maintainer sign-off on the package list up front and silently under-covers any new package added later until someone remembers to add it to the list."
 ],
 "recommendation": "A, because it is the only option that both (1) actually gates CI as 'error' -- real business need: the issue exists because #7139 had zero automated net, and B's 'warn' path measurably provides none either given this repo's no-max-warnings policy -- and (2) does not fight legitimate, already-reviewed code (CLI stdout, a Logger-interface implementation, an opt-in debug utility gated behind a global flag) to get there. It stays long-term sound by mirroring the override pattern this exact file already uses elsewhere (the test-file override block for object-ui/no-dynamic-import-in-test-hook) rather than introducing an allow-list maintenance burden (C) that silently under-covers new packages. For making AI-authored code hard to get wrong, it keeps the rule's blocked surface precisely aligned with the stated invariant (importing a package must not write console noise) instead of either overshooting into CI-breaking false positives on legitimate infrastructure or undershooting into silent no-op warnings."
 }
 ],
 "out_of_scope_findings": []
}

Generated by Claude Code

---

Generated by Claude Code

[yinlianghui]

os-dev-report

(Corrected marker: the previous comment on this issue opened with an HTML-entity-escaped <!-- os-dev-report --> instead of the literal marker, so it may not match an automated sweep. This comment carries the authoritative report; the JSON content is identical.)

{
 "issue": 4029,
 "status": "needs_decision",
 "branch": "claude/issue-4029-no-console-rule",
 "pr": null,
 "pr_number": null,
 "pr_url": null,
 "head_sha": null,
 "changed_files": [],
 "premise_still_valid": true,
 "summary": "Confirmed the issue's core claim (root eslint.config.js has zero no-console configuration; grep hits: 0) and re-read the full objectstack#7146 source thread end to end -- it was promoted finding-to-pm:queue then migrated to this card under the file-at-destination ruling, with no hold/restart condition and no contrary ruling. Implemented the delegated shape (no-console: ['error', {allow: ['warn','error']}] plus overrides for root scripts/**, examples/**, and test files) in a worktree solely to run the mandated pre-change census. That literal exemption list leaves 235 real violations once the rule actually runs as 'error' -- far past the ~20-hit ceiling the delegated ruling set for absorbing cleanup into this PR -- so per the ruling's own instruction (more hits = stop and report the fork) I did not land the change. eslint.config.js was reverted with git checkout and the worktree was torn down; nothing is committed or pushed.",
 "tests": "Both runs executed under the shared lock: flock -E 99 -w 300..540 /tmp/os-heavy-verify.lock -c '...'. (1) Upper-bound sanity check: NODE_OPTIONS=--max-old-space-size=4096 pnpm exec eslint . --rule '{\"no-console\":[\"error\",{\"allow\":[\"warn\",\"error\"]}]}' --format json -- 423 raw hits, but this CLI-override run lints beyond eslint.config.js's own **/*.{ts,tsx} file selection (it also caught .mjs files such as root lazy-test.mjs and per-package plugin-gantt/scripts/*.mjs that the real config never lints), so it is superseded by (2). (2) After literally implementing the delegated eslint.config.js shape (no-console rule in the main ts/tsx block + a new override block turning it off for scripts/**, examples/**, **/*.test.{ts,tsx}, **/__tests__/**) and running plain `pnpm exec eslint . --format json`: 235 real violations remain -- see hit_census. Mechanism assumptions from the dispatch prompt were both confirmed: (1) 0 no-console hits in eslint.config.js before this work (grep); (2) packages/plugin-map/src/ObjectMap.tsx's 3 warn/error diagnostic sites and packages/core/src/registry/Registry.ts's register() warning show 0 hits against the no-console rule in both census runs, confirming allow:['warn','error'] correctly passes the house convention. `pnpm lint` was never run to green because the rule cannot go green under the literally-delegated scope without either breaking legitimate CLI/logger-infrastructure code or downgrading to 'warn' -- and this repo's .github/workflows/lint.yml deliberately never sets --max-warnings (documented reason: warning counts already run into the thousands), so a 'warn'-level no-console would provide zero real CI enforcement, which defeats the issue's stated purpose.",
 "hit_census": {
 "before_rule_existed": "0 (grep no-console in eslint.config.js, matches mechanism assumption #1)",
 "raw_repo_wide_no_overrides_upper_bound": 423,
 "raw_upper_bound_caveat": "measured via the --rule CLI flag, which is not scoped by eslint.config.js's files:['**/*.{ts,tsx}'] matcher and picked up .mjs files the real config never lints -- sanity-check only",
 "after_literal_delegated_overrides_root_scripts_examples_tests": 235,
 "breakdown": {
 "cli_family_packages_packages_cli_and_create_plugin_src": 193,
 "cli_family_pct_of_total": "82%",
 "cli_family_note": "packages/cli's src/index.ts re-exports serve/init 'for programmatic use', so it is not purely a standalone bin -- it has a real library-import surface too",
 "per_package_examples_dirs_not_reached_by_root_anchored_examples_glob": 18,
 "per_package_examples_example": "packages/types/examples/*.ts (18 of the 18)",
 "everything_else": 24,
 "everything_else_by_file": {
 "apps/site/app/components/ObjectUIProvider.tsx": 1,
 "packages/app-shell/src/views/ObjectDataPage.tsx": 1,
 "packages/core/src/utils/debug.ts": 3,
 "packages/data-objectstack/src/index.ts": 4,
 "packages/fields/src/widgets/MasterDetailField.tsx": 1,
 "packages/plugin-detail/src/DetailView.tsx": 2,
 "packages/plugin-gantt/demo/main.tsx": 2,
 "packages/runner/src/App.tsx": 2,
 "packages/runner/src/LayoutRenderer.tsx": 1,
 "packages/runner/src/lib/mockDataSource.ts": 3,
 "packages/sdui-parser/scripts/gen-manifest.ts": 1,
 "packages/sdui-parser/verify.ts": 2,
 "packages/vscode-extension/src/extension.ts": 1
 },
 "everything_else_notable": "packages/core/src/utils/debug.ts (debugLog/debugTime/debugTimeEnd, gated behind globalThis.OBJECTUI_DEBUG) and packages/data-objectstack/src/index.ts's createQuietHttpLogger (a Logger-interface implementation whose methods deliberately wrap console.debug/info/warn/error/log) are the repo's actual debug-channel infrastructure -- exactly the surface the card's own Q2 said not to bundle, yet the blanket rule as literally specified flags them without a new carve-out. packages/app-shell/src/views/ObjectDataPage.tsx:142 uses console.debug for a genuine diagnostic (explains why a URL filter was dropped) -- a candidate to promote to console.warn rather than delete, since 'debug' is not in the allow list."
 }
 },
 "gates": "not run -- no config change was committed and no PR was opened, so there is no HEAD to gate. The census commands above are the verification performed; see `tests`.",
 "changesets": "none -- no code landed, so no changeset is needed at this checkpoint.",
 "notes": "No positive-control add-a-console.log-then-revert check was run: since nothing is being landed, there is no green baseline to prove was flipped red by a real mutation. The mechanism was validated instead by the fact that the census's 235 hits are real, named files/lines the rule is correctly catching, and by the plugin-map/Registry 0-hit confirmation above -- the rule construct itself (no-console + allow:['warn','error']) works exactly as intended; the open question is purely about exemption boundaries, not mechanism.",
 "open_questions": [
 {
 "question": "The delegated exemption list (root scripts/**, examples/**, test files) leaves 235 no-console violations once the rule actually runs as 'error' -- 193 of them (82%) in packages/cli and packages/create-plugin (CLI tools whose job is terminal stdout; packages/cli also re-exports serve/init for programmatic import, so it has a real library surface too), 18 in per-package examples/ dirs the root-anchored glob does not reach, and 24 more including two files (packages/core/src/utils/debug.ts, packages/data-objectstack/src/index.ts's createQuietHttpLogger) that are deliberately-designed debug/logger infrastructure whose entire job is calling console.* -- exactly the debug-channel surface the card's own Q2 said not to bundle, yet the blanket rule as specified breaks it without a new carve-out. This is the more-than-~20-hit fork the delegated ruling told the dev to stop and report instead of absorbing. How should scope be resolved?",
 "options": [
 "A. Extend the override list with three additive, invariant-preserving carve-outs -- packages/cli/src/** + packages/create-plugin/src/** (CLI stdout is not 'a package a consumer imports and gets noise from'), examples/** widened to any depth (**/examples/**) so per-package example dirs match the same treatment root examples/** already gets, and named eslint-disable-line comments on the debug.ts / createQuietHttpLogger console.* calls (they ARE the debug/logger channel, not leaked debris) -- then clean the remaining ~22 genuine-residue sites in this PR (delete stubs like MasterDetailField.tsx:46, or promote diagnostics like ObjectDataPage.tsx:142's console.debug to console.warn to match the house convention) and land no-console as 'error'.",
 "B. Land only the literally-delegated override list and accept the rule cannot go green as 'error' without either (B1) breaking CLI/logger-infra code that has nothing to do with the #7139 bug class, or (B2) downgrading to 'warn' repo-wide -- but this repo's lint.yml deliberately never fails CI on warnings (no --max-warnings; documented reason: warning counts already run into the thousands), so 'warn' ships zero real enforcement and does not close the gap #4029 exists to close.",
 "C. Invert the rule to an explicit allow-list of guarded packages (files: ['packages/{core,components,fields,...}/src/**']) instead of a root rule with excludes -- the most conservative boundary, but needs maintainer sign-off on the package list up front and silently under-covers any new package added later until someone remembers to add it to the list."
 ],
 "recommendation": "A, because it is the only option that both (1) actually gates CI as 'error' -- real business need: the issue exists because #7139 had zero automated net, and B's 'warn' path measurably provides none either given this repo's no-max-warnings policy -- and (2) does not fight legitimate, already-reviewed code (CLI stdout, a Logger-interface implementation, an opt-in debug utility gated behind a global flag) to get there. It stays long-term sound by mirroring the override pattern this exact file already uses elsewhere (the test-file override block for object-ui/no-dynamic-import-in-test-hook) rather than introducing an allow-list maintenance burden (C) that silently under-covers new packages. For making AI-authored code hard to get wrong, it keeps the rule's blocked surface precisely aligned with the stated invariant (importing a package must not write console noise) instead of either overshooting into CI-breaking false positives on legitimate infrastructure or undershooting into silent no-op warnings."
 }
 ],
 "out_of_scope_findings": []
}

Generated by Claude Code

---

Generated by Claude Code

[yinlianghui]

Fork adjudication (supplementary delegated ruling, veto window stays open; PM session session_01RnQd8iMMUwXQEV1crFmQiQ).

The dev's census honored the dispatch's stop-and-report ceiling: 235 violations under the literal exemption list — 82% in packages/cli + packages/create-plugin (terminal stdout is their function), 18 in per-package examples/ dirs the root-anchored glob missed, and two deliberately-designed debug/logger infrastructure files. Ruling: Option A — extend the overrides additively (packages/cli/src/**, packages/create-plugin/src/**, depth-agnostic examples/**), line-level disables with reason comments on the two infra files, clean the ~22 genuine residue sites (each named, delete-vs-promote-to-diagnostic judged per site), and land the rule as error. B rejected (a warn-level rule this repo's CI never fails on is zero enforcement — a gate that cannot fire is not a gate); C rejected (a maintainer-maintained allow-list silently under-covers new packages and adds a standing human dependency). All carve-outs follow the card's own invariant: importing a package must not write noise — a CLI's stdout is its product, not noise. Dev resumed to implement.

---

Generated by Claude Code

[yinlianghui]

os-dev-report

{
 "issue": 4029,
 "status": "done",
 "branch": "claude/issue-4029-no-console-rule",
 "pr": "https://github.com/objectstack-ai/objectui/pull/4725",
 "pr_number": 4725,
 "pr_url": "https://github.com/objectstack-ai/objectui/pull/4725",
 "head_sha": "ab8d59d08",
 "changed_files": [
 "eslint.config.js",
 "apps/site/app/components/ObjectUIProvider.tsx",
 "packages/app-shell/src/views/ObjectDataPage.tsx",
 "packages/app-shell/src/views/ObjectDataPage.saveAsViewFilterFold.test.ts",
 "packages/core/src/utils/debug.ts",
 "packages/data-objectstack/src/index.ts",
 "packages/fields/src/widgets/MasterDetailField.tsx",
 "packages/plugin-detail/src/DetailView.tsx",
 "packages/plugin-gantt/demo/main.tsx",
 "packages/runner/src/App.tsx",
 "packages/runner/src/LayoutRenderer.tsx",
 "packages/runner/src/lib/mockDataSource.ts",
 "packages/sdui-parser/scripts/gen-manifest.ts",
 "packages/sdui-parser/verify.ts",
 "packages/vscode-extension/src/extension.ts",
 ".changeset/no-console-lint-rule.md",
 ".changeset/no-console-debug-infra-comments.md"
 ],
 "premise_still_valid": true,
 "summary": "Confirmed the issue's premise (root eslint.config.js had zero no-console configuration; source thread objectstack#7146 held no contrary ruling, only promote-to-queue then a clean migration). First pass measured 235 real hits under the originally-delegated exemption list -- far past the ~20-hit ceiling -- and was reported as needs_decision per the ruling's own stop condition. The PM's supplemental ruling adopted recommendation A: three additive carve-outs (packages/cli/src/**, packages/create-plugin/src/**, examples/** at any depth), line-level eslint-disable + comment on the two files that ARE the repo's deliberate debug/logger infrastructure (core/src/utils/debug.ts, data-objectstack's createQuietHttpLogger), and individual delete-vs-promote judgment on the remaining 17 real residue sites (2 promoted to warn/error where a real anomaly was diagnosed, 15 deleted as pure happy-path narration). Landed no-console as 'error' with full-repo pnpm lint green. One pinned test (ObjectDataPage.saveAsViewFilterFold.test.ts) asserted the pre-promotion console.debug call and was updated to assert console.warn.",
 "tests": "Full-repo eslint census run twice under the shared /tmp/os-heavy-verify.lock (both stages summarized in hit_census below). Post-implementation: `pnpm exec eslint .` -- 0 errors (10353 pre-existing, unrelated warnings), confirmed green AFTER the final commit at HEAD ab8d59d08 (git rev-parse --short HEAD). Positive control: temporary module-scope console.log added to packages/core/src/index.ts (not committed), confirmed `pnpm exec eslint packages/core/src/index.ts` goes red with the exact expected no-console message, then reverted (git diff empty afterward). Type-check green for all nine touched packages (app-shell, core, data-objectstack, fields, plugin-detail, plugin-gantt, runner, sdui-parser, object-ui/vscode-extension) via `pnpm --workspace-concurrency=2 --filter (package name) run type-check` for each. Vitest run in two passes: (1) app-shell+core+data-objectstack+fields -- 618 test files / 7628 tests, 1 initial failure (the pinned test asserting console.debug, fixed and re-verified green in pass 2); (2) plugin-detail+runner+the fixed test+packages/plugin-map/src/index.registration.test.tsx (the sibling 'import must not write console noise' pin from #4007/#7139) -- 86 test files / 806 tests, all green including 'registers its components without printing to the console'. node scripts/check-changeset-presence.mjs and node scripts/check-changeset-no-major.mjs both green. node scripts/check-control-bytes.mjs and node scripts/check-changeset-fixed.mjs also green (unaffected baseline checks).",
 "hit_census": {
 "stage_1_before_carve_outs": {
 "after_literally_delegated_overrides_root_scripts_examples_tests": 235,
 "breakdown": "193 (82%) in packages/cli + packages/create-plugin (CLI tools); 18 in per-package examples/ dirs; 24 more including 2 files that are the repo's real debug/logger infrastructure",
 "reported_as": "needs_decision, per the delegated ruling's own >~20-hit stop condition"
 },
 "stage_2_after_pm_supplemental_ruling": {
 "carve_out_1": "packages/cli/src/** + packages/create-plugin/src/** -- removes 193 hits",
 "carve_out_2": "examples/** widened to any depth (**/examples/**) -- removes 18 hits",
 "carve_out_3_line_level": "eslint-disable-next-line + comment on 7 sites across 2 files (core/src/utils/debug.ts x3, data-objectstack/src/index.ts's createQuietHttpLogger x4) -- documented as deliberate debug/logger infrastructure, not residue",
 "remaining_17_individually_judged": {
 "promoted_to_warn_or_error": 2,
 "deleted": 15
 },
 "final_no_console_hit_count": 0
 }
 },
 "gates": {
 "eslint_full_repo": "0 errors at HEAD ab8d59d08 (10353 pre-existing warnings, unrelated)",
 "changeset_presence": "green -- node scripts/check-changeset-presence.mjs",
 "changeset_no_major": "green -- node scripts/check-changeset-no-major.mjs",
 "changeset_fixed": "green (baseline, unaffected by this diff)",
 "control_bytes": "green -- node scripts/check-control-bytes.mjs (this repo's nul/control-byte gate; scripts/check-nul-bytes.mjs does not exist here)",
 "typecheck": "green for all 9 touched packages",
 "vitest": "green, 704 test files / 8434 tests across both passes (1 pinned test fixed mid-run, re-verified green)",
 "ci_at_report_time": "in_progress -- draft PR just opened, GitHub Actions checks not yet reported (only the Vercel preview-build status context has posted so far, 'success'/ignored-build-step); per protocol this report is delivered at draft-PR time without waiting for CI convergence"
 },
 "changesets": "2 files: .changeset/no-console-lint-rule.md (patch: @object-ui/app-shell, @object-ui/fields, @object-ui/plugin-detail, @object-ui/runner, object-ui) for the 5 published packages with a real console-output behavior change; .changeset/no-console-debug-infra-comments.md (empty frontmatter) for @object-ui/core and @object-ui/data-objectstack, comment-only zero-behavior-change edits. packages/plugin-gantt and @object-ui/sdui-parser carry no changeset -- every touched file in each sits outside that package's src/ (demo/main.tsx; scripts/gen-manifest.ts and root verify.ts), which is the guarded surface check-changeset-presence.mjs uses by design. objectui has no skip-changeset label convention (that clause is objectstack's mechanism per the dispatch prompt) so it was not applied.",
 "notes": "Two adjudication rounds on the claim comment thread, both quoted in full in the PR body: the original delegated ruling (measure-first, ≤~20-hit ceiling) and the supplemental ruling (adopt recommendation A) that authorized this implementation after the needs_decision report. Resource-discipline note: the first full test attempt (all 8 touched packages via a single vitest invocation) ran ~750 test files and took over 20 minutes under the shared lock, holding up two other queued agents (one nearly exhausted its 8-minute wait budget) -- that run's own output was also lost to a `| tail -200` pipe that only flushes at EOF, so its actual pass/fail summary was never seen even though it happened to exit 0. It was interrupted (SIGTERM on its recorded PID, though it turned out to have exited naturally moments earlier) and replaced with two properly-scoped batches, each writing directly to a log file (no tail pipe): batch 1 (app-shell/core/data-objectstack/fields, 618 files) surfaced the one real, expected failure -- the pinned test asserting the pre-promotion console.debug call -- which was fixed and re-verified green in batch 2 alongside plugin-detail, runner, and the plugin-map pin test (86 files). plugin-gantt and sdui-parser's test suites were deliberately not run: neither package's changed file (demo/main.tsx; scripts/gen-manifest.ts, verify.ts) is referenced by any test file (grepped to confirm), and both packages' type-check was already green.",
 "open_questions": [],
 "out_of_scope_findings": []
}

Generated by Claude Code

---

Generated by Claude Code