Add "Yes, Always" option to upgrade reporting prompt

[Copilot]

The upgrade prompt's "one-time" language was discouraging users from reporting on subsequent upgrades, preventing tracking of version adoption rates and upgrade vs. install differentiation.

Changes

• Added 4th prompt option: "Yes, Always" enables automatic reporting on future upgrades without re-prompting
• Removed "one-time" language: Changed prompt text to focus on ongoing value proposition rather than single-event framing
• Added alwaysReport flag: Extended version-info.json structure to persist user's always-report preference
• Implemented auto-reporting: When alwaysReport: true, subsequent version changes report automatically without showing prompt

Implementation

When user clicks "Yes, Always":

1. Current upgrade is reported immediately
2. alwaysReport: true saved to version-info.json alongside existing neverAsk and version fields
3. Future version changes detected → automatic reporting bypasses prompt
4. Confirmation toast: "Thank you! Future upgrades will be reported automatically."

// Existing prompt had 3 options, now has 4
dialog.innerHTML = `
  <div style="display:flex;flex-wrap:wrap;gap:8px;">
    <button id="versionReportYes">Yes</button>
    <button id="versionReportAlways">Yes, Always</button>  <!-- NEW -->
    <button id="versionReportNo">Not Now</button>
    <button id="versionReportNever">Never Ask</button>
  </div>
`;

Screenshots

Upgrade prompt:

Install prompt:

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Upgrade prompt too "noisy"</issue_title>
<issue_description>The new prompt after an install or upgrade talks about "one time action", which was meant to convey this is not on-going monitoring/tracking, but that's possibly a little too literal at the moment.

We are seeing a much lower conversation rate between the download stats and the reporting of install/download which implies users were ok for the initial report, but possibly now saying "never again" for the upgrade.

This gives us a few issues, one is that we can't differentiate downloads for installs Vs upgrades, we won't actually know what % are on the latest release - meaning we don't know how many people are holding off upgrade due to anxiety about stability, had to downgrade due to bugs etc.

Also, during first install we don't know how many LEDs or if users are using a 2D matrix, only when they next upgrade version (as there is no ongoing monitoring)

---

Should we swap the prompt to allow automatic reporting of your next upgrade, or would 4 prompts be too many (yes, yes always, skip, never)

If we do add option for yes - always, how best to word the privacy policy to cover this use case; not all the time, just on later upgrades but without prompting </issue_description>

<agent_instructions>Please implement opinion 2</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@netmindz What are your thoughts @coderabbitai @netmindz What are your thoughts @copilot

• Fixes Upgrade prompt too "noisy" #5164

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}