perf(observability): opt-in DAP trace + proxy logger honors effective log level

[debugmcpdev]

Fixes #403

Two always-on observability defaults in the proxy worker were heavyweight for every session (evidence in the issue: a 658 MB dev logs/ directory):

1. Per-frame DAP trace is now opt-in

The default trace-file factory set DAP_TRACE_FILE for every session, and MinimalDapClient then appendFileSync'd every frame in both directions — synchronous I/O on the proxy's event loop in the hot path of every step/variables/stackTrace exchange, into an uncapped ndjson file.

Now:

• Default off. DAP_TRACE=1 (or true) enables the standard per-session dap-trace-<sessionId>.ndjson; an explicit DAP_TRACE_FILE (inherited via the spawn env) is honored as-is, without renaming.
• 50 MB cap when enabled (consistent with the main logger's maxsize): one truncation marker line, then silence for the client's lifetime. Cap injectable for tests (traceMaxBytes).
• The hooks.createTraceFile test seam is unchanged.
• Sync writes retained deliberately (issue proposed a buffered async queue): tracing is now an opt-in crash-triage tool, and a write queue loses the final frames exactly when the process dies — the moment you need them. Happy to split this out if the sync-write latency matters to someone who has tracing on.

2. Proxy logger honors the effective log level

proxy-<sessionId>.log was hardcoded to 'debug', ignoring --log-level and DEBUG_MCP_LOG_LEVEL. The effective level now rides the init payload:

SessionManager (reads the winston logger's .level, which already resolves CLI flag → env → info) → ProxyConfig.logLevel → ProxyInitPayload.logLevel → ILoggerFactory(sessionId, logDir, level). Legacy parents that send no level keep the historical debug default, so old payloads behave identically.

Sibling noted while here (not fixed): adapter-registry.ts:397 also hardcodes logLevel: 'debug' when building per-adapter dependencies for dynamically loaded adapters — same bug class, no plumbing available there yet.

Deferred to #399's startup-janitor refactor

Sweeping stale per-session run dirs (proxy-*.log / dap-trace-*.ndjson): session logs live under os.tmpdir()/debug-mcp-server/sessions/<id>/run-<ts>/, out of reach of the flat logger.ts sweeper — a session-dir sweep fits naturally next to the orphan reapers being reworked in #399.

Docs

CLAUDE.md debugging scenarios + docs/development/setup-guide.md env table document DAP_TRACE / DAP_TRACE_FILE.

Tests (TDD, all watched fail first)

• Worker: default factory off without DAP_TRACE, on with DAP_TRACE=1, explicit DAP_TRACE_FILE honored unrenamed; logLevel passed to the logger factory.
• ProxyManager: logLevel included in the init command.
• SessionManager: effective logger level lands in the proxy config (startCalls[0].logLevel).
• Dependencies: loggerFactory passes the level to createLogger; legacy debug default without one.
• MinimalDapClient: byte cap writes one truncation marker then stops.
• Full npm test green (260 files / 3959 tests), npm run lint clean.

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!