Proposal: Add human-readable fix hints for arming disable flags

[cskgcskg]

BODY:

The problem

"Why won't my quad arm?" is probably the most common support question across Discord, Reddit, and YouTube. The current system shows flag names like RPMFILTER, DSHOT_BBANG, or NOT_DISARMED on the OSD and in CLI status — these are meaningful to experienced developers but confusing for most pilots.

There are 29 arming disable flags. Each one requires different knowledge to resolve. A beginner seeing DSHOT_TELEM has no idea this means their ESC firmware needs to support bidirectional DShot. Someone seeing BOOTGRACE doesn't know it will go away on its own in a few seconds.

Proposed solution

Add a parallel string array in runtime_config.c with a short, plain-English fix instruction for each flag. For example:

Current flag name	Proposed fix hint
THROTTLE	Lower throttle to minimum
RPMFILTER	ESC RPM telemetry missing. Check ESC
CALIB	Calibrating. Hold still...
BOOTGRACE	Wait a few seconds after power on
MOTOR_PROTO	Select motor protocol in Config tab
MSP	Disconnect configurator to arm

Plus a getArmingDisableFixHint() getter function, mirroring the existing getArmingDisableFlagName().

Scope

This would be a small, contained change — two files (runtime_config.c and .h), roughly 40 lines added. It only adds the data and getter. It does not change what the OSD or CLI currently displays. Wiring the hints into OSD warnings, CLI status output, or MSP for the configurator could be done in separate follow-up PRs.

Implementation

I'm not a core C developer — I'd be implementing this with AI assistance (Claude). I've already worked through the approach and have the code drafted, so if the team is open to this I can have a PR ready. Of course happy to adjust anything based on your feedback.

Concerns I've thought about

• Flash size on F411: The hint strings would add ~1KB. Happy to wrap them in #ifndef MINIMAL_CLI or a similar guard for memory-constrained targets.
• String length for OSD: All hints are kept short enough to fit within OSD_WARNINGS_MAX_SIZE.
• Maintenance: A STATIC_ASSERT would enforce that the hints array stays in sync with the flags enum.

Questions for the team

1. Is this something you'd be open to merging?
2. Any preferred approach for handling flash-constrained targets?
3. Should I also update CLI status to print hints alongside flags in the same PR, or keep that separate?

Would love to hear your thoughts before I submit anything. Thanks for all the work you do on Betaflight.

[VitroidFPV]

This would not work on analog OSD very well, the maximum grid width is 30 characters. Many of your suggested strings already go well over that count. It would require extra text wrapping logic and a lot of room to work.

There's already a lookup table on the wiki, perhaps we could improve that instead?