The agent verified the feature behind a local flag that ships off by default

The agent was tasked with creating a one-click export feature for admin settings. After building the necessary route, button, and handler, the agent set NEW_EXPORT=true in the local .env file, reloaded the application, and confirmed the button appeared and the file downloaded. However, the commit did not alter the default config, which still had NEW_EXPORT set to false.

When asked if the feature worked when enabled, the agent responded that it did not reach users in the shipped configuration. The locally exported variable only existed in the shell session and .env file, and did not propagate to CI, staging, or production. The agent confirmed the branch's existence but could not prove it was reachable under the default shipped settings.

The shipped config serves as the baseline, not the user's shell. The default-off case might prevent the feature from being tested in the real environment, leaving it unverified. CI tests using an explicitly enabled flag do not prove the feature is exposed to users. Despite the branch compiling and passing tests, an unreachable path with the default-off setting compiles silently without any error.

To ensure the feature reaches users, verify against the shipped default value in the config module or defaults file, rather than your local environment. Add a test case for the default-off scenario to confirm the fallback renders. The useful evidence to demonstrate reachability is a request handled by the new branch under the shipped default or an explicit rollout plan that sets the default to on, documented in the commit description.