Verify config flags actually do something before promising them
Configuring a sync agent or any service whose runtime behaviour depends on env-var inputs documented in .env.example.
A config field can be fully parsed by the loader (env var → typed field → exported) and never actually consumed anywhere in the agent that uses it. The .env.example documents it as a working knob, the type system is happy, the loader returns the expected shape — and the value silently has zero effect on runtime behaviour. The smell is a single grep result for the field outside config.ts and the test that pins config parsing. Before promising a user that a setting will change behaviour, grep for the symbol across the consumer modules — if the loader is the only place that knows about it, the README is lying.
After parsing a new config field, immediately grep that field across the consumer modules. If the only hit is the loader file and its test, the flag is documented vapor — either wire it in or strike it from .env.example.