solmara-lab: default ports and purpose URIs repeated across five independently maintained surfaces

[jeremi]

Repo: the standalone solmara-lab repo (tracked here until it has a remote). Found during the 2026-07-07 YAML config audit.

Context

Default service ports (43xx family, 54329, 63799) and purpose URIs (https://id.registrystack.org/solmara/purpose/...) are hardcoded independently in .env.example, compose.yaml, scenarios/service_config.py, perf/k6/*.js, and requests/registry-lab/environments/Local Compose.bru (URIs additionally in ministries/*/manifest/fragment.yaml, notaries/*.yaml, metadata/assembly.yaml, and the wave manifest). Nothing cross-checks them; a port or URI change requires touching five-plus files and CI will not notice a miss.

Scope

Pick a cheap mechanism: a single defaults table that generates the Bruno environment and k6 defaults, or a lint that cross-checks the literals across surfaces. Full templating is overkill; drift detection is the goal.

Acceptance

• Changing a default port or purpose URI in one place either propagates or fails lint.

[jeremi]

Triage update (2026-07-14): registrystack/solmara-lab now has its own repository, and this issue is entirely about that repository's configuration surfaces. Transferring it there so ownership, code changes, and CI stay together.