fix(rules): make list order the single source of priority

[jackerjay]

Why

LinkPilot was carrying two competing notions of "priority":

1. A numeric Rule.priority: i32 field.
2. The position of each rule inside config.rules.

They drifted apart in practice — the GUI editor stamped 100 on every new rule, the CLI defaulted to 10, the demo config used 10, and drag-to-reorder restamped (N - idx) * 10. So a user with a source-app = Lark → Ask rule and a url-host = github.com → Open Chrome rule could easily end up with both at the same numeric priority. The stable sort then silently favored whichever rule was added first; the picker for Ask did pop but the user, expecting github.com → Chrome to dispatch directly, read it as "nothing happened — priority isn't working."

User report (translated): "当我的 rules 存在冲突的时候,例如我配置了 lark 打开使用 ask,同时配置了 github.com 默认走 Chrome,此时我在 lark 中点击 github 相关的域名不会有任何的浏览器跳转反应... 而且不能出现重复的优先级,应该按照列表排序的方式来规定优先级".

What

Collapse the two sources into one: list order in config.rules IS priority. Top of list wins. Duplicates are now structurally impossible.

Core (crates/core/)

• Drop Rule.priority from the schema.
• Router::evaluate_explained walks config.rules top-to-bottom and returns the first matching enabled rule — no sort.
• One-shot migration in ConfigStore::load_or_init: if a pre-v0.2 config still has priority fields on rules, stable-sort by priority descending (preserving user intent), strip the field, and persist atomically. The fsnotify external-edit path runs the same migration so hand-edited legacy configs still work.

CLI (crates/cli/)

• rules add drops --priority; new rules append at the bottom (safe default — won't silently override existing ones).
• set-priority removed; replaced by rules move <id> <top|up|down|bottom>.
• rules list renders 1-based slot numbers instead of a priority column.

Frontend (apps/desktop/src/)

• RuleEditor removes the Priority input and explains that priority is now set by list order on the Rules page.
• pages/rules.tsx drops the sort + restamp; drag-reorder is a pure list rewrite. The leading #N badge is now the rule's 1-based global slot.
• pages/inspector.tsx, pages/test-url.tsx, pages/workspace.tsx: same — show the slot, not a numeric priority.
• OnboardingFlow prepends toggled templates in their declared order so the first template lands at slot chore(deps): bump softprops/action-gh-release from 2 to 3 #1.

DSL (packages/config-dsl/)

• .priority(p) builder removed; RuleJson.priority removed from the wire shape.
• compile() documents that cfg.rules order is authoritative.

Tests

• New regression routing::tests::first_match_in_list_order_wins — reproduces the user's exact scenario (Lark/Ask + github/Chrome) and asserts that swapping the list positions flips the winning decision.
• New migration test config::store::tests::migrates_legacy_priority_to_list_order — writes a legacy JSON with "priority": 10 and "priority": 100 rules in the wrong order, loads it, verifies the prio-100 rule moves to slot 1 and that the priority key is gone from disk after persistence.
• New DSL test rule array order is preserved (list-order priority) plus an updated RouteBuilder modifiers stick that asserts no priority field is emitted.

Local verification

• cargo test -p linkpilot-core — 32 passed (incl. the two new tests above)
• cargo test -p linkpilot-cli — 7 passed
• cargo check --workspace incl. linkpilot-desktop — clean
• cargo clippy --workspace — no new warnings (only pre-existing tray.rs needless_borrows)
• npm run build in apps/desktop (tsc + vite) — clean
• bun test in packages/config-dsl — 13 passed
• npm run bundle:mac — produces LinkPilot.app + LinkPilot_0.2.0_aarch64.dmg; Info.plist patch applies cleanly

Backwards compatibility

The Rule struct doesn't use serde(deny_unknown_fields), so existing configs that still carry priority deserialize without error. The migration runs on the next load — sorts by priority desc (stable), drops the field, persists once. Idempotent: subsequent loads see no priority and skip migration. User-authored priority intent is preserved.

Test plan

• First launch on an existing install: confirm linkpilot.config.json no longer contains "priority": after the daemon boots once.
• Repro user's case: configure source-app = Lark → Ask and url-host = github.com → Open Chrome; drag the github rule to the top in the Rules page; click a github link inside Lark → opens directly in Chrome with no picker.
• Drag the lark rule above github → same click → picker appears.
• lpt rules list prints rules in list order with #N slots.
• lpt rules move <github-id> top raises that rule to slot 1.
• Onboarding: toggle two templates → both land at the top in declared order.

🤖 Generated with Claude Code