chore: refresh the generated endpoint counts so CI is green on main - #1144
chore: refresh the generated endpoint counts so CI is green on main#1144dmazhukov wants to merge 1 commit into
Conversation
Signed-off-by: Dmitrii Zhukov <dmitry0983@gmail.com>
|
@dmazhukov is attempting to deploy a commit to the rohitg00's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThe change synchronizes REST endpoint counts in ChangesREST endpoint count synchronization
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
CI is currently red on
mainitself, so every open PR inherits two failures it did not cause.This refreshes the four places that carry a hardcoded endpoint count.
An endpoint landed in #1132 / #1136 without the generated docs being refreshed alongside it:
npm run skills:check→DRIFT: plugin/skills/agentmemory-rest-api/REFERENCE.md(says 118, generator produces 119)test/consistency.test.ts > documented REST endpoint counts match registered API paths→ README says129 endpoints on port, 130 are registeredAGENTS.mdand the boot banner insrc/index.tscarry the same number and the consistencytest checks all three, so all four files move together.
Verification
On a clean checkout of
main:With this change:
REFERENCE.mdis the generator's own output (npm run skills:gen), not hand-edited.Noticed while working on #1142; keeping it separate so that PR stays one logical change.
Summary by CodeRabbit
Documentation
Chores