From 65fc400fcd8c8b4c3a2f700ad6346ffbd905cd8c Mon Sep 17 00:00:00 2001 From: Paul O'Reilly Date: Fri, 18 Sep 2026 14:18:17 +1200 Subject: [PATCH] fix(gitea-ssh-hatchmate): correct account_ref space id (hatchmate, not platform) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The accelerators/ai-enablement precedent uses the literal 'platform' space id — those credentials happen to live in the platform-owned CP accounts. For hatchmate the credentials live in a CP account owned by the hatchmate space, so the ref must be 'hatchmate.space:hatchmate'. Misnamed ref caused the dispatcher's account resolver to fail with 'no active account for AccountRef(name=hatchmate, scope=space:platform)', failing every review task in the W4 vertical slice within seconds of dispatch. After this lands and the next CRS sync (~5 min) refreshes the concepts PVC, the next auto-advance fire on dfc4358c should resolve the account and proceed through the working-repo clone with the per-org hatchmate key. --- harnesses/contexts/gitea-ssh-hatchmate/v1/harness.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/harnesses/contexts/gitea-ssh-hatchmate/v1/harness.yaml b/harnesses/contexts/gitea-ssh-hatchmate/v1/harness.yaml index 347c754..3328ff6 100644 --- a/harnesses/contexts/gitea-ssh-hatchmate/v1/harness.yaml +++ b/harnesses/contexts/gitea-ssh-hatchmate/v1/harness.yaml @@ -23,6 +23,6 @@ scripts: secrets_required: - name: gitea-ssh-hatchmate - account_ref: "hatchmate.space:platform" + account_ref: "hatchmate.space:hatchmate" mount_path: /run/agent/secrets/gitea-ssh-hatchmate mode: "0400" -- 2.49.1