Triage long-stale pull requests #101 and #50

[sambetts]

Problem

Two pull requests have been open long enough that their value is unclear and their cost is real:

• New v3 for Analytics Report #101 "New v3 for Analytics Report" — draft, opened May 2026, +941/-0 across 3 files. Purely additive.
• Soonish aggregation #50 "Soonish aggregation" — draft, opened April 2025, +2733/-1009 across 16 files, and already CONFLICTING.

Why it matters

Stale PRs of this size accumulate conflicts against a moving dev until reviving them costs more than rewriting them. #50 in particular is 16 months old and touches 16 files, so every week it stays open makes it less likely to ever land.

They also add noise to the PR list, which makes it harder to see what is actually in flight.

Action

For each, decide and record:

1. Revive — bring up to date with dev, resolve conflicts, mark ready for review.
2. Close — with a comment explaining why, and an issue capturing anything still worth doing so the intent is not lost.

Acceptance criteria

• Both PRs are either ready for review against current dev, or closed with the reasoning recorded.

[sambetts]

Triage completed.

Findings:

• New v3 for Analytics Report #101 is still draft but currently mergeable. It is a potentially salvageable report-model v3 proposal, but its own checklist says the profiling SQL side is still pending and the described change may affect older/custom reports. I commented asking the author whether to complete/split it or close it.
• Soonish aggregation #50 is draft, broad, and GitHub reports it as conflicting/dirty. Given its age and overlap with newer Copilot/profiling work, I recommended treating it as a manual rewrite into smaller PRs if the idea is still wanted, rather than trying to merge the old branch. I commented asking the author whether to revive or close.

Because these PRs are authored by another contributor, I did not close them. The triage requested by this issue is done and the decision now sits with the author/maintainers, so I am closing this tracking issue.