revert(mcp): back out leadbay_getting_started (#175) pending Codex fixes - #176
Draft
ArtyETH06 wants to merge 1 commit into
Draft
revert(mcp): back out leadbay_getting_started (#175) pending Codex fixes#176ArtyETH06 wants to merge 1 commit into
ArtyETH06 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reverts the
#175merge commit24cf7cd— Codex's review landed after the merge with 8 findings (4× P1, 4× P2), and the shipped version number is wrong (packages/mcp/package.jsonsays0.28.0, already published to npm from a different commit).Tree is byte-identical to pre-merge
main(git diff 24cf7cd^1 HEADis empty). Gates green: build ✅ · typecheck ✅ · 608 tests passing.The feature comes back, corrected, in the follow-up PR — merge this one first.