chore: advance Lotus Next startup budget pointer

[bigduu]

Summary

• advance only the lotus-next gitlink to the merged startup-budget slice
• preserve every other Zenith submodule pointer and root file unchanged

Closes #175

Submodule Updates

• lotus-next
  • old: bb59f562214a5a20ae1efadd5c1641374411dcb0
  • new: e9675302854e6df35971f3f2d39816351b8184f5
  • provenance: [lotus-next] perf: lazy-load settings and enforce ordinary-chat startup budgets lotus-next#32 and perf: lazy-load settings and enforce startup budgets lotus-next#33
  • reviewed PR head: 0bdfdb700747a4f20f1cade664111ef9cab95186
  • rationale: adopt the all-surface lazy Settings boundary, remove the eager
    catch-all vendor graph, and enforce executable ordinary-chat startup
    module/package ownership and size budgets
  • acceptance evidence: Node 22 and Node 24 checks passed; 23 test files / 708
    tests passed; immediate JS is 992,616 B raw / 301,093 B deterministic gzip;
    desktop, phone, and localized Settings chunk failure production checks
    passed

The squash-merge tree for e9675302854e6df35971f3f2d39816351b8184f5
matches the independently reviewed head tree exactly.

Test Plan

• confirm git diff --raw origin/main...HEAD contains exactly one mode-160000
  lotus-next change
• confirm git ls-tree HEAD lotus-next resolves exactly to
  e9675302854e6df35971f3f2d39816351b8184f5
• require the protected Submodule Guard check to pass
• require an independent exact-head review before merge