Broaden gapp:deploy skill triggers to include deployment-status checks

[krisrowe]

Problem

The gapp:deploy skill description currently triggers on intents like "deploy this," "set up CI/CD," "push to production." It doesn't trigger on exploratory intents like "is this deployed?", "does this have cloud presence?", "where would I check if this is running?"

As a result, agents in non-gapp sessions don't reach for gapp's gapp_list / gapp_status / gapp_projects_list MCP tools when those would answer the user's question — even when gapp is the right answer. The user has to explicitly say "check gapp" to get the agent there.

Repro

1. Open a Claude Code session in a repo that has been deployed by gapp.
2. Ask "is this deployed?" or similar without naming gapp.
3. Observe: the agent doesn't reach for gapp's MCP tools to check.

Proposed fix

No code changes — only widen the description field in skills/deploy/SKILL.md to include deployment-status intents alongside deploy-action intents.

Suggested phrases to add:

• "is this deployed"
• "does this have cloud presence"
• "is this in production"
• "where is this running"
• "what cloud presence does this have"
• "is X deployed"
• "check deployment"
• "does this have a deployment"

Out of scope

• Adding new tools or MCP changes — gapp_list / gapp_status already cover the read path; only discoverability is missing.
• Changing the deploy-action triggers (those work fine).