v2.0.6 — oumta-dashboard: hardwire config, drop settings tab

This plugin only targets one specific deployment, so the settings
panel was noise that tempted accidental misconfiguration. baseUrl,
authToken and pollIntervalSec now live in a top-of-file CONFIG
constant; the hyprcrd-settings tab, the localStorage persistence,
and the panel CSS are gone.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

public/plugins/oumta-dashboard/README.md

@@ -19,13 +19,15 @@ Close with **ESC** or the × button.
 
 Tab row at the top. Currently two mocks (`oumta-dev`, `oumta-beta`). Real list comes from the backend once `/api/namespaces` exists.
 
-## Settings
+## Configuration
 
-Open the hyprcrd settings overlay and choose the **oumta** tab:
+Hardwired at the top of `oumta-dashboard.js` in the `CONFIG` block:
 
-- **API Base URL** — e.g. `http://localhost:8080` for local dev, or the cluster-internal URL
-- **Auth token** — optional, sent as `Authorization: Bearer …`. Will eventually be filled automatically once Keycloak is wired up.
-- **Poll interval** — polling fallback cadence when SSE is unavailable. Default 15 s.
+- **baseUrl** — where the Oumta Go backend is reachable (default `http://localhost:8085`).
+- **authToken** — optional, sent as `Authorization: Bearer …` when non-empty.
+- **pollIntervalSec** — polling fallback cadence when SSE is unavailable. Default 15 s.
+
+No UI settings panel: the dashboard only runs against one specific deployment, so exposing these as editable fields would be noise.
 
 ## State today