version: "1.0.1" name: code-diagnostics description: "Диагностика BSL и объяснение отключений диагностик в коде. Используй когда нужно запустить или разобрать диагностики, объяснить коды АПК, EDT, BSL LS, inline/range disable markers, suppression-комментарии или стандарт v8std за диагностикой."

Code Diagnostics

MCP routing

• Preferred path: use MCP unica tools unica.code.diagnostics, unica.code.graph, unica.code.definition, unica.code.outline, unica.code.search, unica.standards.explain, unica.standards.search, and unica.runtime.execute.
• Use unica.code.diagnostics with mode=analyze or no mode for the classic analyzer run; large workspaces may set timeoutSeconds from 30 to 3600. Without that argument the call uses operational.code_diagnostics.analyze_timeout_seconds from <workspaceRoot>/unica.local.toml, then unica.toml, then the compiled 120-second fallback. Use mode=status|catalog|file|workspace for typed diagnostic catalog and scoped diagnostic reads; those modes do not read this operational config and do not accept timeoutSeconds.
• mode=analyze always returns typed data assembled from the analyzer JSONL protocol; raw JSONL and console reports never appear in stdout. Omit format, or use the migration aliases format=json|jsonl; console, unknown formats and format on another mode are rejected before the analyzer starts.
• Analyze filters default to minSeverity=warning, detail=concise and limit=200 (1..=200). codes matches exact case-sensitive codes. Read files, diagnostics, itemsTotal, itemsReturned and truncated before treating items as exhaustive; file failures remain visible regardless of diagnostic filters.
• path belongs to mode=file only. Every other mode rejects it instead of scanning the whole source set, so name the file and the mode together.
• When the analyzer workspace model is still loading, mode=file|workspace fail with diagnostics_pending: and a retry hint rather than reporting an empty finding set. For mode=analyze, a stream containing only start is diagnostics_pending:, file events without done are diagnostics_incomplete:, and malformed events or inconsistent totals are diagnostics_invalid:. Only state=completed, complete=true and ok=true prove a finished analysis; treat every other state as not clean code. mode=status reports loading as a successful readiness answer.
• unica.code.definition returns index_pending: only while an RLM index is building and index_unavailable: for missing, stale, failed or unavailable indexes. Neither state means “no definitions”; only a ready typed result with definitions=[] is a successful empty answer.
• Read-only tools do not accept dryRun; preview and apply modes belong only to mutating tools.
• Use unica.code.graph only for diagnostic impact context: containing node, callers, callees, neighbors, or workspace graph status.
• v8std access goes only through public unica.standards.* tools.
• Do not call internal analyzer, standards, or package adapters directly. They are hidden behind MCP unica.

Workflow

1. Run unica.code.diagnostics for the selected source-set or module. Start with mode=status when the analyzer workspace model may still be loading, and use mode=catalog when diagnostic codes need classification.
2. Group diagnostics by file, diagnostic id/code, and root cause. Do not fix duplicate reports independently when one source issue explains them.
3. For one file or range, use unica.code.diagnostics with mode=file; then use unica.code.outline, unica.code.definition, or unica.code.search for exact context.
4. When diagnostic output includes a graph id or the fix may affect callers/callees, inspect impact with unica.code.graph before proposing a change.
5. Search nearby code with unica.code.search only when exact context tools do not identify the root cause.
6. For each diagnostic id/code, call unica.standards.explain with codes when the code is explicit; otherwise search unica.standards.search by diagnostic name, APK/EDT/BSL LS token, or nearby snippet.
7. Report fixes in cause-first order: source defect, impacted diagnostics, graph impact if relevant, standard reference, verification command.

Verification gate

• The verification gate is part of the delivery contract, not an optional final

polish step.

• Run diagnostics after syntax-sensitive edits and treat new error or critical

findings as blocking.

• Run impact analysis with unica.code.graph when an exported method, metadata

handler, public API, query path, or shared module contract changes.

• If public MCP unica cannot expose the required syntax, diagnostic, or impact

evidence, report that as a Unica MCP contract gap instead of claiming the change is fully verified.

Suppression and range-disable comments

When comments disable diagnostics over a line or range, treat the exact marker as evidence, not as decoration.

• Extract literal codes or ids from the comment: АПК, EDT, BSL LS, analyzer rule names, numeric or mnemonic ids.
• Use unica.standards.explain with all extracted codes. If v8std does not resolve a code, search with unica.standards.search using the code plus nearby diagnostic text.
• Explain why the отключение exists only when the code, surrounding range, and standard support the reason. If the reason is absent, say that the suppression is not justified in the source.
• Prefer narrowing the disabled range or fixing the code. Keep suppression only when development-standard evidence, a verified platform-help source, or a runtime reproduction proves the diagnostic intentionally false-positive. Do not infer a platform limitation from unica.standards.*.

MCP examples

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "unica.code.diagnostics",
    "arguments": {
      "cwd": "<workspace>",
      "sourceDir": "src",
      "mode": "file",
      "path": "CommonModules/Продажи/Ext/Module.bsl",
      "limit": 100
    }
  }
}

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "unica.code.diagnostics",
    "arguments": {
      "cwd": "<workspace>",
      "mode": "catalog",
      "codes": ["UnusedLocalVariable", "DataExchangeLoading"]
    }
  }
}

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "unica.standards.explain",
    "arguments": {
      "codes": ["АПК:142", "LineLength"]
    }
  }
}

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "unica.runtime.execute",
    "arguments": {
      "cwd": "<workspace>",
      "operation": "syntax",
      "mode": "designer-modules",
      "dryRun": false
    }
  }
}