What changed
We repaired production OpenClaw authentication and runtime permissions that could cause the trial signup advanced setup to fail. The release hardened the service-device defaults used by app and worker runtimes, added a preflight check to the automated signup runbook, and expanded recovery steps in the OpenClaw runbook for operator scope, device approval, and identity/device ACL repair. The investigation and related artifacts were archived for operations reference.
User impact
If you start a trial, you should no longer remain stuck behind the advanced setup failure banner caused by OpenClaw auth or runtime-permission drift. Password-reset flows used in verification were also checked and validated. This was an operations-focused fix; the visible signup and reset UI did not change.
Operational notes
The affected post-signup prep job was retried and completed. Non-visual operational evidence images are included with this changelog. Operators also ran automated signup and password-reset verification and inspected production logs and health checks to confirm the issue was resolved.
What’s next
Operators may consider surfacing a more specific message when advanced setup fails due to gateway auth or runtime permissions. No further action is required from jobseekers at this time.
Summary: Production OpenClaw auth and runtime permissions were repaired so trial signup advanced setup can complete reliably; this was an operations-only change with no visible UI updates.