chore: prune merged feature branches (hyperguild + infra) #65
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: mathias/hyperguild#65
Reference in New Issue
Block a user
Branch debris surfaced during the 2026-06-23 closeout ground-truth pass. All merged, safe to delete after verifying each.
hyperguild (8): feat/capture-mcp-relay, feat/capture-audit-degradation, feat/capture-rest-i1-gate, feat/capture-gitea-tracker, feat/capture-service, feat/capture-classification, chore/drop-cursor-aider-adapters, feat/brain-update-supersede
infra: feat/capture-relay-deploy, adr/0009-brain-interface-consumer-split, docs/architecture-set (these merged this session), plus older debris to verify: feature/git-dma-be-ingress, adr-0004-gitea-rename-github-mirror, feat/qwen36-fast-coder, docs/agentic-dev-platform, docs/agent-platform-nature.
Verify-merged-then-delete. Consider whether the Gitea PR-sweep automation should auto-prune branches on merge.
🤖 dispatch: routing: executor=claude (default — no executor: label) — starting headless run
🤖 dispatch: executor claude failed: runner error: agent run ended in error (see stderr)
Same dispatch stall as #54/#4/#39 — falling back to direct execution. Verified all 8 hyperguild branches against
pr_list(each has a closed PR intomainwith a legitimate shipped-feature title, not an abandoned/rejected one) and deleted:feat/capture-mcp-relay,feat/capture-audit-degradation,feat/capture-rest-i1-gate,feat/capture-gitea-tracker,feat/capture-service,feat/capture-classification,chore/drop-cursor-aider-adapters,feat/brain-update-supersede.infra's branch list (the other half of this issue) is out of scope for tonight's hyperguild/brain-gardener/brain sprint — leaving those, and the "should PR-sweep auto-prune" question, for a separate pass. Closing the hyperguild half.