| name | report |
| description | Build the monthly Thunderbird support report. Usage: /report <month> <year> (e.g. /report may 2026) |
Monthly Support Report — $month $year
Run the full report cycle for $month $year. Follow every step in order.
Step 1 — Re-fetch all live data sources
Do NOT use YAML values from a prior session. Always fetch fresh.
FeatureOS ideas (board 17437):
featureos-cli posts list --query "sort=votes_count&order=desc&per_page=25&status=all" --json
Update both new_this_month and top_alltime in data/$month_$year.yaml.
new_this_month: cross-reference with Lisa's FeatureOS board filtered by creation date for this month
top_alltime: top 5 by votes_count from CLI output
- JSON key is
feature_requests, not posts
- Ideas can be removed from the board between sessions — verify all entries still exist
SUMO data (Roland's reports):
- Desktop:
https://thunderbird.github.io/thunderbird-metrics-and-reports/html_reports/desktop/$year-$month_num-sumo-desktop-report.html
- Android:
https://thunderbird.github.io/thunderbird-metrics-and-reports/html_reports/android/$year-$month_num-sumo-android-report.html
- Fetch both pages and update
sumo: section in the YAML
Step 2 — Confirm Play Store CSVs are in place
Required files in project root or data/input/:
reviews_reviews_net.thunderbird.android_$year$month_num.csv
reviews_reviews_com.fsck.k9_$year$month_num.csv