Restart profile queue worker after backend loss

[rmcdaniel]

Change

Match the published Server Compose queue-worker restart policy in the disposable standard-workflow performance profile. The profile is used by Server #137 runtime comparison and backend-interruption checks. The production Compose stack already uses restart: unless-stopped for its queue worker.

Why

In a local exact-image Swoole qualification fixture, stopping Redis caused the profile's queue worker to exit with a connection error. Server readiness correctly returned 503 and recovered when Redis returned, but workflow processing did not resume until the queue worker was started manually. This was a fixture configuration gap, not an HTTP runtime change.

Verification

• docker compose ... config --format json reports services.worker.restart = unless-stopped.
• With published Server 2.4.26 and the Swoole candidate under the fixed 1 CPU / 1 GiB HTTP envelope, the worker restarted four times while Redis was unavailable, then became healthy without operator action after Redis returned. Server readiness was 503 during the outage and 200 after recovery.
• The 65-second published PHP SDK workflow probe completed 11/11 exact one-activity workflows with zero errors after automatic recovery. The durable database then held 40/40 completed runs, 120 completed workflow tasks, 40 completed activities, zero non-completed tasks and zero duplicate WorkflowCompleted history entries across the earlier interruption and follow-up probes. Server and worker had zero OOM kills.

This adjusts only the disposable profile. It does not select or publish Swoole.

The repository-contract CI run also exposed a binary-read bug in the regression-corpus validator: git show of a tracked gzip blob was decoded as UTF-8 before being re-encoded. The validator now reads Git blob bytes directly. A Python 3.12 container run against base 10b367a835661e2c621249dc4842fd18ef7ab2e4 passed the full regression-corpus validation with unchanged 16/16 codec cases and no review-required paths.

Part of #137.