Skip to content

[triage-seat task] one-time priority-signal pass over the objectui pm:queue backlog (~64 cards) — type + queue-membership re-grade #9644

Description

@os-support-ai

Named reader: the triage seat (Routine), next fire. This card is an operational pass, not a lane card — execute during sweep, leave the audit trail here, close when the pass is done. Filed by the skills seat (session session_01WswfK2yNYT9hNnMH6TzAwL) recording a maintainer directive.

Maintainer, 2026-08-18, PM chat, verbatim: 「可派发库存 ~60,至少应该分优先级吧」

Measured context (2026-08-18 ~14:1xZ)

  • objectui open pm:queue = 64, ~59 unassigned; oldest unclaimed card 2026-08-09 (9 days); ~14 new cards entered today alone.
  • objectui merged-PR throughput last 7 days = 378 (~54/day) — capacity is not the constraint; selection is: the queue carries almost none of the signals the selection total order keys on (type, target:, pm:blocking, priority:p0), so high-value and polish cards are indistinguishable and old cards get skipped every round.

The pass

  1. Type every objectui pm:queue card (Bug / Feature / Task — the mechanical boundary test as everywhere). The no-backfill rule is deliberately overridden for this one pass by the maintainer's directive above; new cards continue to be typed at filing per standing policy.
  2. Re-grade queue membership while touching each card — a card untouched for 9 days deserves the exit question: still a real queue card? Decision-shaped ⇒ needs-user-decision (four-facet block); observation-grade ⇒ regrade; obsolete ⇒ close not planned with reason (maintainer can veto-reopen).
  3. Derive pm:blocking from the Blocked-by: reverse index over the objectui backlog while at it (standing cache duty, same read).
  4. Report in the round brief: before/after queue depth, type distribution, cards exited, oldest-card age.

Out of scope: lane-splitting objectui (domain:* for objectui) — deliberately deferred by the maintainer pending a post-pass re-measurement of the registered scale-out triggers; do not mint labels for it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions