[core-1] Dashboard tabs are declared by the solver adapter, and by nothing else

[florian-simvia]

Principle

The dashboard tabs a campaign shows are decided by its solver adapter, and by nothing else: not the execution backend, not a user setting, not the campaign configuration, not the frontend.

The adapter states the list. csauto checks that the adapter can feed every tab it lists, and the dashboard renders exactly that list.

Where main stands

Since #22, the tabs already come from the adapter alone. /api/app_config returns adapter.dashboard_panels, and frontend/src/routes/+page.svelte renders exactly that list through showPanel. #34 does not change this.

But the adapter does not choose its tabs. It only implies them:

• dashboard_panels (csauto/solvers/base.py:228) is derived from what the adapter implements. Residuals appears if find_residuals_files is redefined, Probes if list_probe_files is redefined, Performance if performance_columns is non-empty, and Compare if compare_kinds is non-empty.
• Declaring the list explicitly is forbidden: __init_subclass__ (base.py:192) raises TypeError if an adapter declares dashboard_panels.
• Status, Log Tail and Recent Errors are imposed by generic code through ALWAYS_ON_PANELS (base.py:50). No adapter can remove them.

As a result, an adapter cannot hide a tab whose data it provides. Probes, for instance, may be implemented for internal use and still not be worth showing. And an adapter author has to read the derivation rules to know which tabs their solver will get.

Proposal

1. Each adapter declares its tabs

class CodeSaturneAdapter(SolverAdapterBase):
    dashboard_panels: ClassVar[tuple[str, ...]] = (
        "status", "residuals", "probes", "performance", "compare", "tail", "errors",
    )

class CodeAsterAdapter(SolverAdapterBase):
    dashboard_panels: ClassVar[tuple[str, ...]] = ("status", "compare", "tail", "errors")

• The declaration is required: the base class has no default, so a new adapter cannot get tabs by accident.
• ALWAYS_ON_PANELS goes. Status, Log Tail and Recent Errors become ordinary entries the adapter lists, or leaves out.
• The __init_subclass__ ban on dashboard_panels goes. The ban on capabilities stays: capabilities drive actions and buttons, and remain derived.
• Display order stays fixed by ALL_DASHBOARD_PANELS, so tabs appear in the same order whatever the solver. Only the selection belongs to the adapter.

2. A test checks every declaration

For every adapter, each declared tab must be feedable: the method or declaration it depends on is provided. A tab the adapter could feed but does not list is allowed. That is precisely the choice this issue gives the adapter.

This follows 06535bf ("assert analytics parsers imply their declarations"). Unknown tab names fail too, so a typo cannot silently hide a tab.

3. Nothing else may change the list

• Backend: [qarnot-2] Qarnot for every solver: a Run option each adapter opts into (code_saturne, code_aster, openTELEMAC) #36 hides Restart and Stop for a case running on Qarnot. Those are actions, not tabs, so they stay out of this rule. The tabs of a campaign are the same whether its cases run locally or on Qarnot.
• Live data on a backend: an adapter that opts into a backend ([qarnot-2] Qarnot for every solver: a Run option each adapter opts into (code_saturne, code_aster, openTELEMAC) #36) must list in observability_globs the files that feed its declared tabs, otherwise a tab would be shown but stay empty during a remote run. The opt-in test of [qarnot-2] Qarnot for every solver: a Run option each adapter opts into (code_saturne, code_aster, openTELEMAC) #36 should check that, against this declaration.
• Per-case data: a declared tab is never hidden because the selected case has no results yet. It shows its empty state. The fix that keeps a plot tab usable on a case without results (4188a61) is currently in [qarnot-1] Run a campaign on the Qarnot cloud #34, and is worth extracting ahead of it.
• User and campaign settings: no setting hides or adds a tab.

4. Docs

docs/adding-a-solver.md explains how the tabs are derived today. It should instead tell the adapter author to declare them, and say which method feeds each tab.

Order

Part of the Generic core milestone, and the first item in it:

• it is small: csauto/solvers/base.py, the three adapters, one test and the docs;
• it is independent of [core-2] Wire the API layer to adapter attributes that already exist #27 to [core-6] Widen test_solver_boundary.py and give the accepted residue an allowlist #31;
• the Solver adapters milestone needs it, so that [solvers-1] Bring the code_aster adapter up to the level of code_saturne #32's triage is written straight into a declaration and [solvers-2] openTELEMAC adapter #33 declares its tabs from the start.

#34 (Qarnot), which also edits base.py and the adapters, comes in the last milestone and rebases on this.

Effect on other issues

These issues have been updated to match:

• [solvers-1] Bring the code_aster adapter up to the level of code_saturne #32 (code_aster): the triage result becomes code_aster's dashboard_panels, readable in one line.
• [solvers-2] openTELEMAC adapter #33 (openTELEMAC): the adapter declares its tabs from the start.
• [qarnot-2] Qarnot for every solver: a Run option each adapter opts into (code_saturne, code_aster, openTELEMAC) #36 (Qarnot): "capabilities become a function of (solver, backend)" now reads "actions", and the Qarnot requirements check that observability_globs covers the declared tabs.

Definition of done

• Every adapter (code_saturne, code_aster, stub, and openTELEMAC when it lands) declares dashboard_panels explicitly.
• ALWAYS_ON_PANELS and the dashboard_panels ban in __init_subclass__ are gone.
• A test fails if an adapter declares a tab it cannot feed, or an unknown tab name.
• /api/app_config and csauto doctor report exactly the declared list, and the dashboard shows exactly those tabs for every backend.
• For code_saturne, the dashboard is unchanged: it declares the seven tabs it shows today.