cc-settings-api

What problem does it solve? The Director's local HTTP Control API was removed when its network listener was deleted, so any workflow or script that drove settings over loopback HTTP no longer works. This Skill exists to prevent agents from calling the dead API and to point them at the settings mechanisms that actually exist on current builds. ## Core Features & Use Cases - Retirement Notice: Clearly states that the Director's GET /settings and PUT /settings loopback routes no longer exist and that the bundled configure_settings.py script must not be used against a current Director. - Current Settings Paths: Directs users to the desktop Settings dialog for live gateway changes, and to the cc-devthrottle settings get/set CLI commands that read and write config.json directly on disk. - Remote Configuration Guidance: Explains that remote configuration now rides the Gateway's tunnel verbs driven from the Cockpit. - Use Case: An agent asked to change a Director's gateway URL learns here not to hunt for a local port, and instead uses the Settings dialog for a running Director or cc-devthrottle settings set for on-disk edits that apply at next start. ## Quick Start Ask the agent how to change a DevThrottle Director setting on the current build and follow the redirected path it gives you.