Feature: multi-host plugin layout and full-CLI agent skill

[akshaysasidrn]

📝 What this does

Turns the skills repo into a multi-host plugin and widens the skill from a deploy-only golden path to the whole CLI. Previously an agent went blind the moment a user asked for logs, a database, or why their app was crashing — every one of those commands already existed, the skill just never mentioned them.

🏗️ Architecture

One payload directory, three host catalogs pointing at it. This adds marketplace installs without breaking the host-agnostic one — verified before committing that the skills CLI still discovers a nested layout.

.claude-plugin/marketplace.json  ─┐
.cursor-plugin/marketplace.json  ─┼─→  plugins/stackdome/
.agents/plugins/marketplace.json ─┘      ├── three host manifests (version-locked)
                                         ├── hooks/  (PreToolUse auto-approve)
                                         └── skills/stackdome-deploy/SKILL.md

The hook exists because allowed-tools alone is not sufficient: an allow decision covers the whole Bash command, so stackdome status; rm -rf ~ and printf x # stackdome status both pass a naive prefix match. It strips quoted spans and escapes, refuses if any control metacharacter survives at top level, and requires a bare PATH binary. Everything else falls through to the normal prompt, which is the safe direction.

🔀 Changes

• Restructured the repo into a plugin payload with catalogs for Claude Code, Cursor, and Codex.
• Grew the skill from 73 to 185 lines: intent routing table, auth ladder, day-2 command tables, debugging recipes, destructive-operation rules.
• Rewrote the skill description so it triggers on logs, secrets, databases, and crashes rather than only on deploys.
• Scoped allowed-tools to the Stackdome CLI alone, and added a PreToolUse hook that auto-approves only single simple invocations.
• Corrected the documented install and docs URLs to hosts that resolve, and required deploy --wait before any success claim.

🧪 How to test

• Run the hook test suite and confirm every case passes.
• Put a stackdome binary on PATH, then feed the hook a plain command and confirm it approves.
• Feed it a chained command and confirm it defers.
• Install the skill with the host-agnostic command and confirm it lands.
• Add the repo as a plugin marketplace source in Claude Code and install from it.
• Spot-check a few day-2 commands in the skill against stackdome <cmd> --help.

⚠️ Notes for review

• The Codex manifest's interface field names are a best-effort schema guess — inert if wrong, worth checking against an authoritative schema.
• No privacy-policy or terms URLs are set, because those pages do not exist yet. Omitted rather than invented.
• The CLI install path stays gated until the CLI repo is public and tagged.