Add rewrite-kernel-config command to Build commands

[HeyMeco]

Added 'rewrite-kernel-config' command to validate kernel config changes and ensure persistence in CI.

Documentation website preview will be available shortly:

 Open WWW preview 

[coderabbitai]

Walkthrough

This PR adds documentation for a new rewrite-kernel-config build command in the Developer Guide. The section explains that the command automatically validates kernel config changes and their dependency chains, is intended to run after manually editing configs for a specific family or branch to ensure CI persistence, and includes the corresponding usage example: ./compile.sh rewrite-kernel-config BOARD=xxxxx BRANCH=current.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: adding documentation for the rewrite-kernel-config command to the Build commands guide.
Description check	✅ Passed	The description is directly related to the changeset, explaining the purpose of the new rewrite-kernel-config command being documented.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch rewrite-kernel-config

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/Developer-Guide_Build-Commands.md`:
- Around line 23-27: Update the paragraph so the phrase "persist our CI" reads
"pass our CI", and fix the fenced code block spacing by ensuring there is a
blank line before the opening ```bash fence and a blank line after the closing
``` fence; keep the command text exactly as shown ("./compile.sh
rewrite-kernel-config BOARD=xxxxx BRANCH=current") and ensure the
triple-backtick fences are properly separated from surrounding text to avoid
MD031.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e8c780e8-6d1d-4ab8-a516-497422b0deeb

📥 Commits

Reviewing files that changed from the base of the PR and between 2365684 and 355e93a.

📒 Files selected for processing (1)

• docs/Developer-Guide_Build-Commands.md

[HeyMeco]

Preview looks good: https://github.armbian.com/documentation/922/Developer-Guide_Build-Commands/