Config Validator (static summary)

The interactive validator UI is temporarily disabled while we move it to a client-only component. Use this checklist to keep configs healthy until the tool returns.

Critical checks

• Balanced delimiters and unclosed strings
• Missing Config table or JSON root objects
• Hardcoded secrets (DB creds, API keys, webhook URLs)
• Debug flags left enabled (Config.Debug, debug=true)
• Missing recommended keys: Config.Locale, Config.UseTarget, job/grade arrays

Quick validation workflow

1. Run a search for Debug = true, debug=true, and placeholder credentials.
2. Confirm every resource registers Config = Config or {} before assignments.
3. Validate JSON files with jq or python -m json.tool for schema drift.
4. Enforce consistent locales and feature flags via env vars or convars.
5. Keep exports documented per resource so downstream scripts can type-check.

Rollout tips

• Add a CI step to lint configs before deployment.
• Keep sample configs in config.example.* and never commit secrets.
• After large edits, run resmon and smoke-test start/stop flows for each resource.

Roadmap

The UI validator will return with file uploads, inline linting, and JSON/Lua outputs once the client component path is restored.