Skip to content

🐛 stage engine: proposal/kind-design issues read as Actionable after their RFC lands #17150

Closed

Description

@clubanderson

Problem

Issues labelled proposal (and/or kind/design) whose RFC text has already merged keep deriving to stage/010-actionable. The Activity monitor then shows them as agent work sitting idle, when there is nothing left for an agent to do. Two live cases on hivecommons/hive today:

Mechanics

  • src/pkg/stageengine/derive_issue.go:244-253 — issueProgress books the fall from 040 back to 010 as progress (not a regression) when the issue carries hive/partially-addressed; actionableIssueStage then returns stage/010-actionable for any open, unclaimed, unparked issue regardless of kind.
  • src/pkg/github/issue_claim_gate.go:160-180 — the admission gate refuses only needs-human, the hold family, blocked, parked (045/017) and never-claim labels. proposal / kind/design / 📝 titles are not gated, so the issue is genuinely claimable and "Actionable" is truthful to the scheduler — it is just the wrong stage for an issue whose remaining content is a discussion.
  • src/pkg/claims/neverclaim.go:23 — DefaultNeverClaimLabels = []string{"epic"}: the umbrella family already has a "list of work, not the work" stage treatment (derive_issue.go:197-205); proposals have no equivalent.

Net: the governor sits IDLE with nothing due, and the dashboard shows two "Actionable" items that no lane will ever usefully pick up.

Proposed rule

An open issue labelled proposal (and/or kind/design) with no live claim derives to a non-agent stage in the same family as the epic/never-claim umbrella treatment, rendered in Activity as "Open for discussion" (not "Actionable"). It stays claimable:

  • a human /claim (or the contribute relay) stages it 020/030 as today;
  • removing the proposal / kind/design label returns it to normal 010 derivation;
  • a live agent/contributor claim recorded before the rule still stages 020/030 (mirror the epic behaviour, not stricter).

The rule should not touch the admission gate (issue_claim_gate.go): proposals remain claimable; only the derived stage and its Activity wording change.

Acceptance criteria

  • derive_issue.go: an open issue with proposal or kind/design and no live claim derives to the new stage; with a live claim it derives 020/030 as today.
  • Stage label + Activity chip read "Open for discussion"; the stage reason string names the triggering label.
  • Falling 040 → the new stage after a merged Refs PR is booked as progress, not regression (extend issueProgress).
  • issue_claim_gate.go behaviour unchanged (test: a proposal issue is not refused).
  • Both 📝 RFC: LLM-ranked knowledge advisor (OMP-style) #17054 and 📝 Nous → Spek: feed the winning Nous experiment into spek-new as a source #17020, replayed through the engine, land on the new stage rather than 010.
  • Unit tests in stageengine cover: proposal unclaimed, proposal claimed, kind/design unclaimed, label removed → 010.

Docs to update

  • src/docs/stage-engine-plan.md (and any stage-tracker / stage-label reference) — add the new stage and its derivation rule.
  • src/docs/governor-thresholds.md — note that "Open for discussion" issues do not count toward actionable queue depth (or state explicitly that they do, if that is the decision).
  • CONTRIBUTING.md proposal section — mention that a proposal issue shows as "Open for discussion" until someone claims it.

Activity

  1. added
    bugSomething isn't working
    area/schedulerIssues or PRs related to edge workspace
    dashboardDashboard UI and API issues
    on Nov 8, 2026
  2. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 8, 2026
  3. hivecommons-hive commented on Nov 8, 2026

    @hivecommons-hive
    Contributor

    🔓 Claim by @Karibhou released (lease revoked).

    Claim history
    • 2026-11-08 01:49 UTC — claimed by Karibhou (contributor on hive hosted-available-oke-11-placeholder-r05x)
    • 2026-11-08 02:06 UTC — released by Karibhou (contributor; lease revoked)
  4. added 2 commits that reference this issue on Nov 8, 2026
    f6d7614
    ce5c07e
  5. hivecommons-hive commented on Nov 8, 2026

    @hivecommons-hive
    Contributor

    PR #17220 covers this issue: #17220

    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.

  6. added a commit that references this issue on Nov 8, 2026
    d17151e
  7. added a commit that references this issue on Nov 8, 2026
    bf4b8e7
  8. github-actions commented on Nov 8, 2026

    @github-actions
    Contributor

    @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 /reopen and 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.

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

    area/schedulerIssues or PRs related to edge workspacebugSomething isn't workingdashboardDashboard UI and API issueshelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions