docs: recommend the combined package and link console/client setup - #5
Merged
Merged
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.
The README currently starts with separate console-plugin installation. Make the stable combined package the default Joomla installation path, linking site setup, AI/direct client usage and the external client README.
Explain the package/component/console/webservices/client roles, fresh-install plugin enablement and update-state preservation, and the authority difference between local console access and remote stdio. Preserve developer and release documentation and add matching pending Markdown/XML changelog entries.
Depends on mcp_component #37; merge it first. Validation: reviewed installer/source boundaries, checked Markdown targets and parsed changelog XML with a single pending section and unchanged released history. Documentation-only; no release or runtime change.