L4 0.2.15

Software Factory activation works on Workers Paid, and the VPS installer accepts the published workspace image on both Docker image stores. Landing, Shell, installer, Server, portable runtime and Docs share 0.2.15. Existing customer Servers stay pinned until their operator chooses an update.

• Activate Factory no longer fails with an empty HTTP 500. The container probe treats the default scheduling policy's empty image report as the released image, compares digests when a report is present, and returns that failure on the Factory card. Provisioning writes the released image, size and name onto the Server's container entry and keeps them across a later update.
• Cloudflare consent requests Artifacts Read and Artifacts Write (artifacts.read, artifacts.write). Provisioning checks the namespace first and tells you to reconnect when those scopes are missing. Reconnect once so the new grant replaces an older 25-scope token.
• The Factory page on /create stays on Factory after Cloudflare returns. The paid-usage checkbox is kept in this browser across that redirect, and a missing Cloudflare account list includes the provider error.
• The landing headline introduces L4 and matches the page title. VPS installation is labelled “Your server”.
• The VPS workspace pin matches the loaded image id to the published image id, config digest or index digest. Classic Docker and containerd both verify the same release, and the executor keeps the id the local daemon loaded.
• Factory checks for systemd before it writes executor files. A fresh Server install stays successful when only the optional Factory step fails. llll factory status and logs fail clearly without systemd. llll factory enable --trust-shared-kernel --no-systemd prepares the verified files and prints the manual node command.
• Loopback LLLL_NO_TLS publishes on 127.0.0.1. The installer creates its lock directory or names that failure. Long container waits print progress. A VPS Factory card describes host capacity. Running the installer again with LLLL_FACTORY=true says how to enable Factory when no executor is installed.

No Server SQL migration is required. Durable Object migration v5-factory-executor is unchanged. Published releases and earlier migrations remain immutable.

Reconnect Cloudflare before provisioning Factory on an account whose previous grant predates the Artifacts scopes. A Server provisioned by 0.2.14 should be provisioned again so its container entry receives the released image, then activated from Settings → Repositories. VPS hosts that already loaded the 0.2.14 workspace image should enable Factory again from 0.2.15 so the local image id is recorded.