[zenith-root] chore: advance Lotus Next pointer for bootstrap gate

[bigduu]

Summary

• advance exactly the lotus-next submodule pointer to the merged canonical Bamboo bootstrap consumer
• keep all other submodule pointers, root configuration, release metadata, and source files unchanged
• preserve the user-owned primary checkout; this commit was produced from a fresh isolated worktree at origin/main

Submodule Updates

• lotus-next: f33045b276026351d960708111fd5c2197c5c4bc → c9066038e6aac72ded0c025b27a97e4c154bb9e8
  • upstream Issue: [lotus-next] feat: gate every surface on the canonical Bamboo bootstrap lotus-next#28
  • upstream PR: [lotus-next] feat: gate every surface on canonical Bamboo bootstrap lotus-next#29
  • exact reviewed head: ebc71cb07dd9fb131e8f2c6ee0c66cd51b02c8fd
  • upstream merge tree was verified identical to the exact reviewed head tree
  • upstream CI: Node 22 and Node 24 passed; independent exact-head review reported zero findings
  • diff-true rationale: Zenith main still pinned the pre-bootstrap-consumer commit while upstream main now contains the accepted all-surface startup gate

Test Plan

• verify the staged/root diff contains exactly one mode-160000 path: lotus-next
• verify upstream main resolves to c9066038e6aac72ded0c025b27a97e4c154bb9e8
• require both Submodule Guard checks on this exact PR head
• after merge, verify git ls-tree origin/main lotus-next resolves to the new commit

Screenshots

Not applicable: pointer-only root change; no additional UI diff beyond the independently reviewed upstream PR.

Closes #171

[bigduu]

Independent exact-head review: APPROVE — zero blocker, zero high-value finding, zero nit.

• Reviewed head: 7f0e6b890fbbd8e78db2d65116286321bfd028ad
• Reviewed base/current main: 0e1646b330f1bd95d7d246ec33ebe866a761a7cc
• Raw diff contains exactly one change: mode-160000 lotus-next from f33045b276026351d960708111fd5c2197c5c4bc to c9066038e6aac72ded0c025b27a97e4c154bb9e8
• No root source, configuration, release metadata, documentation, or other submodule pointer changed
• ## Submodule Updates contains full old/new SHAs, Issue chore: bump Codex config submodule pointers #28 / PR chore: update Codex app-server submodule pointers (#574) #29 provenance, exact reviewed head, CI/tree evidence, and a diff-true rationale
• Upstream PR chore: update Codex app-server submodule pointers (#574) #29 is merged; reviewed head tree and squash-merge tree are both 027ce1babb1927b42f322cb0a81ecffda9094c9a
• Upstream merge is the direct one-commit successor of the old pointer, is reachable, and is current lotus-next/main
• Upstream Node 22 / Node 24 checks passed and the exact-head review recorded zero findings
• Both Zenith Submodule Guard checks passed; no unresolved review thread exists
• git diff --check passed and the isolated pointer worktree is clean