test: add Crestodian QA lab setup scenario

docs/cli/crestodian.md

@@ -306,7 +306,12 @@ pnpm test:docker:crestodian-first-run
 
 That lane starts with an empty state dir, routes bare `openclaw` to Crestodian,
 sets the default model, creates an additional agent, configures Discord through
-a token SecretRef, validates config, and checks the audit log.
+a plugin enablement plus token SecretRef, validates config, and checks the audit
+log. QA Lab also has a repo-backed scenario for the same Ring 0 flow:
+
+```bash
+pnpm openclaw qa suite --scenario crestodian-ring-zero-setup
+```
 
 ## Related
 

docs/help/testing.md

@@ -65,8 +65,10 @@ When debugging real providers/models (requires real creds):
     config write.
 - Crestodian first-run Docker smoke: `pnpm test:docker:crestodian-first-run`
   - Starts from an empty OpenClaw state dir, routes bare `openclaw` to
-    Crestodian, applies setup/model/agent/Discord SecretRef writes, validates
-    config, and verifies audit entries.
+    Crestodian, applies setup/model/agent/Discord plugin + SecretRef writes,
+    validates config, and verifies audit entries. The same Ring 0 setup path is
+    also covered in QA Lab by
+    `pnpm openclaw qa suite --scenario crestodian-ring-zero-setup`.
 - Moonshot/Kimi cost smoke: with `MOONSHOT_API_KEY` set, run
   `openclaw models list --provider moonshot --json`, then run an isolated
   `openclaw agent --local --session-id live-kimi-cost --message 'Reply exactly: KIMI_LIVE_OK' --thinking off --json`