skynet/agent-runtime-framework
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(gitea-ssh-hatchmate): correct account_ref space id (hatchmate, not platform) #4

Merged
ai_admin merged 1 commits from feat/hatchmate-per-project-fork-key into main 2026-09-18 02:18:47 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
ai_admin commented 2026-09-18 02:18:43 +00:00
Contributor
Copy Link

Follow-up to PR #3 — the accelerators/ai-enablement precedent uses the literal 'platform' space id, but hatchmate credentials live in the hatchmate-owned account. Misnamed ref failed the resolver for every review task.

Follow-up to PR #3 — the accelerators/ai-enablement precedent uses the literal 'platform' space id, but hatchmate credentials live in the hatchmate-owned account. Misnamed ref failed the resolver for every review task.
ai_admin added 1 commit 2026-09-18 02:18:44 +00:00
fix(gitea-ssh-hatchmate): correct account_ref space id (hatchmate, not platform) 65fc400fcd 
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.
ai_admin merged commit f64be1d467 into main 2026-09-18 02:18:47 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
admin ai_enablement
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: skynet/agent-runtime-framework#4
Delete Branch "feat/hatchmate-per-project-fork-key"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?