Data engagement: reporting links, group stats, Fixometer fixes (#919)

[edwh]

Implements the code changes for #919 (sub-issues #920–#925). The Metabase reports and dashboards live outside this repo. Each sub-issue has a write-up with screenshots.

What changes

Reporting links — #920, #921

• Networks have a reporting dashboard address (networks.reporting_url, new migration). Only administrators can set it, on the network edit page. When it's set, the network page links to it in two places: Network actions → View reports, and a "See more in your network's reports" link under the impact figures.
• Groups link to the group reporting dashboard, filtered to that group. The links are in Group actions → View reports and under the group stats.
  • There's one dashboard per language: GROUP_REPORTING_URL_EN and GROUP_REPORTING_URL_FR.
  • A group uses the default language of its network. A regional language such as fr-BE uses its base language. Anything else falls back to English.
  • {group} and {group_name} in the address are filled in.
  • Group members and the people who look after the group see the link. Without a dashboard address there's no link.

Group page stats — #922

• Device breakdown is removed, along with the queries that fed it. Most repaired devices is renamed Most repaired items, here and on the admin stats page. It now includes unpowered categories, leaving out both "None of the above" ones.
• Three layouts are on the page for Neil and James to compare. ?stats_layout=compact (the default), after or split picks one. The other two, and the option, go once one is chosen.

Fixometer headline stats — #923

• Powered/unpowered items fixed and years of time volunteered have their new labels.
• New events held figure: past events that weren't cancelled, in approved groups.
• New items seen figure: every item recorded.
• "See more analysis in our further reports." links to FIXOMETER_REPORTING_URL. It doesn't appear when that isn't set.
• The homepage stats cache key is now homepage_data_v3, so the new figures appear straight after deploy.

Fixometer repair records — #924

• One list. Powered and unpowered records are in one list. Before, they were in separate tabs. A Powered or unpowered select (Both, Powered, Unpowered) filters it. The item entry on event pages keeps its tabs.
• Filters. The order is Powered or unpowered, Category, Item ("What is it?"), Brand, Model, Assessment, Repair status. Brand and Model show for every type of item. The 'i' icons are gone from the filters and from expanded records, but stay on data entry.
• Fixes. Sorting uses the column clicked. The status filter works. The To date includes that day and now defaults to today. Deleted events are left out. Expanding a record shows its details.
• Table. The date is the event date and links to that event's items. Status comes before Group. The list is white again, without the how-to text.
• Old ?category_powered= / ?category_unpowered= links still work.

Repair data download — #925

• Download all data is shown to everyone.
• export:repair-data builds the full file at public/exports/repair-data.csv, holding what anyone can see. The web server sends it directly, as compressed CSV, without going through PHP.
• The command runs hourly, but rebuilds at most once a day, and only when repairs, events or groups have changed. A new server gets the file within the hour; until then, the button uses the live export.
• The CSV writing moved into App\Services\RepairDataExport, which the per-event and per-group exports share. The query applies User::userCanSeeEvent()'s visibility rules and works in chunks.

Screenshots

Fixometer (#923, #924)

Group page, compact layout (#921, #922). The other layouts are on #922.

Network impact with the reports link (#920)

Tests

• PHPUnit: reporting links (per language, fallbacks, group name), events held and items seen, most repaired items, the repair records API, and the export file (what's in it, the once-a-day rule, skipping when nothing changed, the Fixometer button).
• Jest: the Fixometer filters, records table and headline; group stats layouts; network page link.
• Checked on the preview with production data: the export built in 44 seconds (40 MB), and it's served as compressed CSV.

For the code review

• /api/devices without powered returns both powered and unpowered records. Before, it returned unpowered only. The Vue client is the only known caller.
• Production needs GROUP_REPORTING_URL_EN (and later _FR) and FIXOMETER_REPORTING_URL set for those links to appear.
• GROUP_REPORTING_URL is no longer read. It isn't set in production (checked the Fly secrets).

[ngm]

@edwh That's great, thanks - but can we move the discussion about each of the items to the related sub-issue?

[edwh]

@ngm Done - each sub-issue now has a comment with what this PR does for it, its screenshots, and the points to discuss: #920, #921, #922, #923, #924, #925. The PR description now just points to them.

There's also a preview of this PR on production data at https://restarters-pr-926.fly.dev (it's being deployed now), which is the place to try the repair records list and time the full download (#925).

[github-actions]

Preview: https://restarters-pr-926.fly.dev

✅ Ready - restore and migrations succeeded.

• Password-protected test environment (usual dev gate password); commit f68ad0ed62d28b33be0e09cd70f3f975c7031101 merged with develop.
• If you see a "warming up" page, give it a few minutes - it refreshes itself.
• The preview database is refreshed on every deploy and may reset at any time; anything you create here is disposable.
• Emails go to shared Mailpit, never to real recipients. Image uploads are disabled.
• The app suspends when idle; the first request after a pause can take a moment.

[sonarqubecloud]

Quality Gate passed

Issues
7 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.7% Duplication on New Code

See analysis details on SonarQube Cloud