Document merge precedence; display lmm list in profile load order

[dyoung522]

Final pre-release polish (user-directed, 2026-08-02):

1. Document merged-pak precedence — nowhere in README/configuration.md: mods later in the profile load order are merged later and win conflicting row fields (per-field upsert); bundled assets are whole-file last-wins with a warning. The bottom of the load order has final say.
2. lmm list should display profile load order, not install order (ORDER BY installed_at today) — the visible order should be the order that decides merge precedence. Applies to all games (load order is a universal profile concept); mods missing from load_order append at the end.

🤖 Generated with Claude Code

[dyoung522]

Shipped in PR #202 (develop): merge precedence documented (later in load order = merged later = wins conflicting fields on shared rows; assets whole-file last-wins) in README/configuration.md/list help/man page, and lmm list now displays profile load order via core.OrderByProfile — the same never-omit seam the TUI and deploy already use — so the visible order IS the precedence order in both interfaces.