The published marketplace install path has never been run

[rdbruhn]

The idea

Get one real run through the published marketplace install path, and keep it exercised on every
release. Right now we have no evidence it works.

From local plugin usage data:

Plugin	Uses	Last used
vine@inline (local dev copy)	3,830	today
vine@moduloMoments (published)	0	never

Every release since 0.4.0 has shipped an install path that has never been run once, while all
development and dogfooding happens against the inline copy.

Why it matters

The dogfooding argument for VINE is that we run what we ship. That holds for the skills and
breaks completely at the distribution boundary — the packaging, the manifest, the marketplace
entry, and the ${CLAUDE_PLUGIN_ROOT} path resolution are all unexercised in the form a user
receives them.

This is not hypothetical. The Autonomous Delegation dangling reference (filed separately) is
precisely a defect that only appears in a freshly-initialized repo and is invisible from the
inline copy, because our own overlay masks it. That class of bug is structurally undetectable
until someone installs the published plugin and runs a cold cycle.

Context

• Related to Research: canonical publish path for VINE plugin releases (survey other marketplace repos) #149 (canonical publish path) and Automate cross-skill /vine: colon-form smoke test (auth-blocked today) #137 (cross-skill colon-form smoke test), but the
  framing here is narrower and more testable: not "research the path" — run it once, cold, and
  find out what breaks.
• The obvious shape: install vine@moduloMoments into a scratch repo, run
  init → verify → inquire → navigate on a trivial feature, and record what diverges from the
  inline experience.
• Worth deciding whether this becomes a release-gate step in /release-plugin rather than a
  one-off. A path with zero usage will drift back to zero usage without a gate.
• The human-only constraint from Automate cross-skill /vine: colon-form smoke test (auth-blocked today) #137's AC-1 likely applies here too — nested headless runs can't
  stand in for a real install.