[zenith-root] chore: pin merged Lotus Next actor UI source

[bigduu]

Acceptance slice

Advance only Zenith's lotus-next mode-160000 gitlink from the current remote main pointer e8d7e7f5f3807393093da0f06b5af40a1acac22d to Lotus Next's merged main commit cdc226031079063b517fbf862037f7dac4aaad83. This makes the merged Lotus Next actor UI source chain available in the Zenith wrapper. It is source synchronization, not runtime or release acceptance.

Acceptance criteria

• Start from a freshly fetched Zenith origin/main in an isolated worktree; preserve the divergent primary checkout and all nested worktrees.
• Confirm the target commit is the exact Lotus Next remote main and that the old pointer is its ancestor.
• Change exactly one path, lotus-next, as a 160000 gitlink; verify the old and new SHAs with git ls-tree, git diff --raw, and git diff --name-only.
• Run git diff --check; publish one focused PR to Zenith main with ## Submodule Updates containing both SHAs and the source-only rationale. Pass both Submodule Guard checks on the exact PR head before merge.
• Complete local source review; do not request GitHub PR review.

Scope and estimate

One Zenith root gitlink; approximately 4 hours including source identity verification, local review, and protected PR checks. Related Lotus Next source Issues: bigduu/lotus-next#194, #195, #196, #197, #199, #198, #202, #201. Bamboo orchestration tracker: bigduu/Bamboo-agent#791.

Non-goals

No release artifact publication or adoption, release-train configuration change, Bamboo/Bodhi pointer movement, claim that partial Lotus UI Issues are complete, or live authenticated Bamboo acceptance. The current release configuration still locks @bigduu/lotus-next@2026.9.22 to source a480e2bb94f5dd08fe4b01b2f8844a2c9ed03245; this PR does not change that identity or authorize a release.

[bigduu]

🔒 claimed by /root/epic_audit at 2026-09-28T02:32:33Z. Isolated branch: zenith-root/chore/295-lotus-actor-ui-source; source-pointer only, no release acceptance.

[bigduu]

Delivered the source-pointer slice through PR #296, merged into Zenith main as 7ee3e22. The merged tree changes only the lotus-next mode-160000 gitlink from e8d7e7f5f3807393093da0f06b5af40a1acac22d to cdc226031079063b517fbf862037f7dac4aaad83; both Submodule Guard checks passed on the reviewed PR head. This closes source synchronization only. The release configuration still locks @bigduu/lotus-next@2026.9.22 to source a480e2bb94f5dd08fe4b01b2f8844a2c9ed03245; no new artifact, Bamboo/Bodhi consumer, live integration, or release acceptance is claimed.