[m1ngshum]

The homepage associated mcpm search with computed trust evidence, while search reports registry lifecycle status. Its numbered workflow also skipped installation and showed only a guard dry run.

Separate Discover from Assess and complete the tour with Install and Enable guard. Show both scoped dry-run and actual enable commands, followed by the required server restart. Use the more concrete headline, qualify the mcpm account/model-subscription claim, and explain that individual servers/providers may need credentials. Add an Unreleased documentation note.

Validation:

• Astra independently checked the exact two-file diff against search/install/guard source and README and cleared it with no findings.
• Local browser checks at 320/375/768/1280/1440/1920px: no page overflow, clipped changed text, broken images or missing anchor targets; desktop hero/workflow screenshots inspected.
• Clipboard success/denial and no-JavaScript disclosure/workflow checks passed.
• Ran the production staging script in a disposable copy: exactly six public assets, byte-identical to candidate source; git diff --check passed.

Only homepage HTML and CHANGELOG change. No CSS, JavaScript, dependencies or CLI/runtime behavior changes. No live deployment or CLI/native tests were performed. The existing Netlify integration may create a PR preview; merging to main publishes the homepage and remains a separate action.