The settings screen I did not build

A plugin with three configuration values, deployed by a pipeline, and a settings screen that would have had one user.

// the entire configuration surface
define( 'TD_SYNC_ENDPOINT', 'https://supplier.example/v2' );
define( 'TD_SYNC_BATCH_SIZE', 500 );

add_filter( 'td_sync_should_run', function ( bool $default ): bool {
    return $default && ! wp_get_environment_type() === 'local';
} );

A settings screen exists so somebody without deployment access can change something, and on a site whose configuration is in a repository that person does not exist. The filter is the extension point and documenting it as one — in the readme, with a signature — is what makes this a decision rather than an omission.