Skip to content

[zenith-root] chore: advance Lotus Next pointer for canonical REST client - #174

Merged
bigduu merged 1 commit into
mainfrom
zenith/chore/173-lotus-next-rest-pointer
Sep 2, 2026
Merged

[zenith-root] chore: advance Lotus Next pointer for canonical REST client#174
bigduu merged 1 commit into
mainfrom
zenith/chore/173-lotus-next-rest-pointer

Conversation

@bigduu

@bigduu bigduu commented Sep 2, 2026

Copy link
Copy Markdown
Owner

Summary

  • Advance only the lotus-next gitlink to the merged canonical native REST client implementation.
  • Preserve the current Zenith main base, including the nightly release configuration update.
  • Keep all root source, documentation, workflow, and release files unchanged.

Submodule Updates

  • lotus-next: c9066038e6aac72ded0c025b27a97e4c154bb9e8bb59f562214a5a20ae1efadd5c1641374411dcb0
    • Rationale: Lotus Next chore: bump Bamboo pointer for #663 #30 / PR chore: bump bamboo pointer for #251 #31 collapses native REST onto one canonical /api/v1 client and removes the retired Ant Design-era split transport/base model.
    • Acceptance evidence: independent exact-head review; Node 22 and Node 24 CI; 20 test files / 671 tests; local real-runtime HAR with 315 requests, 96 canonical /api/v1 requests, and 0 legacy /v1 requests.

Test Plan

  • git diff --check
  • Verify the root diff contains exactly one mode-160000 lotus-next gitlink change with the old/new SHAs above.
  • Verify the nested checkout is clean and origin/main resolves to the new SHA.
  • Require Zenith Submodule Guard on the exact PR head.
  • Require an independent exact-head review before merge.

Screenshots

N/A — gitlink-only change.

Closes #173

@bigduu bigduu added the review:needed Waiting for review label Sep 2, 2026
@bigduu

bigduu commented Sep 2, 2026

Copy link
Copy Markdown
Owner Author

Independent exact-head review completed for 58e0fe9 against the current main base ab5b8e9.

No blocker found. The object-level diff contains exactly one mode-160000 gitlink update: lotus-next moves from c9066038e6aac72ded0c025b27a97e4c154bb9e8 to bb59f562214a5a20ae1efadd5c1641374411dcb0, with no other root file changes. An independent temporary checkout confirmed both the Zenith checkout and initialized Lotus Next checkout are clean, and Lotus Next origin/main resolves exactly to the new SHA.

The source provenance is valid: lotus-next PR #31 is merged, its reviewed head 3165f8be3151f0fdb154fca234b370fd21566f47 and merge commit bb59f562214a5a20ae1efadd5c1641374411dcb0 share the exact tree e551e7deca772a4394af81c29322bd16bcf64501. Node 22 and Node 24 CI passed; the source CI log confirms 20 test files and 671 passing tests. The recorded runtime HAR independently confirms 315 total requests, 96 canonical /api/v1 requests, and 0 legacy root /v1 requests.

The PR body contains the required accurate ## Submodule Updates section, old/new SHAs, rationale, and acceptance evidence. Both Submodule Guard jobs passed on this exact head. Final live state is CLEAN/MERGEABLE with no review threads or requested changes, and the PR correctly closes #173.

@bigduu bigduu added review:agent Agent review complete; merge gates may proceed and removed review:needed Waiting for review labels Sep 2, 2026
@bigduu
bigduu merged commit 27944d2 into main Sep 2, 2026
2 checks passed
@bigduu
bigduu deleted the zenith/chore/173-lotus-next-rest-pointer branch September 2, 2026 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

review:agent Agent review complete; merge gates may proceed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[zenith-root] chore: advance Lotus Next pointer for canonical REST client

1 participant