Default status names

I'm curious why we use `safe-to-run` and `safe-to-deploy`, which map to `safe for dev` and `safe for production` instead of straightforwardly saying the latter?

Also, in some cases couldn't `safe for dev` be a higher standard because it can access your file system? I guess in Rust that's always assumed, so no?

No files, tests, or entry points are named. Start by locating where `safe-to-run`, `safe-to-deploy`, `safe for dev`, and `safe for production` are defined and used, then clarify whether the goal is renaming the statuses or revising their security meaning; done requires an agreed naming and policy change.

Written by the indexing model from the issue text.