Add a configuration flag with its defaults, validation, and documentation
A new setting wired the way every other setting in the project is wired.
The ticket
Add a configuration flag following the project's existing configuration pattern.
Acceptance criteria
- The flag is validated at startup rather than at first use
- Each branch has a test
- The default is documented alongside the other settings
- An invalid value fails loudly at boot
What lands as proof
Tests for both branches plus a boot failure on an invalid value, so a typo cannot ship silently.
Why teams defer it
- Configuration is scattered across a schema, a type, a default, and a document, so a one-line setting touches four files.
- Nobody remembers all four, which is how half-wired flags get shipped.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: add a configuration flag following the project's existing configuration pattern. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means a test per branch, the default recorded in the docs, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.