Create Railway environments before storage and services

[davejohnson]

What this fixes

Setting up a new Railway environment could stop immediately on storage because Hypervibe tried to inspect the bucket before the Railway environment existed. This is what blocked Billforge staging.

What changes

• Hypervibe now creates or finds the Railway environment first.
• Storage, databases, and services wait for that environment.
• After creating a new Railway environment, apply pauses and asks you to run hv_plan again. This gives Hypervibe fresh live information before it creates anything else.
• An empty Railway storage list is treated as a real observation, so the next plan can offer the expected bucket create action.
• Storage is no longer allowed to secretly create a Railway project or environment.
• Stale environment IDs are repaired only after Railway confirms the old environment is gone.

Safety

If Railway cannot confirm whether the environment exists, Hypervibe blocks instead of guessing. Newly created environments are verified before their IDs are saved.

Checked

• 935 tests pass
• TypeScript typecheck passes
• Production build passes