chore: bump lotus-next for all-surface E2E

[bigduu]

Summary

• advance only the lotus-next gitlink to the merge of Lotus Next PR chore: sync Bamboo and Lotus submodule pointers #38
• carry the all-surface browser acceptance foundation and portable nested-mount artifact fix into the canonical Zenith snapshot
• leave Bamboo, legacy Lotus, Bodhi, Pavilion, Bodhi Server, Jiandu, Nova, and Magpie pointers unchanged

Submodule Updates

Submodule	Previous SHA	New SHA	Rationale
lotus-next	44cb3568805e834e3600ad9456c7fb424a3f3ea1	4fa46103d6e323f030cbaaa6c9e48a5e0467c446	Lotus Next PR #38 / Issue #36: desktop, tablet, and phone browser gates for standalone, secure remote, and nested embedded hosting, plus relative production asset paths.

Test Plan

• git diff --check origin/main...HEAD
• verify git diff --name-status origin/main...HEAD contains only lotus-next
• verify git ls-tree HEAD lotus-next is mode 160000 at 4fa46103d6e323f030cbaaa6c9e48a5e0467c446
• verify bigduu/lotus-next main resolves to the same new SHA
• source PR chore: sync Bamboo and Lotus submodule pointers #38 passed exact-head independent review and Node 22/24 CI

Screenshots

Not applicable; this PR updates one submodule pointer and contains no root-level visual change.

[bigduu]

Independent agent review completed against exact head 77edbb8e39b9f612c09b261433382d33b593551b: no blocking findings. The diff contains only the lotus-next mode-160000 gitlink, advances directly from 44cb3568805e834e3600ad9456c7fb424a3f3ea1 to the merged source SHA 4fa46103d6e323f030cbaaa6c9e48a5e0467c446, and both Submodule Guard checks pass.