Sleep windows follow the slider: the runtime reads its idle windows from the position, live #10186

Moving the profit slider now changes when apps go to sleep, starting with the next sweep (once a minute) and with no restart. Setting app.always_on: true in an app's forge.json keeps its production awake at any slider position.

• Sweep (src/apps/runtime.ts, src/apps/sleep_window.ts): each pass reads the slider position and picks each environment's idle window from it.

- Previews of quiet pulls follow the slider too: 1 day at 0, 3 days at 50, never at 100. FORGE_PREVIEW_IDLE_DAYS, when set, still fixes that age (src/main.ts). - At the default position of 50, nothing changes.

• Test hooks: the runtime's sleepAfterMs option still fixes the window when set; the forge itself never sets it. A new clock option lets a test move the sweep's time forward.
• Log line: names the window and the position, e.g. asleep: nothing asked for it in 10 min (economy 0); the next request wakes it. This is "10 min", the slider's own short form, where the issue's example said "10 minutes".
• always_on: the issue says app.yaml, but apps here declare themselves in forge.json, so the field is app.always_on.

- Only true or false is accepted; any other value fails the deploy with a reason. - It applies to production only; previews still follow the slider. - When it is set, the app page says it never sleeps whatever the slider says.

• Docs: docs/APPS.md covers the windows, always_on and the FORGE_PREVIEW_IDLE_DAYS default.

Not done: a line on the app page saying how long production has until it sleeps at the current position. Only the always_on exception is shown.

Why the earlier pull was parked: its last check (#10181) never reached an assertion. Shard 3 was killed after 49 s while running test/web-refs-links.test.ts, with the runner at 16% free disk. That file passes on this branch. This push merges current main into the branch; apart from that merge, nothing changed since #10181.

Tests

• test/apps-sleep-slider.test.ts runs a real app:

- At 100, an app idle for 11 minutes stays up. - Moved to 0, the next sweep puts it to sleep and the log has the new line. - After a push that sets always_on, it stays up at 0 and its status says so.

• test/sleep-window.test.ts covers the windows at 0, 50 and 100, always_on winning over 0, the log wording, the forge.json check on the field, and the app-page line.
• scripts/gate.ts, tsc --noEmit and design-lint are clean.
• These test files pass here: sleep-window, apps-sleep-slider, web-refs-links, apps-sleep, apps-idle, apps-busy, slider, idle-pulls-bound and flow-idle-pulls.
• No existing test was changed.

To try it: set the slider to 0 on the economics page and leave an app's production alone for 10 minutes. It goes to sleep and its deploy log names the window. Then add "always_on": true under app in its forge.json and push; it stays up.

🤖 Generated with Claude Code

Closes #506

Moving the profit slider now changes when apps go to sleep, starting with the next sweep (once a minute) and with no restart. Setting app.always_on: true in an app's forge.json keeps its production awake at any slider position.

• Sweep (src/apps/runtime.ts, src/apps/sleep_window.ts): each pass reads the slider position and picks each environment's idle window from it.

- Previews of quiet pulls follow the slider too: 1 day at 0, 3 days at 50, never at 100. FORGE_PREVIEW_IDLE_DAYS, when set, still fixes that age (src/main.ts). - At the default position of 50, nothing changes.

• Test hooks: the runtime's sleepAfterMs option still fixes the window when set; the forge itself never sets it. A new clock option lets a test move the sweep's time forward.
• Log line: names the window and the position, e.g. asleep: nothing asked for it in 10 min (economy 0); the next request wakes it. This is "10 min", the slider's own short form, where the issue's example said "10 minutes".
• always_on: the issue says app.yaml, but apps here declare themselves in forge.json, so the field is app.always_on.

- Only true or false is accepted; any other value fails the deploy with a reason. - It applies to production only; previews still follow the slider. - When it is set, the app page says it never sleeps whatever the slider says.

• Docs: docs/APPS.md covers the windows, always_on and the FORGE_PREVIEW_IDLE_DAYS default.

Not done: a line on the app page saying how long production has until it sleeps at the current position. Only the always_on exception is shown.

Why the earlier pull was parked: its last check (#10181) never reached an assertion. Shard 3 was killed after 49 s while running test/web-refs-links.test.ts, with the runner at 16% free disk. That file passes on this branch. This push merges current main into the branch; apart from that merge, nothing changed since #10181.

Tests

• test/apps-sleep-slider.test.ts runs a real app:

- At 100, an app idle for 11 minutes stays up. - Moved to 0, the next sweep puts it to sleep and the log has the new line. - After a push that sets always_on, it stays up at 0 and its status says so.

• test/sleep-window.test.ts covers the windows at 0, 50 and 100, always_on winning over 0, the log wording, the forge.json check on the field, and the app-page line.
• scripts/gate.ts, tsc --noEmit and design-lint are clean.
• These test files pass here: sleep-window, apps-sleep-slider, web-refs-links, apps-sleep, apps-idle, apps-busy, slider, idle-pulls-bound and flow-idle-pulls.
• No existing test was changed.

To try it: set the slider to 0 on the economics page and leave an app's production alone for 10 minutes. It goes to sleep and its deploy log names the window. Then add "always_on": true under app in its forge.json and push; it stays up.

🤖 Generated with Claude Code