LabKit MATLAB Workbench

history

Launcher code-analysis export

id: LK-20260701-launcher-code-analysis-export
date: 2026-07-01
sequence: 29
type: feat
compatibility: compatible
component: `labkit_launcher` | `1.1.6 -> 1.2.0`
scope: Launcher code-analysis export

Context

The launcher offered a Code Analyzer action, but its earlier implementation carried substantial custom export code. That made a maintenance tool harder to maintain than the MATLAB analysis it was exposing.

Decision and rationale

Use MATLAB's native issue representation and export path, and keep the launcher responsible only for choosing the target and destination. This reduced custom conversion logic while preserving a launcher-level entry point for the report.

Changes

User and data impact

The launcher could export Code Analyzer findings in a MATLAB-supported form without requiring a separate script. This action inspected source code only and did not start or modify an app project.

Compatibility and migration

Existing launcher actions remained available. Newly exported issue files used MATLAB's native representation rather than the removed custom conversion.

Validation

LauncherGuiTest gained coverage for the native issue-export path and the implementation in 8fd3ddff removed more launcher code than it added.

Evidence

Known limitations and follow-up

Code analysis remained a maintainer tool. It did not become a prerequisite for launching an app or a replacement for the repository's automated checks.