Workspace startup retries

Workspaces now retry readiness when a machine starts before its provisioning result or billing start is confirmed. These environments can continue starting instead of waiting until the startup deadline. The existing funding and billing checks still apply before work begins.

Machines that fail their checks before starting work are released immediately instead of waiting for the startup timeout. Nodus absorbs the failed machine’s charges when its runtime containment check fails before activation.

Reserved compute (Beta) keeps its scheduled start and expiry deadlines while browser endpoint verification retries. Unverified browser links stay hidden, and a warning appears in the Workspace’s events.