feat: unify runtime diagnostics and repair app workflows

[Pluze]

Goal and scope

• Goal: replace Debug-only launch behavior with clean launches, on-demand synthetic inputs, and an always-on privacy-safe session diagnostic stream while repairing the affected App and Launcher workflows.
• In scope: App SDK diagnostics and synthetic-input contracts; Launcher repair and catalog/UI separation; Batch Crop native-resolution preview and managed ROI interaction; EIS impedance units; semantic event migration across public Apps; documentation, versions, history, and tests.
• Intentionally out of scope: new scientific algorithms, saved-project schema changes, release tagging, and private App source.

User-visible behavior

• Before: Debug launch could preload behavior or produce inconsistent output; ordinary sessions could not retain enough post-incident detail; Batch Crop could downsample ordinary images and lose ROI pointer interaction; Launcher repair and catalog concerns were coupled.
• After: every App starts clean; synthetic inputs are generated explicitly from Developer Tools without loading them; Diagnostics exposes the current sanitized session history and bundle export; Batch Crop keeps native pixels unless its own preview policy requires scaling and supports center/body ROI dragging; Launcher preserves status, details, double-click launch, version browsing, repair, and private discovery while showing a concise user-facing table.
• Compatibility / upgrade note: the App SDK is 2.0.0 (app >=2 <3) and DTA facade is 3.0.0 (dta >=3 <4). Retired diagnostic/debug adapter APIs require migration to BuildSyntheticSample, semantic status events, and the session journal. Saved App projects and scientific result schemas are unchanged.

Validation

• I ran the smallest relevant local validation from docs/development/maintain-and-release/testing.md.
• I ran the required final gate for this handoff, or this PR is not ready for final review.
• Automated validation was not run; reason and risk are recorded below.

Commands and results:

matlab -batch "buildtool changedFast"
PASS: 10/10 selected architecture and runtime-contract identities

matlab -batch "addpath('tools/docs'); repoRoot=pwd; maintainLabKitDocLinks(repoRoot); renderLabKitDocs(); buildtool docsCheck"
PASS: 371/371 generated documentation files current

Focused MATLAB evidence completed during branch iteration:
PASS: App smoke catalog 63/63
PASS: final App/facade/SDK checkpoint 79/79
PASS: Launcher dispatch 11/11
PASS: version management 17/17
PASS: test architecture 10/10
PASS: focused diagnostics, journal, viewer, bundle, projection, instrumentation, App-family workflows, and managed ROI specifications

Manual / native behavior not verified:

• Automated hidden-GUI tests do not establish physical mouse feel. Launcher layout was visually inspected from a rendered native screenshot; final Batch Crop pointer feel remains an explicit developer-led native check before merge.

Documentation and boundaries

• Human docs were updated where user-facing behavior or public contracts changed.
• Agent guidance was updated where execution, ownership, or governance rules changed.
• Docs and agent guidance were left unchanged because their contracts were preserved.
• Versioned component docs and a related docs/history/records/**/*.md record were updated where required.
• App-specific workflow logic stayed in the owning app.
• Reusable +labkit changes, if any, are domain-neutral and app-facing.

Shared runtime behavior is documented once in the App index and framework runtime guide. App manuals contain only App-specific workflow details.

Delivery state

• The branch is committed and pushed.
• Required GitHub checks are linked below, or are pending:

CI / review links:

• Pending on this PR.
• Private App migration is delivered separately in the private repository.

Data hygiene

• This PR does not add raw lab files, identifying file names, subject names, device serials, local absolute paths, timestamps, or private experiment labels.

Unverified behavior

• Final developer-led Batch Crop native pointer interaction and any OS-native file dialogs remain outside hidden automation.