Fix plugin slash-command docs to use the namespaced form

[anshss]

Summary

• Claude Code namespaces every plugin command as /<plugin-name>:<command> (prefix from plugin.json's name, which is tokenjam). Both READMEs documented the bare forms (/onboard, /status, /optimize, /doctor, /uninstall), which do not resolve once the plugin is installed. Reproduced live: typing /onboard after a successful marketplace add + install matches nothing.
• Corrected all references (table entries and mid-sentence prose) in README.md and plugin/README.md to the namespaced form, and fixed the install line to /plugin install tokenjam@tokenjam.
• Added tests/unit/test_plugin_command_docs_namespaced.py, which derives the command set from plugin/commands/*.md and the prefix from plugin.json at test time (not hardcoded), so a rename or a newly added/removed command is caught automatically if the docs drift again.

Test plan

• python3 -m pytest tests/unit/test_plugin_command_docs_namespaced.py -v — 4 passed
• Confirmed the guard actually fails: temporarily reintroduced a bare /onboard in README.md, reran the test, observed a real AssertionError failure with a useful message, then restored and reran to confirm it passes again
• claude plugin validate ./plugin --strict — Validation passed
• Grepped the existing test suite for the bare command strings before editing; all hits were unrelated /api/v1/* HTTP routes and code comments, not plugin slash-command docs, so nothing needed inverting

[greptile-apps]

Greptile Summary

The PR corrects Claude Code plugin installation and command documentation to use the configured marketplace and plugin namespace. It also adds a regression test that derives command names and the namespace from plugin metadata.

• Updates both READMEs to advertise /tokenjam:<command> forms.
• Changes the installation example to /plugin install tokenjam@tokenjam.
• Adds a pytest guard against bare plugin-command references.

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking gap in the new documentation regression test.

The documentation changes match the configured plugin and marketplace names, but the test can still pass when namespaced command references are stale or missing because it checks only for bare forms.

Files Needing Attention: tests/unit/test_plugin_command_docs_namespaced.py

Important Files Changed

Filename	Overview
README.md	Updates plugin installation and slash-command examples consistently with the repository metadata.
plugin/README.md	Documents the namespace rule and updates all listed plugin commands and related prose.
tests/unit/test_plugin_command_docs_namespaced.py	Adds useful bare-command detection, but does not enforce the stated rename and command-set drift guarantees.

Prompt To Fix All With AI

### Issue 1
tests/unit/test_plugin_command_docs_namespaced.py:79-81
**Guard misses namespaced drift**

The test computes `namespaced` but only asserts that bare references are absent. A plugin rename or command addition, rename, or removal can therefore leave namespaced references missing or stale while this regression guard still passes, contrary to its stated coverage.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "docs: fix plugin slash-command reference..." | Re-trigger Greptile}

[greptile-apps]

Guard misses namespaced drift

The test computes namespaced but only asserts that bare references are absent. A plugin rename or command addition, rename, or removal can therefore leave namespaced references missing or stale while this regression guard still passes, contrary to its stated coverage.

Prompt To Fix With AI

This is a comment left during a code review.
Path: tests/unit/test_plugin_command_docs_namespaced.py
Line: 79-81

Comment:
**Guard misses namespaced drift**

The test computes `namespaced` but only asserts that bare references are absent. A plugin rename or command addition, rename, or removal can therefore leave namespaced references missing or stale while this regression guard still passes, contrary to its stated coverage.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!