Skip to content

docs: improve channel README with app URL#324

Open
ai-cora wants to merge 2 commits intomasterfrom
cora/channel-readme-v2
Open

docs: improve channel README with app URL#324
ai-cora wants to merge 2 commits intomasterfrom
cora/channel-readme-v2

Conversation

@ai-cora
Copy link
Copy Markdown
Collaborator

@ai-cora ai-cora commented Mar 22, 2026

Summary

  • Removed manual .mcp.json config section -- the server ships with the VoiceMode plugin
  • Added "Make a call" section linking to app.voicemode.dev
  • Cleaner, shorter README that tells users what they actually need to do

🤖 Generated with Claude Code

mbailey and others added 2 commits March 23, 2026 02:25
Users don't need to register the MCP server manually -- it ships with
the VoiceMode plugin. Added link to app.voicemode.dev for making calls.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown

@JiwaniZakir JiwaniZakir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The restructuring of the unreleased section drops the dedicated #### Security heading and folds what was a standalone security callout into a sub-bullet (Explicit opt-in required: set VOICEMODE_CHANNEL_ENABLED=true). Security-relevant behaviors generally benefit from being visually distinct in a changelog — a user scanning for "what changed" is more likely to notice a #### Security heading than a sixth nested bullet under a feature entry. Consider keeping the security opt-in as its own subsection or at minimum promoting it to a top-level bullet rather than nesting it after implementation details.

The diff also includes a large number of blank-line-only insertions after ### Added, ### Fixed, ### Changed, etc. headings across historical entries (e.g., 6.1.1, 6.0.x, 5.1.x). These are purely cosmetic and create significant noise in the diff, making it harder to identify the substantive changes. If normalizing whitespace throughout the file, that cleanup is better done in a separate, dedicated commit so the structural content changes here remain easy to review and revert independently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants