feat(dashboard): add native operations tab

[PhilipJohnBasile]

Scope

Read-only Native MTPLX operations tab, extracted from #336. Displays setup, diagnostics, inspect and benchmark commands, quotes shell-sensitive model IDs, and includes navigation/keyboard routing. It copies commands; it does not execute processes or add a backend API.

Current readiness

Head 05cb79271b454f17072b12898a7248a098de5901 is integrated with upstream 21be78b3f51820eecef020e5e4855c0715eaf9a5 through a normal merge. The source-only cleanup remains intact: only four dashboard source files plus scripts/bench_native_dashboard.mjs differ from main. No rebuilt static assets are included.

Readiness run 34069355260, macOS ARM64 / Python 3.11 / Node 22:

• 421 serving/dashboard/import-boundary tests passed, zero failures/errors/skips.
• Frozen Bun dependency installation and production dashboard build passed. This build completed in 4.20 seconds; it is not a paired performance benchmark.
• Python compilation and diff checks passed.
• After validation, generated assets were restored to the upstream tree and the absence of a static-asset diff was asserted.
• Exact tested merge commit fast-forwarded to this PR; no fork-only audit workflow/helper is included.

Ready for source review. #362 now includes a real serving-status provider, addressing the previously identified empty-registry dependency for coordinated #362/#364/#365 review. Release order and maintainer approval remain separate.

Historical measurement

The earlier three-run benchmark reported upstream median 2584.632 ms versus feature median 2653.999 ms (+2.68%), and a generated-bundle delta of 10,345 raw / 2,696 gzip bytes. Those historical values are retained for context, not relabeled as measurements of the new integrated head.

Excluded: runtime ownership, adaptive controls, telemetry panels, server-side execution and unrelated systems from #336.

[youssofal]

Thanks for splitting these out cleanly. As a set they are read-only and low risk, and the registry is the piece the other two depend on. They will be reviewed together for the next release once there is a first component that publishes into GET /v1/mtplx/systems. An empty registry with a tab over it is not something I want to ship before that.

One request for then: leave the rebuilt dashboard assets out of the PRs and let the release build regenerate them, so the diff is source only. Not in 2.11.2.

[PhilipJohnBasile]

@youssofal Addressed the source-only request in baeae5e. I restored mtplx/dashboard/_static to the exact merge-base subtree, so the PR now changes only four dashboard source files and the benchmark script. The Native tab source is unchanged; the release build regenerates the assets.

The description now distinguishes the existing build measurements from this asset-only cleanup. Ready for source review, with the next-release/provider coordination for #362/#364/#365 still intact.

[PhilipJohnBasile]

Current-main readiness update: 05cb792 includes 21be78b. All 421 serving/dashboard/import-boundary tests and the production dashboard build passed on the exact candidate before the branch was fast-forwarded. Static assets were restored and the source-only diff asserted. Receipt: https://github.com/PhilipJohnBasile/MTPLX/actions/runs/34069355260 .

#362 now contains a real read-only serving provider, not an empty registry, so the previously missing producer is ready for coordinated review with #365. This PR still only copies commands and does not own runtime operations.