kubestellar-hive files PRs with titles that fail the Conventional Commits check

[castrojo]

Problem

The kubestellar-hive app opens PRs titled with a bracketed prefix:

• test: add BATS regression coverage for theming hook #926 — [quality] add BATS regression coverage for theming hook
• test(docs): add check-skill-index regression tests #924 — [quality] add docs skill validator regression tests

The validate workflow runs a Validate PR title (Conventional Commits) step, which rejects these:

ERROR: PR title does not follow Conventional Commits.

validate is a required status check in the main — merge queue ruleset, so these PRs are born unmergeable. They sit in the queue accumulating red CI until a human notices the failure is about the title rather than the code, and manually runs gh pr edit --title.

Why it's worth fixing at the source

• The failure is indistinguishable from a real failure in the check rollup — validate is one job with several steps, so a title violation and a genuine test failure both surface as validate: FAILURE. Triage cost is paid on every bot PR.
• It burns reviewer attention on a mechanical rename that the bot could have gotten right.
• It contributed to the impression that the PR backlog was full of broken changes when the underlying code was fine.

Fix

Have the bot emit a Conventional Commits title. The [quality] marker maps naturally onto existing types:

Current	Suggested
[quality] add BATS regression coverage for theming hook	test: add BATS regression coverage for theming hook
[quality] add docs skill validator regression tests	test(docs): add check-skill-index regression tests

If the [quality] marker carries meaning for Hive routing, move it to a label or the PR body rather than the title.

Verification

# Reproduce: inspect which validate step failed on a bot PR
gh run view "$(gh pr checks 926 --json name,link \
  --jq '.[]|select(.name=="validate")|.link' | grep -oP '(?<=runs/)\d+')" --log-failed \
  | grep -i "conventional"

Surfaced while triaging the PR backlog. #924 was retitled by hand to unblock it; #926 still has the problem.

[castrojo]

Found the mechanical half of this while landing #926.

.github/workflows/validate.yml triggers on pull_request with no types:
filter, so it uses the default set: opened, synchronize, reopened.
edited is not included.

Consequence: when a maintainer fixes a bad PR title, the Conventional Commits
check does not re-run. gh run rerun --failed doesn't help either — a rerun
replays the original event payload, so it re-reads the old title and fails
again. The only ways to go green today are pushing a commit or closing and
reopening the PR. I had to close/reopen #926.

So a [quality] ... PR from kubestellar-hive isn't just born unmergeable —
it stays unmergeable after the obvious fix, which is what makes it feel broken.

Suggested fix alongside whatever is done about the bot's title format:

on:
  pull_request:
    types: [opened, synchronize, reopened, edited]
    branches:
      - main
  merge_group:

The title step is already gated on if: github.event_name == 'pull_request',
so edited events cost one short job and nothing else.

[Danathar]

Resolved at the source. Hive shipped hivecommons/hive#7159, which makes a repository's AGENTS.md take precedence over Hive's built-in prompts, and every Hive PR opened in this repo since 2026-09-12 (#1106, #1108, #1118, #1122, #1125, #1127, #1128, #1138) has a Conventional Commits title. The older PRs that predated the fix were retitled under #1132.

The mechanical half noted in the comment above — validate.yml not re-running on title edits because edited isn't in its pull_request types — is still true and is worth its own small fix if it keeps biting.