Update ICM426xx IMUs filtering settings information

[LoyalLinjy]

Clarified filtering settings for ICM426xx IMUs and recalibration notes.

[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.

[github-actions]

🤖 Kimi Code Review Report

中文审查报告

变更总结:
删除 .github/workflows/kimi-pr-review.yml，即移除基于 Moonshot Kimi API 的 PR 自动代码审查工作流。该工作流通过手动触发，拉取指定 PR 的 diff，调用 Kimi 模型生成双语审查报告，并以评论形式发布到 PR。

问题与建议:

1. 密钥明文日志风险：
   第 32 行 echo "Key prefix: ${KIMI_API_KEY:0:15}..." 会把密钥前 15 字符打印到 GitHub Actions 日志，一旦日志公开，攻击者可利用前缀进行字典/暴力破解，或与其他泄露片段拼接还原完整密钥。
   建议：删除或屏蔽该输出，改用 *** 占位。

2. 异常处理不足：

   • 第 38 行测试 API 连通性时，未判断返回 JSON 是否包含 "error" 字段，可能误把错误响应当成成功。
   • 第 45 行 git fetch 若失败（如 PR 号不存在），脚本继续执行，导致后续 git diff 比较的是空分支，浪费额度。
     建议：增加 set -euo pipefail，并对关键命令做显式判断。

3. diff 截断导致上下文丢失：
   第 46 行 head -c 4000 硬性截断，大 PR 会被截断，模型只能看到片段，审查结论不完整。
   建议：按行数或结构化 diff 统计（如最大 200 文件、3000 行）并给出提示，而非直接截断字节。

4. 模型参数与提示词耦合：
   固定使用 kimi-k2-turbo-preview，若模型下线或更名，工作流失效；提示词硬编码在 Python 脚本里，后续维护困难。
   建议：提取为环境变量或仓库配置文件，方便热更新。

5. 评论长度未控制：
   第 118 行直接提取完整回复，若 Kimi 返回超长内容（>65536 字符），GitHub REST API 会报错。
   建议：增加长度检查，必要时拆分多条评论。

6. 删除合理性：
   如果团队决定不再使用 Kimi，或已迁移到更稳定的审查方案（如 GitHub Copilot、CodeQL、自定义规则），删除是合理的；否则建议保留并修复上述问题。

代码评分: 2.5/5
（功能完整但存在日志泄露、异常处理弱、diff 截断草率等明显缺陷）

---

English Review Report

Summary:
The entire .github/workflows/kimi-pr-review.yml workflow is removed. It used to let maintainers manually trigger a review of any PR by number, fetch its diff, send it to the Moonshot Kimi chat-completion API, and post the bilingual response back as a PR comment.

Issues & Suggestions:

1. Secret leakage in logs:
   Line 32 prints the first 15 chars of KIMI_API_KEY. GitHub Actions logs can be exposed, giving attackers a head-start for brute-forcing or correlating with other breaches.
   Fix: Redact the echo or replace the value with ***.

2. Weak error handling:

   • The connectivity test (line 38) only checks that curl succeeds, not that the returned JSON is error-free.
   • git fetch for a non-existent PR number will fail silently because the script lacks set -e; downstream steps then run against an empty working tree.
     Fix: Add set -euo pipefail and verify each critical step.

3. Hard byte-limit on diff:
   head -c 4000 (line 46) crops large PRs mid-line, depriving the model of context and producing unreliable reviews.
   Fix: Limit by line count or number of files and warn when truncation happens.

4. Tight coupling of model & prompt:
   Model name and review prompt are embedded inside the shell heredoc; any change requires a commit.
   Fix: Move them to environment variables or a config file.

5. Comment size overflow:
   The full response is posted unchecked; GitHub caps comments at ~64 kB.
   Fix: Truncate or split the message if it exceeds the limit.

6. Justification for deletion:
   If the team has switched to another review automation (e.g., GitHub Copilot, OpenAI, or in-house rules) deleting the workflow cleans up the repo. Otherwise, keep it and address the above flaws.

Rating: 2.5/5 stars
(Functional but hampered by logging risks, poor resilience, and crude diff truncation)

---

Generated by Kimi AI

[github-actions]

🤖 Kimi Code Review Report

中文审查报告

变更总结:
该 diff 删除了整个 .github/workflows/kimi-pr-review.yml 文件，意味着项目不再使用基于 Kimi（Moonshot）大模型的 PR 自动审查能力。删除后，PR 将失去由 Kimi 生成的双语代码审查报告。

问题与建议:

1. 可维护性：工作流脚本较长且混合 Bash/Python，调试困难；若未来仍需类似能力，建议拆分成独立脚本并加单元测试。
2. 安全性：原脚本用 head -c 4000 截断 diff，可能遗漏关键变更；若重新启用，应改用 GitHub REST/GraphQL 接口获取完整 diff。
3. 成本与可靠性：依赖外部大模型 API，存在配额、延迟、失效风险；删除前未评估替代方案（如 GitHub Copilot、本地模型）。
4. 审计缺失：删除工作流未在 PR 描述中说明理由，建议补充“为什么不再需要”以及“后续计划”。

代码评分: 2/5（删除本身无代码质量问题，但缺乏迁移/替代说明）

---

English Review Report

Summary:
The entire kimi-pr-review.yml workflow is removed, disabling automated bilingual PR reviews powered by the Kimi large-language model.

Issues & Suggestions:

1. Maintainability: The single-file workflow mixed Bash & Python without tests; if re-implemented, extract scripts and add CI tests.
2. Security: Truncating diff with head -c 4000 could hide important changes; prefer GitHub’s official diff endpoint for completeness.
3. Cost & Reliability: External LLM dependency introduces quota, latency, and availability risks; no fallback or replacement was documented.
4. Audit Trail: PR lacks justification for removal; include rationale and any successor plan (e.g., GitHub Copilot, local model, or manual review).

Rating: 2/5 stars (deletion is clean, but missing migration context)

---

Generated by Kimi AI

[github-actions]

🤖 Kimi Code Review Report

中文审查报告

变更总结:
仅对 readme.md 中的一行警告文本做了格式调整，将“ICM426xx”拆成了“ICM426 xx”，并在前面插入了多余空格。

问题与建议:

1. 拆分产品型号会导致读者困惑，官方文档应保持型号连续（ICM426xx）。
2. 行首新增的无用空格破坏了 Markdown 排版一致性，可能被渲染为代码块或导致后续自动化脚本解析失败。
3. 此次改动无功能或语义收益，属于无效变更，建议直接回滚。

代码评分: 1/5

---

English Review Report

Summary:
A single formatting tweak in readme.md: the word “ICM426xx” was split into “ICM426 xx” and extra leading spaces were added.

Issues & Suggestions:

1. Breaking the part number “ICM426xx” confuses readers; keep it contiguous as per vendor datasheet.
2. The stray leading spaces violate Markdown consistency and may break parsers or render as a code block.
3. The change brings zero functional or semantic value; recommend reverting.

Rating: 1/5 stars

---

Generated by Kimi AI