Merge Maintenance 9.x to master

[sensei-hacker]

PR Type

Enhancement, Documentation

---

Description

• Add MSP2_INAV_SET_GVAR command for global variable control

• Update MSP protocol documentation with new GVAR message

• Add comprehensive release creation guide for maintainers

• Fix documentation links and enum references

---

Diagram Walkthrough

flowchart LR
  A["MSP Protocol"] -->|"Add SET_GVAR"| B["fc_msp.c"]
  A -->|"Define 0x2214"| C["msp_protocol_v2_inav.h"]
  D["MSP Documentation"] -->|"Update messages"| E["msp_messages.json"]
  D -->|"Update reference"| F["msp_ref.md"]
  G["Developer Docs"] -->|"Add release guide"| H["release-create.md"]
  I["Maintenance"] -->|"Fix links/enums"| J["LedStrip.md & inav_enums_ref.md"]

Loading

File Walkthrough

	Relevant files
Enhancement	2 files fc_msp.c Implement MSP2_INAV_SET_GVAR command handler                          +17/-0    msp_protocol_v2_inav.h Define MSP2_INAV_SET_GVAR protocol constant                            +2/-1
Documentation	6 files msp_messages.json Document MSP2_INAV_SET_GVAR message structure                        +23/-0    msp_ref.md Add MSP2_INAV_SET_GVAR to protocol reference                          +16/-1    rev Increment MSP documentation revision number                            +1/-1      inav_enums_ref.md Fix enum names and add wind offset operand                              +4/-3      release-create.md Add comprehensive INAV release creation guide                        +345/-0  LedStrip.md Update Oscar Liang guide link to current URL                          +2/-2
Miscellaneous	1 files msp_messages.checksum Update checksum for MSP messages                                                  +1/-1

---

[github-actions]

Branch Targeting Suggestion

You've targeted the master branch with this PR. Please consider if a version branch might be more appropriate:

• maintenance-9.x - If your change is backward-compatible and won't create compatibility issues between INAV firmware and Configurator 9.x versions. This will allow your PR to be included in the next 9.x release.

• maintenance-10.x - If your change introduces compatibility requirements between firmware and configurator that would break 9.x compatibility. This is for PRs which will be included in INAV 10.x

If master is the correct target for this change, no action is needed.

---

This is an automated suggestion to help route contributions to the appropriate branch.

[qodo-code-review]

PR Compliance Guide 🔍

All compliance sections have been disabled in the configurations.

[qodo-code-review]

Suggestion: Verify the new MSP ID is consistently defined and documented everywhere (header, handler switch, JSON/docs) to keep one source of truth. Ensure the numeric value (0x2214/8724) matches the docs and header constant. [Learned best practice, importance: 6]

Suggested change

	case MSP2_INAV_SET_GVAR:
	if (dataSize != 5) {
	return MSP_RESULT_ERROR;
	}
	{
	uint8_t gvarIndex;
	if (!sbufReadU8Safe(&gvarIndex, src)) {
	return MSP_RESULT_ERROR;
	}
	const int32_t gvarValue = (int32_t)sbufReadU32(src);
	if (gvarIndex >= MAX_GLOBAL_VARIABLES) {
	return MSP_RESULT_ERROR;
	}
	gvSet(gvarIndex, gvarValue);
	}
	break;
	case MSP2_INAV_SET_GVAR: // 0x2214 (8724), must match msp_protocol_v2_inav.h and docs
	if (dataSize != 5) {
	return MSP_RESULT_ERROR;
	}
	uint8_t gvarIndex;
	if (!sbufReadU8Safe(&gvarIndex, src)) {
	return MSP_RESULT_ERROR;
	}
	const int32_t gvarValue = (int32_t)sbufReadU32(src);
	if (gvarIndex >= MAX_GLOBAL_VARIABLES) {
	return MSP_RESULT_ERROR;
	}
	gvSet(gvarIndex, gvarValue);
	break;

[sensei-hacker]

Does this suggestion change any code, or just add a comment without any other changes?

[qodo-code-review]

Ask❓

Does this suggestion change any code, or just add a comment without any other changes?

Answer:

It only adds an inline comment/annotation next to the case label and does not alter the actual code logic or behavior.