chore: advance Bamboo bootstrap pointer (#169)

[bigduu]

Summary

• Advance the single bamboo gitlink from b412deaee8fc95a356fea7793a993f78072e461b to current Bamboo dev@655732e24561b09869b7e97ab11bba01cf9bc4df.
• Bring fresh Zenith checkouts onto the accepted canonical frontend bootstrap contract from Bamboo #1039 / PR #1040.
• Leave every other submodule pointer and every root file unchanged.

Closes #169

Parent migration tracker: bigduu/lotus-next#11

Submodule Updates

Submodule	Old SHA	New SHA	Rationale
bamboo	b412deaee8fc95a356fea7793a993f78072e461b	655732e24561b09869b7e97ab11bba01cf9bc4df	Advance one root gitlink over independently reviewed and merged Bamboo #1039. The upstream diff adds the public canonical GET /api/v1/bootstrap schema for Bamboo/API/realtime identity and capability admission, derives request-sensitive auth state from one authoritative config snapshot, keeps legacy /v1 probing out of Lotus Next, documents the missing WSS acknowledgement as a separate slice, and removes a redundant header-derived locality fallback that produced CodeQL alert #203 without changing auth semantics.

Verification

• Fresh isolated worktree started at exact Zenith origin/main@30b7637bdef354a3a67914f3a7ccf76750e3d5ce.
• git diff --cached --raw before commit showed exactly one mode-160000 update: bamboo b412dea -> 655732e.
• git diff --check origin/main...HEAD passed.
• The new gitlink equals live bigduu/Bamboo-agent dev@655732e24561b09869b7e97ab11bba01cf9bc4df, and the old pin is its ancestor.
• Bamboo PR #1040 exact head 9023c9b67195064b2a64799b961282e33e6b37e8 received an independent exact-head approval and both CI/CodeQL workflows passed; its tree was squash-merged unchanged as 655732e24561b09869b7e97ab11bba01cf9bc4df.
• Zenith Submodule Guard, applicable exact-head checks, and an independent exact-head root review must pass before merge.

Test Plan

• git diff --check origin/main...HEAD
• git diff --raw origin/main...HEAD
• git diff --name-only origin/main...HEAD
• git ls-tree HEAD bamboo
• Verify every non-target origin/main gitlink remains byte-for-byte unchanged.

Screenshots

Not applicable; root repository gitlink-only change.

[bigduu]

Independent exact-head review: APPROVE

• Zenith head: aaf72b4a4cca91755ea3e4ca97f40d5d17250245
• Zenith base/current main: 30b7637bdef354a3a67914f3a7ccf76750e3d5ce

Verified against Issue #169:

• The PR contains exactly one commit whose sole parent is the exact base.
• The complete root diff is exactly one mode-160000 gitlink update: bamboo from b412deaee8fc95a356fea7793a993f78072e461b to 655732e24561b09869b7e97ab11bba01cf9bc4df.
• All eight non-target gitlinks and every root file are byte-for-byte unchanged.
• The new SHA is the live bigduu/Bamboo-agent dev tip and the verified squash merge of Bamboo PR #1040. Its tree is identical to PR #1040 exact head 9023c9b67195064b2a64799b961282e33e6b37e8, and the old Zenith pin is its sole parent/ancestor.
• The ## Submodule Updates row contains the exact old/new SHAs and a diff-true rationale for the canonical bootstrap contract, auth snapshot, no-/v1 behavior, documented WSS-ack boundary, and CodeQL remediation.
• Exact-head checks Validate Submodule Pointers and Require Submodule Notes (PR) are successful.
• Final live gate: OPEN, non-draft, MERGEABLE/CLEAN, with zero review threads, zero requested changes, and no unrelated security-sensitive root changes.

Any head or base drift requires a fresh review.