What problem does it solve? Adding a new runtime-tunable setting to the Catalyst Code core requires touching five separate layers (struct field, JSON parsing, environment variables, CLI flags, and TUI/web surfacing), and missing any one of them produces an inconsistent or silently broken configuration option. ## Core Features & Use Cases - Five-layer wiring guide: Step-by-step instructions for adding a field to the Config struct, reading it from JSON via apply_json, loading CATALYST_CODE_* environment variables, parsing CLI flags, and surfacing it in the TUI/web settings. - Precedence and merge semantics: Documents the full config precedence chain (CLI > env > settings.local.json > settings.json > user config files) and how arrays and objects merge. - Security guardrails: Warns against reading security-sensitive toggles from project-local JSON files and against documenting env vars that are never actually read in load(). - Use Case: You want to add a new timeout knob like request_timeout_secs. Follow the skill to add the struct field with a default, wire JSON/env/CLI parsing, expose it via set_config and the ready event, and verify with cargo clippy and a unit test. ## Quick Start Add a new configuration setting named max_retries to the core following the add-config-knob five-layer wiring steps.
