X_SEED_ENVIRONMENT

the seed's tier is not one this environment runs

x db seed <name> naming a dev-tier seed while ULTIMATE_ENV resolves production, which runs reference only. dev fixtures reaching production is the one irreversible thing x db seed can do, so it is refused rather than confirmed — and the check runs twice, in selectSeeds and again in cmd-db.ts before the driver is booted, because the layer that opens a connection to production must not be the only layer that decided it was allowed to. Its own code and not X_CLI_BAD_FLAG: the argv was well formed, and the one remedy is naming the tier rather than re-reading x help

x db seed <name> --tier <tier> --json — the cause names the tier and the environment. For a container whose command line is fixed, ULTIMATE_SEED_TIER=<tier> says the same thing, and the cause names it too