[Upstream PR #212] Satisfy latest CI guardrails

[quangdang46]

Mirrored from upstream 1jehuang/jcode — Pull Request #212 by @1jehuang
Original state: open
Created: 2026-05-14T10:28:05Z · Updated: 2026-05-14T11:15:20Z
Diff: https://github.com/1jehuang/jcode/pull/212.diff
This issue is an auto-mirrored copy. Comments and edits here are local to quangdang46/jcode — do not expect them to propagate upstream.

---

This PR was originally used for issue #201 validation, but the Windows browser setup fixes are now already on master:

• d4fda75 Require Firefox bridge host asset during setup
• a68185c Use file URLs for browser extension install
• 719b4a5 Always refresh Windows native host registry
• 95db8ae Repair browser setup when native host is missing

After rebasing on current master, this PR only carries unrelated CI guardrail cleanup for newer rustfmt/clippy behavior. It is no longer required to close #201.

[quangdang46]

Already implemented in this fork. The four match-arm-guard / checked_div refactors that upstream PR #212 applies are already in place locally:

• crates/jcode-compaction-core/src/lib.rs:219 — match arm uses if X => { ... } form.
• crates/jcode-compaction-core/src/lib.rs:220 — same.
• crates/jcode-import-core/src/lib.rs:362, :790 — serde_json::Value::String(text) if !text.trim().is_empty() => { ... }.
• crates/jcode-tui-mermaid/src/mermaid_viewport.rs:89 — div_ceil_u32_local already uses saturating_add(divisor.saturating_sub(1)).checked_div(divisor).

Closing as already implemented.

[quangdang46]

Verified — fork's CI already passes its own guardrails. scripts/check_warning_budget.sh + clippy -D warnings + warning budgets all run clean against current master. Upstream PR #212's specific changes were target-warning thresholds that don't apply 1:1 to our state. Closing.