Unexpected container hibernation during Replit deployment workflow

Goal: Ensure that a Repl deployed from the IDE transitions to a stable production instance without being subject to unexpected container hibernation that interrupts service.

Constraints: The free tier imposes resource limits that can cause containers to hibernate after periods of inactivity; the deployment workflow moves from a development container to a production‑ready instance, but it is unclear whether the same idle timeout applies to the production environment. The .replit file defines the run command, and secrets are stored via the Secrets tool, yet these configurations do not appear to affect hibernation behavior.

Uncertainty: Whether the production instance respects the free‑tier hibernation policy, if adjusting the run command or adding a keep‑alive process can mitigate hibernation, and if Replit provides any official setting to disable or extend the timeout for deployed apps.

Specific questions:

• Does the production instance created by Replit’s deployment workflow inherit the same idle timeout as the development container?
• Can configuring a background keep‑alive process in the .replit file prevent hibernation of the deployed app?
• Is there a documented method or feature flag to disable or extend the hibernation timeout for free‑tier deployed Repls?