swarm ui: the issue report card is named "issues"

The reports tab holds cards, so a card named "issue report" repeats the word.
The card is now "issues", beside "pull requests", and the handbook says the
same.

docs/2-handbook/swarm/ui.md

@@ -30,7 +30,7 @@ smaller; short confirm dialogs stay short.
 | `/swarm`                                       | what belongs to the whole swarm: a folded **hives** card with the hive directory and each hive's last reported status, a folded **egress** card with the swarm-wide allowed and denied domains, and a folded, **beta** **notification router** card (with a warning banner) holding the router's flows: a switch for each built-in, every flow drawn as a graph, and an editor for custom flows. `/notifications` redirects here |
 | `/agents/<name>/terminal`                      | one agent's live terminal                                                                                                                                                                                                                                                                                                                                                                                                        |
 | `/agents/<name>/subagents/<subagent>/terminal` | one of that agent's subagents' live terminal                                                                                                                                                                                                                                                                                                                                                                                     |
-| `/reports`                                     | two folded cards, each read only once opened: the **alerts** the swarm's Grafana holds now, the firing ones, with a button for the pending, no-data and error ones and a link to Grafana's own alert list; read through the controller with a Viewer service-account token, and a cross-repo **issue report**                                                                                                                    |
+| `/reports`                                     | three folded cards, each read only once opened: the **alerts** the swarm's Grafana holds now, the firing ones, with a button for the pending, no-data and error ones and a link to Grafana's own alert list; read through the controller with a Viewer service-account token, and a cross-repo **issues** list, and a cross-repo **pull requests** list                                                                          |
 | `/jobs`                                        | the controller's job graph, where agent creation and credential mints show progress, and under it the swarm builder's recent builds (agent config PRs, and agents built from `internal/meta` before a deploy), with what nix printed when one failed, and the review classifier's recent runs, a try-out on a real PR, and its settings                                                                                          |
 | `/messages`                                    | the swarm-wide message feed: every message between agents, and to them from the operator, reminders and compaction, with a history window and a filter on sender or recipient; a folded **broadcast** card above the feed sends one message to more than one agent at once, and a folded **schedules** card holds the scheduled prompts: add, edit, pause, resume and remove                                                     |
 
@@ -569,11 +569,11 @@ live rows only.
 
 </details>
 
-### Issue report
+### Issues
 
 The card starts shut. The old `/issues` address redirects to the reports tab, as `/alerts` does.
 
-The **issue report** card on the **reports** tab lists the open issues of every repo that has one, from
+The **issues** card on the **reports** tab lists the open issues of every repo that has one, from
 `GET /api/issue-report`, or of one repo from
 `GET /api/repos/{org}/{repo}/issue-report`. Each row shows whether an open
 dependency blocks the issue and how many other issues depend on it. The
@@ -589,7 +589,7 @@ previous repo's issues under the error.
 
 ### Pull requests
 
-The **pull requests** card, below the issue report on the **reports** tab, lists the open
+The **pull requests** card, below the issues card on the **reports** tab, lists the open
 pull requests of every repo that has one, from `GET /api/pr-report`, or of one
 repo from `GET /api/repos/{org}/{repo}/pr-report`. It starts shut and reads
 nothing until you open it. The **repo** select lists the repos from

frontend/packages/swarm-ui/src/pages/IssueReportPage.tsx

@@ -392,10 +392,7 @@ function IssueReportBody() {
         />
       ) : null}
       {error ? (
-        <ApiErrorPanel
+        <ApiErrorPanel context="failed to load the issues" problem={error} />
-          context="failed to load the issue report"
-          problem={error}
-        />
       ) : null}
       {!error && loading ? <p>generating report…</p> : null}
       {!loading && rows ? (
@@ -416,7 +413,7 @@ function IssueReportBody() {
 export function IssueReportCard() {
   return (
     <LazyDisclosure
-      title="issue report"
+      title="issues"
       icon="📋"
       hint="open issues across every repo, ranked by what they block"
     >

frontend/packages/swarm-ui/src/pages/reports/ReportsPage.tsx

@@ -1,5 +1,5 @@
 // <ReportsPage> — `/reports`: what the swarm reports about itself, as folded
-// cards: the alerts Grafana holds now, mara's issue report and the PR report.
+// cards: the alerts Grafana holds now, the issues and the pull requests.
 // None reads anything until it is opened.
 import { AlertsCard } from "../AlertsPage.js";
 import { IssueReportCard } from "../IssueReportPage.js";