Review an infrastructure config before deploying

Review this configuration before it deploys.

Report:
1. **Values that differ from the default**, each with the reason if I gave one and a question mark if I did not. *Non-default values without a stated reason are how configs become unmaintainable.*
2. Blast radius per changed value — what it affects beyond the obvious.
3. **Applies immediately / needs restart / needs a rebuild.** Getting this wrong means a change that looks applied and is not.
4. Whether it can be reverted cleanly, and what state persists after a revert.
5. Limits and timeouts that interact — a client timeout shorter than a server timeout, a pool smaller than the concurrency, a retry budget that multiplies load during an incident. These only surface under failure.
6. Anything environment-specific that looks copied from another environment.
7. Secrets or credentials present in the file.

Then: the pre-deploy check, and the first symptom to watch after.

Rules:
- *Do not review the whole file line by line.* Focus on what changed and what it interacts with.
- Where a value's effect depends on a version or provider you cannot verify, say so.
- Flag values that are safe in the current environment but dangerous if this file is copied elsewhere.