Repository navigation
Correct the paid install path and the commands reference - #724
Merged
Merged
Conversation
The install guide told buyers to reveal a Composer command in their account, which the account never does (it lists and revokes credentials; the secret is shown only when commands are generated by the site-builder handoff or issued to Marketplace installs), and installed the root package instead of the purchased one. It now describes the two real credential flows, the by-hand install of the purchased package, the Admin theme step, and states the 30-minute expiry and instance and domain binding beside the build-time recommendation. The boost commands reference named commands that do not exist; it now lists the real ones.
howdu
enabled auto-merge (squash)
October 2, 2026 14:54
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.
Problem
The install guide and README told buyers to reveal a short-lived Composer command in their customer account and then installed the root package. The account page only lists and revokes credentials; the secret is shown only when a site-build handoff generates commands, or issued to Marketplace installs in Admin. The boost commands reference also named several commands that do not exist.
Change
Verification
Every claim was checked against the App source on `origin/main` (account view, handoff action, token actions, distribution token resolver) and Core command signatures. The docs checks pass: links (1,308), commands, requirements, orphans, env, config, readme standards and root docs. Not browser-checked, and not confirmed whether the root package is also served from the private repository.