fix(ci): reduce readiness probe pressure (#1)

docs/deployment/linux.md

@@ -53,9 +53,10 @@ operators should normally keep the checked-in relative defaults. CI starts its
 ephemeral smoke client directly on the isolated Compose network; it does not
 widen the default loopback HTTP publication. It mints the disposable publisher
 credential while the generated key is still owner-private, then makes the key
-read-only for the non-root service container. Automation allows up to 90 seconds
-for a cold image to become ready; the protocol smoke retains its separate,
-stricter scenario timeout.
+read-only for the non-root service container. Automation probes readiness once
+per second and allows up to three minutes for a cold, resource-constrained image
+to become ready; the protocol smoke retains its separate, stricter scenario
+timeout.
 
 `deploy/compose/appsettings.Production.json` is a local/private-bridge smoke
 profile, not an Internet template: TCP is published only on host loopback, the