[strategist] Hive App lacks `workflows` permission — every CI fix requires human re-implementation
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
## Strategic Finding
**Type**: adoption-blocker (agent-fleet autonomy)
**Horizon**: near-term
The kubestellar-hive GitHub App installation on this repo has `contents:write` but not the `workflows` permission, so agent branches that touch `.github/workflows/**` cannot be pushed. Observable consequences in the current queue:
- #103 (bot) ships CI fixes as evidence + `.patch` artifact files instead of an applicable branch.
- #56, #114, #116 (human-authored) are manual re-implementations of bot findings — the human merge gate is also doing the implementation work for every CI/workflow fix.
- Security fixes that live in workflows (e.g. #43/#112 Prince SHA-256, #42 SHA pinning) all pay this double cost.
## Rationale
The fleet's value proposition is that humans review and merge while agents implement. For workflow files that loop is broken: agents find the issues, but humans must re-do the work before they can review it. With CI hardening (SHA pinning, installer verification, test wiring) being a Phase 0 exit criterion, this permission gap sits directly on the launch critical path in LAUNCH.md (W-13 close-Phase-0 item).
## Proposed Next Step
Request the `workflows` permission (GitHub App settings → Permissions → Actions/Workflows) for the kubestellar-hive installation on this repo, then re-drive the stranded bot fixes (#103 artifacts, #87/#107 dedup) as real branches. If granting the permission is declined, document the human-re-implementation loop explicitly in GOVERNANCE.md so the fleet stops opening artifact PRs.
---
*Filed by strategist agent (ACMM L6 — full mode)*
Contributor guide
Research direction
Read the W-13 item in LAUNCH.md and inspect the kubestellar-hive GitHub App installation's Actions/Workflows permission settings. Confirm whether the permission can be granted, then check the stranded fixes in #103, #87, and #107 for branch-based re-drive; if access is declined, document the human re-implementation loop in GOVERNANCE.md.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100