gaia-verifylisted

# Gaia Verify Confirm that a Gaia installation actually works. Given a workspace and a delivery surface, run the checks that match that surface and report PASS/FAIL. This skill owns the definition of "a healthy install" -- the wire-up checklist and the per-surface checks. It is the check that `gaia-release` calls at the close of every layer; here it stands alone so the user can invoke it directly against whatever they just installed. Gaia ships as one tree reaching a workspace through two surfaces -- npm/pnpm (the npm package `@jaguilar87/gaia`: symlinks + `settings.local.json`) and the Claude Code plugin (`source: github` with a pinned `ref` -- `.claude-plugin/marketplace.json` advertises the plugin, so `/plugin install` makes CC clone the git repo into its plugin cache and load hooks from the repo root's `hooks/hooks.json`; the root `.claude-plugin/plugin.json` is metadata-only, and there is no `dist/` bundle). A change can pass on one surface and break on the other, so the mode you pick must match the surface you are validating. ## Decision tree ``` "probemos" / "verify" / "test installation" ├─ Already installed in a workspace (npm/pnpm), just edited source? -> live ├─ Proving the npm tarball before a release? -> npm-sandbox ├─ Proving the npm tarball as a plugin before a release? -> plugin └─ Confirming a version already published to npm? -> registry ``` If the user does not name a mode, ask: "Which mode -- live, np