Skip to content

Dev-loop lint gate omits tools/dev-proxy, leaving runtime supervisor code unchecked #718

Description

@debugmcpdev

Problem

The canonical development gate runs pnpm lint, but that command only includes src/**/*.ts, packages/*/src/**/*.ts, and scripts/**/*.{js,mjs,cjs}. Production supervisor code under tools/dev-proxy/ is outside the gate, even though it starts and stops backend processes and handles MCP requests.

Found while fixing #716 and #717. This is already present on main at f8d55f4493ebfc4253475cf4fc4a2faf4b90a55d.

Reproduction

With the repository's pinned pnpm and installed dependencies:

pnpm lint
pnpm exec eslint tools/dev-proxy/dev-proxy.mjs

The first command passes. The second reports two preserve-caught-error errors in the existing BackendManager.rebuild() catches, at lines 355 and 364 on that revision. Any new lint defects added under tools/dev-proxy/ likewise go unnoticed by the normal command and pre-push/CI gate.

Expected

Include maintained runtime tooling such as tools/dev-proxy/**/*.{js,mjs,cjs} in the canonical lint command and resolve or explicitly document the pre-existing findings. Keep intentionally excluded experimental scripts separate from the production tooling selection.

Verified on Windows with Node 24.14.1, pnpm 10.33.0, and the checked-in ESLint configuration.

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions