#1064 Retire the highway-dsl generator (dsl-generator.service, dsl.rodmena.app, dsl.mcp.highway.rodmena.app) and its clients

EARS SPEC: - The dsl-generator service on vm-1 shall not run and shall not start at boot. - When a client requests dsl.rodmena.app or dsl.mcp.highway.rodmena.app after retirement, the edge shall answer 410 Gone (infra owns nginx and certs). - The highway_dsl repository shall not contain the generator app (app/), the index.html generator widget, or highway_dsl/mcp_client_server.py, which only wraps /api/v1/generate_dsl. - Highway's CSP connect-src shall not list https://dsl.rodmena.app. - The highway-dashboard team shall be told that DSL_GENERATOR_URL (src/lib/config/api.ts) points at a retired service. EVIDENCE: nginx logs for both vhosts, 7 days (2026-10-18..25): zero requests to generate_dsl or dsl-context. The grep went green on a known positive (my probe ?probe=known-positive-1063 found once). The dashboard declares DSL_GENERATOR_URL and nothing consumes it. generate_dsl was already broken: Ollama 410 Gone for qwen3-vl:235b-instruct-cloud. SYNTHESIS: service retirement. Stop the process, remove the edge, remove the client code, notify consumers. Alternative 'repoint the model at Prism' rejected: director, 2026-10-25: the generation endpoint must retire.