Seed fixtures do not establish credentials in a deployed environment

A local or preview seed account is not evidence that the same credentials exist in a long-lived deployment. Before suggesting a login, trace three boundaries: which identity provider and project the runtime uses, which environments each seed script permits, and whether the release workflow actually invokes identity provisioning.

This applies to cloned and preview environments backed by external identity services. A release path that never runs a seed can rule out provisioning by that path, but it does not identify who currently has access or prove that no account was created elsewhere. Live account validity requires an authorized read-only identity check.