From 0d2ffbab59182b8a6b9e0685ecf85f6b258c080f Mon Sep 17 00:00:00 2001 From: garrytan Date: Wed, 28 Oct 2026 07:33:56 +0000 Subject: [PATCH] docs: no doc implies QM registration works (document-release audit) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- docs/install.md | 2 +- docs/troubleshooting.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/install.md b/docs/install.md index 637823ef3..9031f353b 100644 --- a/docs/install.md +++ b/docs/install.md @@ -53,7 +53,7 @@ Run inside OpenClaw, Hermes or a Dot, `./setup` also registers gstack's skills with that harness, in the harness's own skills folder, and prints every path it wrote. It never does this when `--host` names another host or with `--local`. Turn it off with `./setup --no-harness-auto` or -`GSTACK_HARNESS_AUTO=0`. Per-harness details, QM and any other harness: [hosts.md](hosts.md#agent-harnesses). +`GSTACK_HARNESS_AUTO=0`. Per-harness details, any other harness, and why QM is not available yet: [hosts.md](hosts.md#agent-harnesses). ## Uninstall diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index ee985392a..0eb279be3 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -5117,7 +5117,7 @@ There is no ledger for that harness or id under `$GSTACK_STATE_ROOT/harness`. `g ### `gstack-harness: no QM admin credential in the environment` / `... needs --yes` (HARNESS_QM_CREDENTIALS) -Registering gstack in QM publishes an org skill pack, so it needs an org admin's credential and an explicit `--yes`. Set `GSTACK_QM_URL` and `GSTACK_QM_ADMIN_TOKEN` (or `GSTACK_QM_SIGNING_SECRET` with `GSTACK_QM_ADMIN_ACTOR`) in the environment and run `gstack-harness register qm --yes`. gstack never prompts for, prints or stores the credential; the message shows the exact request instead. +Registering gstack in QM publishes an org skill pack, so it needs an org admin's credential and an explicit `--yes`. Set `GSTACK_QM_URL` and `GSTACK_QM_ADMIN_TOKEN` (or `GSTACK_QM_SIGNING_SECRET` with `GSTACK_QM_ADMIN_ACTOR`) in the environment and run `gstack-harness register qm --yes`. gstack never prompts for, prints or stores the credential; the message shows the exact request instead. With the credential set, registration still stops at the next check: QM cannot import gstack yet ([HARNESS_QM_PACK_TOO_LARGE](#harness-qm-pack-too-large)). ### `gstack-harness: /v1/admin/skill-packs... returned HTTP ` / `... failed: timed out after 60 s` (HARNESS_QM_API)