Improve generated UI wallet/network/faucet guardrails #47

Background

Dev users frequently hit wallet/network/faucet confusion during first run.

Goal

Improve generated UI wallet guardrails and recovery flows.

Scope

• Explicit guided states for: disconnected wallet, wrong network, no funds, stale deployment.
• One-click actions where possible: request network switch, open faucet request, retry deployment status.
• Better user messaging for chain mismatch and deploymentEntrypointAddress problems.

Implementation Notes

• Align guidance with th up behavior and manifest semantics.
• Keep copy concise and actionable.

Acceptance Criteria

• Wrong network and no-funds scenarios have clear recovery steps in UI.
• Faucet action provides visible success/failure state.
• Regression tests assert key guardrail messages/actions render.