[zenith-root] chore: advance Lotus Next pointer for canonical REST client - #174
Conversation
|
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. |
Summary
lotus-nextgitlink to the merged canonical native REST client implementation.mainbase, including the nightly release configuration update.Submodule Updates
lotus-next:c9066038e6aac72ded0c025b27a97e4c154bb9e8→bb59f562214a5a20ae1efadd5c1641374411dcb0/api/v1client and removes the retired Ant Design-era split transport/base model./api/v1requests, and 0 legacy/v1requests.Test Plan
git diff --check160000lotus-nextgitlink change with the old/new SHAs above.origin/mainresolves to the new SHA.Screenshots
N/A — gitlink-only change.
Closes #173