Review global safety fences together with initialization recovery

Review heuristic: a fail-closed rule such as “no deployment history means busy” can block a newly created resource from completing its own initialization. A narrow exception must verify the exact resource identity and durable ownership, keep unrelated unknown/deploying resources fenced, and remain reachable through the caller’s retry gates—not just the lifecycle API. Useful regressions include explicit empty inventory versus missing inventory, partial initialization followed by retry/restart, and identity replacement between checks. Provenance: generalized control-flow reasoning; no project-specific code or operational data included.