chore: advance Lotus Next feed cursor pointer (#167)

[bigduu]

Summary

• Advance the single lotus-next gitlink from 125b4cf6966f9f67412f9dc8c1eb64786d87ec75 to current Lotus Next main@f33045b276026351d960708111fd5c2197c5c4bc.
• Bring fresh Zenith checkouts onto the accepted monotonic account-feed cursor, reconnect, failure-isolation, and reset contract from Lotus Next chore: bump bamboo model-issued activation pointer (#620) #26 / PR chore: bump Bamboo modular config pointer (#597) #27.
• Leave every other submodule pointer and every root file unchanged.

Closes #167

Parent migration tracker: bigduu/lotus-next#11

Submodule Updates

Submodule	Old SHA	New SHA	Rationale
lotus-next	125b4cf6966f9f67412f9dc8c1eb64786d87ec75	f33045b276026351d960708111fd5c2197c5c4bc	Advance one root gitlink over the independently reviewed and merged Lotus Next #26 slice. The upstream diff validates one JSON/MessagePack cursor state machine, binds reset to the active subscription epoch, preserves monotonicity across reset/reconnect, isolates failed feed delivery without disrupting agent channels, and makes account-feed persistence/reset ordering authoritative.

Verification

• Fresh isolated worktree started at exact Zenith origin/main@b6a4a075ceb1eec5d6d9be8a652345cee912b62e.
• git diff --cached --raw before commit showed exactly one mode-160000 update: lotus-next 125b4cf -> f33045b.
• git diff --check origin/main...HEAD passed.
• The new gitlink equals live bigduu/lotus-next main@f33045b276026351d960708111fd5c2197c5c4bc.
• Lotus Next PR chore: bump Bamboo modular config pointer (#597) #27 exact head c17ba449c6421ecc5643948973bd41f1a241a684 received an independent APPROVE after Node 22/24 full verification (18 files / 408 tests), and was squash-merged as f33045b276026351d960708111fd5c2197c5c4bc; Issue chore: bump bamboo model-issued activation pointer (#620) #26 is closed and Roadmap Done.
• 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 lotus-next
• Verify every non-target origin/main gitlink remains byte-for-byte unchanged.

Screenshots

Not applicable; root repository gitlink-only change.

[bigduu]

Independent agent review: APPROVE for exact head cfc8bca6383d0c83fbf61bcd1fb641634f0a07cd against current base b6a4a075ceb1eec5d6d9be8a652345cee912b62e.

Verified:

• direct one-commit topology from current main
• exactly one raw tree change: mode-160000 lotus-next from 125b4cf6966f9f67412f9dc8c1eb64786d87ec75 to f33045b276026351d960708111fd5c2197c5c4bc
• all other 8 gitlinks and all 31 ordinary root entries are byte-for-byte unchanged
• target SHA equals live Lotus Next main and the merged PR #27 commit; reviewed-head and squash-merge trees are identical
• .gitmodules still points lotus-next to https://github.com/bigduu/lotus-next.git
• the ## Submodule Updates table has exact old/new SHAs and a rationale true to the upstream diff
• exact-head Submodule Guard run 33528782592 is green; PR is CLEAN/MERGEABLE with zero review threads or requested changes

The existing notes workflow does not include lotus-next in its watched set and therefore did not itself validate these notes; Zenith #116 already tracks that gap. This approval relies on the explicit manual notes/tree audit above, which passed, so the pre-existing P3 workflow gap is not a blocker for this exact pointer update.