Repository navigation
[security] agent_issue_decision_policy=resolve fails open on unclassified --needs-decision text #12969
Description
Raised by the ci-maintainer security perspective on #12903 and deferred there as a cross-path policy change.
issueDecisionDowngrade (src/pkg/github/issue_request_watcher.go) parks only when decisionpolicy.Classify(text).Escalate is true. Classify returns the zero Classification{} (Escalate=false) when neither a risk term nor a non-risk engineering term matches, and EffectivePolicy defaults to resolve — so on a stock hive a Hive-authored --needs-decision whose wording misses both keyword lists is silently downgraded (not parked) and gets a Decision taken by hive footer instead of reaching the owner. This applies equally to the issue, label (#12852) and, since #12903, comment paths.
Proposed: fail closed on every path — downgrade only on a positive engineering classification (decisionpolicy.ResolvesWithoutHuman(text), already defined), park otherwise; add tests with neutral wording (e.g. "Agents do not edit repository settings; the owner runs: gh api --method PUT …") asserting the park still happens under resolve. Land on v5, forward-merge to v6.
Risk: security posture
Activity
hivecommons-hive commentedon Oct 19, 2026
🔒 Claimed by agent
scanner(agent on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 2h0m0s without activity and renews while the work continues. Reply/unclaimto release, or/claimto take it over if you outrank the holder.changelog: make the #12969 fragment a bullet entry and drop the autof…
🐛 fix: fail closed when resolve policy cannot classify a needs-decisi…
github-actions commentedon Oct 19, 2026
@clubanderson this issue was closed by @hivecommons-hive[bot] as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment
/reopenand it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.