🐛 dashboard: Overview open-issue/PR totals explain their gap to the forge counts

[clubanderson]

Summary

• Made the Overview Total open issues and Total open PRs KPIs use forge-open totals already captured on the scanner tick, with muted sub-lines showing how much of that population is visible in Overview bands versus filtered outside them.
• Added server-side overviewTotals to /api/status, scanner detail for hard-suppress/exempt issue filters, UI tooltips/sub-lines, docs, changelog, and regression coverage.

Closes #10629

Trace / root cause

Before this PR the Overview cards were not forge totals. The browser built the card values from Overview band slices: overviewIssueBandSlices() walks repos[].actionableIssues plus repos[].heldIssues, while overviewPRBandSlices() walks repos[].openPrs plus repos[].heldPrs; renderOverviewKPIs() then summed those slices for the visible card values (src/pkg/dashboard/static/index.html:12482, src/pkg/dashboard/static/index.html:12521, src/pkg/dashboard/static/index.html:13162). Those arrays come from /api/status.repos[]; FrontendRepo.ActionableIssues/OpenPrs are explicitly the automated-consumer/actionable sets, and HeldIssues/HeldPrs are display-only hold sets (src/pkg/dashboard/server.go:832). buildRepos() fills them from the scanner result and separately attaches WorkBreakdown/raw counts (src/pkg/dashboard/status_builder.go:1927).

The scanner starts from GitHub open data on the existing scan tick: issues use GET /repos/{owner}/{repo}/issues?state=open and then skip pull requests (src/pkg/github/issue_dependencies.go:59, src/pkg/github/client.go:1131); PRs use PullRequests.List(state=open) (src/pkg/github/client.go:1337). The filters before an issue reaches actionableIssues are, in order: standing meta issues (hive/advisory and dependency dashboards), hold labels (moved to heldIssues), governor exempt labels, hard-suppress labels (needs-human, needs-direction, needs-decision, needs-spec), reporter-trust triage for untrusted human reporters, then project.issue_filter.require_labels (src/pkg/github/client.go:1137, src/pkg/github/client.go:1156, src/pkg/github/client.go:1172, src/pkg/github/client.go:1200, src/pkg/github/client.go:1209). Bot-authored issues are not dropped merely for being bots; they are annotated with author_is_human/human acknowledgment for banding after admission (src/pkg/github/client.go:1216). PRs are counted from all open PRs, then hold labels move non-draft held PRs to heldPrs, exempt labels filter, drafts are counted as drafts but excluded from openPrs, and the rest enter openPrs (src/pkg/github/client.go:1358, src/pkg/github/client.go:1365, src/pkg/github/client.go:1420, src/pkg/github/client.go:1425, src/pkg/github/client.go:1457). No age window or dedupe is applied in these count paths; multi-repo union is by the configured repo list. That explains the symptom: issues can be lower than GitHub because hard-suppressed/exempt/reporter-triage/meta issues were outside the Overview bands; PRs can be higher than the single GitHub repo header when the selected/configured repo set spans multiple repos, while drafts/filtered PRs explain gaps between forge totals and Overview bands.

Fix choice

The configured repo set is the dashboard scope operators select, so the cards now show forge-open totals for that selected configured repo set. The server publishes all-repo overviewTotals from the scanner's cached WorkBreakdown without adding a new poll, and the client recomputes the same totals from per-repo breakdowns when the Overview repo filter is narrowed (src/pkg/dashboard/overview_status.go:105, src/pkg/dashboard/static/index.html:13103, src/pkg/dashboard/static/index.html:13138, src/pkg/dashboard/static/index.html:13168). The sub-line explains the gap (tracked in Overview bands, held, and outside reasons such as needs-direction, exempt, draft) and each card tooltip defines the count (src/pkg/dashboard/static/index.html:13148, src/pkg/dashboard/static/index.html:13179).

Tests / validation

• Added TestOverviewTotalsUseForgeCountsAndExplainScannerGap10629 for held, hard-suppressed, bot-authored, draft, and multi-repo fixture coverage.
• Added/updated static UI string-scan coverage to ensure the KPI binds to overviewTotals, uses forge fields, and has tooltips/sub-line wiring.
• Local validation limited to gofmt -l and git diff --check per AGENTS.md; no local go test, go build, go vet, or citation guard was run.

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign hanthor for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

Open PR overlap check

Base branch: v5

Conflicts are checked with every PR merged onto the current tip of v5, so a PR that only needs a rebase is not reported as conflicting with its siblings.

PR	Title	Relation	Files
#10658	🐛 dashboard: Overview median-age KPI names its population and basis	same files	src/pkg/dashboard/overview_kpi_sparklines_test.go src/pkg/dashboard/overview_kpi_values_10139_test.go src/pkg/dashboard/static/index.html
#10655	✨ Spek recheck cadence for continuous convergence	same files	src/docs/api-reference.md src/pkg/dashboard/static/index.html
#10602	✨ feat: label-driven repos skip un-park notice and keep needs-human	same files	src/docs/api-reference.md
#10614	✨ dashboard: Audit Log collapsed row shows entry rate, last entry, today's count and sensitive-action chip	same files	src/pkg/dashboard/static/index.html

[github-actions]

Thank you for your contribution! Your PR has been merged.

We'd love to hear how your experience was: share feedback