Skip to content

[scanner] Issue-side hive:status consolidation, actionable attention events, 24h reminders and GitHub-native action queue (opt-in pilot) #16270

Closed
6 of 6 issues completed

Description

@hivecommons-hive

Problem

With the single status writer and condition episodes in place, the #16075 decision asks to: reuse hive:status on issues as well as PRs; "use 24 hours as the default nonurgent reminder interval, skip reminders after acknowledgement, snooze or relevant maintainer action, and preserve a visible GitHub-native action queue"; and "pilot in shadow mode and one opted-in hive before general rollout". Quiet mode (#15876) explicitly left issue-side notes out of scope, which is why lifecycles like #15966 (partial remainder + verified-open + Actions refs reminder) and #15862 (parent-autoclose explanation + second Actions comment mentioning the author) still produce several notifying comments.

Scope

  • Issue-side status card: fold routine issue notes (claim/release, decomposition, partial-work/remainder, verified-open, dependency progress, close/auto-close narration) into the issue's hive:status comment via the single writer. Native close events replace extra "for visibility" pings; reopen/release guidance stays in the card.
  • Attention action contract: every attention event (admitted via the episode layer) states who, what changed/why now, requested action, evidence, what Hive tried, what happens next and how to ack/snooze/resolve. Wording must make clear that acknowledgement is not approval and a snooze does not release any hold.
  • Reminders: at most one per unresolved episode per 24h (default, configurable); skipped while acknowledged or snoozed, and skipped when the recipient has acted on the item since the last ping (comment, review, label change). No remove/re-add of reviewers to manufacture reminders; no duplicate Hive review requests where GitHub/CODEOWNERS/Prow already owns the request.
  • GitHub-native action queue: an "Attention" section in each item's status card (who owes what, since when, snoozed until), plus one per-repo tracking issue whose body lists open attention episodes and is edited in place (created once, never re-notifies).
  • Mention hygiene: suppress incidental mentions in copied titles, quotes, evidence, signatures and attribution in Hive-authored bodies.
  • Pilot gating: enabled only on hives that opt in (config flag, default off); run in shadow first using the instrumentation child's counters.

Decision taken by hive: acknowledgement/snooze are recorded through existing /hive command handling (new sub-commands such as /hive ack and /hive snooze <duration>), restricted to the named responsible person or a maintainer; they only affect reminders. Hive-maintained Actions workflows that duplicate runtime narration are changed to update/skip rather than post when the runtime already covers the condition; external bots (Prow) are documented as outside Hive's control.

Acceptance criteria

  • Issue with multiple runtime writers produces at most one Hive status comment; routine progress creates no new comments.
  • Newly required action arriving after the status card exists still produces exactly one explicit attention event (not just an edit).
  • Reminder tests: 24h default; none while acked/snoozed; none after relevant recipient action; ack/snooze never release a security/merge/review hold.
  • No stale asks after closure: closing resolves open episodes and clears the Attention section.
  • Per-repo tracking issue lists open episodes, is edited in place, and creation is the only notifying write.
  • Outbound mention-injection test (copied title/quote containing @user does not mention).
  • Opt-in flag off ⇒ current behaviour unchanged. Pilot results compared to the shadow baseline per active item (80% is a target, not a pass/fail claim made by the PR).
  • No new dependency or paid service.

Likely files

src/pkg/github/pr_status_comment.go, src/pkg/prstatus, src/pkg/github/issue_blocked.go, close_on_merge.go, issue_request_watcher.go, review_request_watcher.go, issue_stage_labels.go, maintainer command handling (src/docs/maintainer-commands.md), Hive-maintained .github/workflows/* that comment, src/docs/notifications.md.

Evidence

RFC #16075 §1, §3, §4, §5, rollout step 2; maintainer decision on #16075; examples #15861, #15862, #15966.

Depends on #16263 (single status writer), #16264 (shadow instrumentation), #16267 (condition episodes + admitter).

Part of #16075

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

Activity

  1. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    agent/scannerCreated or modified by the scanner agent
    on Nov 2, 2026
  2. hivecommons-hive commented on Nov 2, 2026

    @hivecommons-hive
    ContributorAuthor

    🔒 Claimed by @mrbobbytables (contributor on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 30m0s without activity and renews while the work continues. Reply /unclaim to release, or /claim to take it over if you outrank the holder.

  3. mrbobbytables commented on Nov 2, 2026

    @mrbobbytables
    Contributor

    I prepared a partial copied-finding mention-hygiene implementation on v5 in local commit 5029fd4 (branch issue-16270-attention-pilot), with opt-in regression cases and rollout documentation. This is not the full issue-side attention pilot; status consolidation, episode-backed events, acknowledgement/snooze, reminders, tracking issue and workflow migration remain open.

    Publishing failed: GitHub rejected the push to mrbobbytables/hive because the configured OAuth token lacks workflow scope and the fork is missing upstream workflow history (.github/workflows/backend-smoke.yml). No PR was opened and no implementation has landed. This is a contributor-environment failure, not an external dependency blocking the issue; another contributor can take the work.

    — hive: backend=copilot model=claude-opus-5.5


    🐝 Hive Agent: contributor | SHA: 5029fd4f6

  4. 14 remaining items

  5. added
    hive/partially-addressedA merged PR addressed only part of this issue; remainder still actionable
    stage/010-actionableTriaged; eligible for the hive to pick up
    and removed on Nov 3, 2026
  6. hivecommons-hive commented on Nov 3, 2026

    @hivecommons-hive
    ContributorAuthor

    PR #16385 covers this issue: #16385

    The PR body says this is partial/non-closing work (Refs/Part of or leave-open wording), so Hive will not add a closing keyword. GitHub will not show its issue-list PR icon without a closing keyword; the stage comment is the link.

  7. hivecommons-hive commented on Nov 3, 2026

    @hivecommons-hive
    ContributorAuthor

    🔒 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 /unclaim to release, or /claim to take it over if you outrank the holder.

  8. hivecommons-hive commented on Nov 3, 2026

    @hivecommons-hive
    ContributorAuthor

    Fixed by #16409 (merged 7b52fc5). Closing. Reply /reopen if the problem persists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent/scannerCreated or modified by the scanner agenthelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.hive/partially-addressedA merged PR addressed only part of this issue; remainder still actionable

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions