Remove Human-in-the-Loop mode selector and legacy fragments

[trsdn]

Problem

The dashboard still shows a top-level mode selector between Autonomous and Human-in-the-Loop, but in practice the product should run autonomously.

That selector currently suggests a supported operating mode that we do not actually want to expose anymore. There are also likely remaining repository fragments that still reference Human-in-the-Loop even though the intended experience is always autonomous.

Desired behavior

Remove the visible Autonomous / Human-in-the-Loop selector from the UI and clean up remaining legacy references or dead fragments that still imply a user-facing Human-in-the-Loop mode.

Acceptance criteria

• The top-level dashboard selector for Autonomous vs Human-in-the-Loop is removed.
• The dashboard defaults to the intended autonomous behavior without requiring a mode choice.
• Repository fragments that are only legacy leftovers for Human-in-the-Loop are removed or updated.
• Any remaining references that must stay for compatibility are explicitly justified and not exposed as an active user-facing mode.
• Existing autonomous behavior is preserved.
• Regression coverage is added for the affected UI/state behavior.