"What do the logs say?" β this is how you answer that question in three steps, without hunting through folders.
Anything you cannot explain from the screen: audio that stutters, a panel that stops updating, a radio that will not connect, an upgrade that did nothing, a page whose buttons went dead.
A report without evidence turns into a guessing game. The bundle exists so that the first answer is a verdict, not a question.
| # | What you do | Why it matters |
|---|---|---|
| 1 | Open π Something went wrong and describe the symptom β what happens, when it started, radio model and frequency | "Audio stutters about once a second since I moved to the Windows box" is answerable; "it does not work" is not |
| 2 | Press Build bundle | Collects logs, a redacted config, an environment snapshot and runs the health checks |
| 3 | Press Upload to maintainer β or Save locally | Upload only happens when you click it |
The page requires you to be logged into the local MRRC UI; without a session it answers 401/403.
The user database, certificate private keys, session secrets, passwords and tokens. None of them are packaged, redacted or not.
Firewall, no route to the receiver, or a machine that never reaches the internet: choose Save locally, then hand the file over by whatever channel you already use.
The bundle is a plain file; uploading early just saves you a step.
Thin evidence produces need_more_info, never a guess β which is exactly why the health summary is part of the bundle.