Private configuration

config.toml is private and must remain secret from coding agents.

Never open, read, search, copy, print, diff, or otherwise inspect that file's contents with agent tools or helper scripts.
Exclude it explicitly from repository searches, even when searching ignored files.
The application may load its private configuration internally during user-authorized runs; this does not authorize displaying or inspecting the configuration or credentials. Use isolated tests with synthetic configuration and credentials for unit verification.
Make configuration changes only in config.example.toml; the user maintains the private file.
Do not inspect or log credentials, runtime session cookies, or authentication tokens. The user permits inspecting API/chart response data for debugging.