initialize generic rms-software repository

Add the reusable RMS core application (server, web UI, plugins, tests, tools) with generic defaults, GPL licensing, and maintainer context documentation so deployments can consume this repo as software source independent of station-specific overlays.

WORKING_CONTEXT.md

@@ -0,0 +1,47 @@
+# Working Context
+
+Last updated: 2026-03-16
+
+## Purpose
+
+- This repository contains the generic RMS software stack.
+- It is intentionally independent from a specific station deployment.
+- Station-specific configuration and infrastructure binding belongs in separate overlay/deploy repositories.
+
+## Scope
+
+Included here:
+- `server/` backend API and orchestration
+- `public/` web UI
+- `plugins/` plugin catalog and capabilities
+- `test/` automated checks
+- `tools/` local utility scripts
+
+Not included here:
+- production secrets
+- station hostnames and private endpoints
+- station-specific bandmaps/bandplans/deploy service wiring
+
+## Configuration Layers
+
+Expected priority order:
+1. RMS software defaults
+2. Station overlay repository defaults
+3. Runtime environment variables (highest priority)
+
+## Plugin Model
+
+- Plugins declare capabilities and optional UI controls in `manifest.json`.
+- Providers can be switched per capability at runtime.
+- Auth methods are plugin-based (`authMethod` in manifest).
+
+## Deploy Contract
+
+- Deploy repositories should fetch this repository as software source.
+- Deploy repositories may overlay files for station-specific behavior.
+- Deploy repositories must not patch in secrets; secrets come from env files on target systems.
+
+## Current Baseline
+
+- Access token default/minimum baseline is 3 hours.
+- OpenWebRX+ integrations remain plugin- and deploy-driven; station-specific profile/bandplan data stays outside this repo.