SQLAlchemy Backlog Intelligence

A read-only, public-safe backlog compression view. It turns individual notifications into an auditable maintainer work plan with linked evidence underneath. No GitHub writes are performed.

all open issues represented
186
Open issues
all represented
32
Open PRs
full local PR graph
99
Review groups
46.8% fewer review units
11
Maintainer moves
88.9% fewer than review groups
175
Work threads
expandable evidence graph
19
PR-backed groups
issues + PRs reviewed together
207
No-write audit rows
dry-run only

Recommended Workflow

This static run compresses 186 open issues and 32 open PRs into 99 review groups, then into 11 recommended maintainer moves. Start with maintainer-owned unblock work, then repair-ready failing PRs, then PR lineages, then batch issue sweeps, then volunteer-ready bundles.

local-only; no GitHub writes

Do First: Maintainer-Owned Unblocks

2 action queues · 27 issues affected · 22 PRs

Stalled work where the next action is maintainer-owned, such as repo-owner test approval or final review.

Example: PRs waiting on repo-owner test approval are separated from contributor-blocked PRs, so maintainers can unblock them without rereading the full thread.

  • approve/inspect gated test run
    12 bundles · 24 issues · 18 PRs
  • make final PR decision
    4 bundles · 3 issues · 4 PRs

Do Second: Repair-Ready PRs

2 action queues · 4 issues affected · 9 PRs

Open PRs with named failing checks, merge state, or concrete repair direction.

  • fix failing static/type checks
    3 bundles · 2 issues · 4 PRs
  • update blocked branch
    3 bundles · 2 issues · 5 PRs

Do Third: PR Lineage Cleanup

1 action queue · 24 issues affected · 15 PRs

Older, superseded, or overlapping PR attempts that should be reviewed together.

  • resolve overlapping PR lineage
    9 bundles · 24 issues · 15 PRs

Do Fourth: Batch Issue Sweeps

4 action queues · 117 issues affected · 1 PR

Grouped issue families where one policy, duplicate, close, or clarification pass can cover several rows.

  • park or close contributor-waiting PRs
    1 bundle · 1 issue · 1 PR
  • apply stale sweep policy
    25 bundles · 111 issues · 0 PRs
  • consolidate duplicate candidates
    1 bundle · 2 issues · 0 PRs
  • park or close waiting-info issues
    3 bundles · 3 issues · 0 PRs

Do Fifth: Volunteer Bundles

2 action queues · 38 issues affected · 0 PRs

Contributor-ready issue slices with shared scope, labels, and test expectations.

  • prepare patch-plan bundle
    11 bundles · 16 issues · 0 PRs
  • prepare volunteer-ready bundle
    12 bundles · 22 issues · 0 PRs

How This Reduces Maintainer Time

The output does not act on GitHub. It turns individual notifications into evidence-bound review units.

Maintainer moves firstShows what a maintainer should do first, second, third, and why.
Threads stay expandableReview threads, relationship edges, and raw rows remain underneath for audit.
Specific blockersPR states are split into owner gates, contributor waits, check fixes, review decisions, and branch updates.
Batchable issue workDuplicate, stale, waiting-info, and volunteer-ready rows are handled as grouped sessions.