chore: advance Lotus Next send lifecycle pointer

[bigduu]

Summary

• advance only the lotus-next gitlink to the merged send-lifecycle fix from bigduu/lotus-next#35
• keep the Zenith wrapper aligned with canonical Lotus Next main

Submodule Updates

Submodule	Previous	New	Rationale
lotus-next	e9675302854e6df35971f3f2d39816351b8184f5	44cb3568805e834e3600ad9456c7fb424a3f3ea1	Includes the merged composer acknowledgement lifecycle fix from Lotus Next PR #35 / Issue #34.

The new commit is the live bigduu/lotus-next main head and descends from the previous gitlink.

Test Plan

• Lotus Next PR chore: bump nova pointer to ax_read #35: Node 22 and Node 24 checks passed
• Lotus Next final local verification: npm run verify passed (28 files / 742 tests), including type-check, strict lint, architecture boundary, production build, and package contents
• independent exact-head review of Lotus Next PR chore: bump nova pointer to ax_read #35 found no P0/P1/P2 blockers
• root diff contains exactly one mode-160000 gitlink update

[bigduu]

Independent exact-head review completed for 1454340e287708ff48be0e42fe0349f1e6357381 with 0 findings / 0 blockers.

• Base is the live Zenith main at 14c8ed875ac751c6a0c29d01b2f989fef82045b3; the PR head has that exact single parent.
• Remote diff changes only the mode-160000 lotus-next gitlink: e9675302854e6df35971f3f2d39816351b8184f5 → 44cb3568805e834e3600ad9456c7fb424a3f3ea1.
• The new SHA is the live bigduu/lotus-next main, is one commit ahead of the old pointer, and is the merge commit for Lotus Next PR chore: bump nova pointer to ax_read #35.
• Excluding lotus-next, the base and head top-level trees are identical.
• The PR body contains the required ## Submodule Updates section with exact SHAs and rationale.
• Submodule Guard Validate Submodule Pointers and Require Submodule Notes (PR) both passed; merge state was MERGEABLE / CLEAN with 0 unresolved review threads.