[zenith-root] chore: advance Lotus Next pointer for startup budgets

[bigduu]

Context

Lotus Next Issue bigduu/lotus-next#32 and PR bigduu/lotus-next#33 merged the
all-surface lazy Settings boundary and executable ordinary-chat startup budget
at e9675302854e6df35971f3f2d39816351b8184f5. Zenith main still pins
lotus-next at bb59f562214a5a20ae1efadd5c1641374411dcb0, so the reviewed
performance boundary and module/package ownership gate are not represented by
the monorepo manifest.

Acceptance slice

• start from current remote bigduu/Zenith main at
  27944d21b51b7fd658ec680951f87ed0cf66a504
• advance only the mode-160000 lotus-next gitlink:
  • old: bb59f562214a5a20ae1efadd5c1641374411dcb0
  • new: e9675302854e6df35971f3f2d39816351b8184f5
• record [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 provenance, exact-head
  review, Node 22/24 CI, bundle-budget evidence, and production browser evidence
  under the PR section named Submodule Updates
• require Submodule Guard success and an independent exact-head review before
  merge
• verify the remote main tree contains the intended Lotus Next commit after
  merge

Estimated effort: under 1 hour.

Non-goals

• no other submodule pointer, root configuration, release version, source, or
  documentation change
• no modification of the user primary checkout or its nested work
• no package publication, Bamboo/Bodhi consumer switch, or release-train change
  in this pointer-only slice

[bigduu]

🔒 claimed by Codex at 2026-09-03T02:24:00+08:00. Scope is one Lotus Next
gitlink from bb59f562214a5a20ae1efadd5c1641374411dcb0 to
e9675302854e6df35971f3f2d39816351b8184f5; no other root or submodule content
will change.

[bigduu]

✅ Completed and merged via #176.

• reviewed head: 6e180d42302bd3599678921bfef907134c879ea3
• merged commit: 14c8ed875ac751c6a0c29d01b2f989fef82045b3
• remote main now pins lotus-next at
  e9675302854e6df35971f3f2d39816351b8184f5
• both Submodule Guard checks passed on the exact reviewed head
• reviewed head tree and squash-merge tree match exactly