feat: Package the ops/DevOps agent as a first-class one-click Trinity starter

[vybe]

Summary

Turn the existing Claude Code ops agent (abilityai/trinity-ops-public) and the /trinity:deploy-new-instance scaffolding into a first-class, one-click starter agent for managing a Trinity instance — discoverable in the standard agent-creation flow with sane defaults and a guided setup, so an operator gets a working "manage my instance" agent without building one from scratch.

Context

The ops-agent pattern is proven but currently requires running scaffolding skills and assembling pieces by hand. To make instance management a true onboarding starting point, it needs to be a packaged, deployable starter with curated defaults (capabilities, schedules, ops skills) that a new operator can launch and immediately use.

Acceptance Criteria

• The ops/DevOps agent is available as a selectable starter in the agent-creation flow (Trinity template and/or github: template)
• One guided setup path collects only what's required (instance URL, MCP key) and produces a running agent
• Ships with curated ops capabilities and skills: health checks, update/rollback, log inspection, basic provisioning
• Defaults are safe (least-privilege scope, read-only where appropriate) and documented
• Consolidates with trinity-ops-public / /trinity:deploy-new-instance rather than duplicating logic

Technical Notes

• Template creation path: POST /api/agents supports template, including github:Org/repo; local templates live in config/agent-templates/.
• Reuse /trinity:connect + /trinity:onboard from the abilities trinity plugin for the connect / MCP-key step.
• Decide packaging: bundled Trinity template vs. pinned github:abilityai/trinity-ops-public reference vs. both.

Parent epic: ops/DevOps starter agents for one-click instance management.