fix(docs): correct plugin install command to harness@harness-marketplace

[k002bill2]

Summary

• The Korean/Japanese READMEs and the Quickstart guide use plugin-install commands that don't match the names declared in .claude-plugin/marketplace.json (marketplace name harness-marketplace, plugin name harness). Copy-pasting them fails to install the plugin.
• This aligns all three with the already-correct English README.md, which uses harness@harness-marketplace.

Changes

• README_KO.md: /plugin install harness-marketplace → /plugin install harness@harness-marketplace
• README_JA.md: same fix
• docs/quickstart.md: harness@harness → harness@harness-marketplace in the Step 2 install command and the two plugin list / plugin enable references in Failure FAQ question: would this be adaptable for google gemini as well? #3

Test Plan

• .claude-plugin/marketplace.json declares marketplace harness-marketplace + plugin harness, so harness@harness-marketplace is the correct reference
• grep -rn "harness@harness" README*.md docs/ — every occurrence is now followed by -marketplace
• claude plugin marketplace add revfactory/harness then claude plugin install harness@harness-marketplace succeeds end-to-end

---

🤖 Generated with Claude Code

[izoa0407]

Confirming this on Claude Code 2.1.226 / Windows 11 — /plugin install harness-marketplace fails, and harness@harness-marketplace is what works. Test plan item 3 checks out end to end for me:

claude plugin marketplace add revfactory/harness
claude plugin install harness@harness-marketplace

Also worth noting (same symptom as #20, different cause, and not covered by this PR): hand-editing settings.json does not install the plugin either. With an extraKnownMarketplaces entry the repo is cloned into plugins/marketplaces/, but it never gets registered in known_marketplaces.json and doesn't appear in claude plugin marketplace list — a half-installed state with no error message anywhere.

Running the CLI afterwards printed:

Successfully added marketplace: harness-marketplace (declared in user settings)

which suggests the settings entry only declares the marketplace, and actual registration plus cache refresh is the CLI's job. In my case the CLI also renamed the mismatched revfactory-harness directory to harness-marketplace.

Might be worth a line in the install docs alongside this fix, since both paths land on the same "installation doesn't work" symptom with no error to go on. Happy to open a separate PR for that if you'd prefer to keep this one scoped to the command strings.