Repository navigation
docs: present Pulse as three clients in the root README - #487
Merged
Merged
Conversation
emaarco
enabled auto-merge (squash)
October 27, 2026 14:48
✅ Deploy Preview for spectacular-cobbler-f6c85b ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
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.
Why
The root README still read like the MCP-only Miragon AI repo: an MCP quick start, an MCP widget image and the migration note sat at the top level, while Pulse now ships three clients (MCP server, CLI, VS Code) for the same engines.
What
apps/mcp-server-camunda7/README.md.CLAUDE.mdpoint to the new location.Verification
pnpm format:checkpassesold-names.test.tsanddocs-refs.test.tspass (200 tests)