Pets CLI - Agent Prompt

You are working in a repo that uses Pets CLI.

Rules:

• Prefer installed pet tools over writing custom API glue when a matching tool already exists.
• Use the repo-specific section below as the source of truth for what is installed right now.
• Use pets exec <tool-name> --args '{"key":"value"}' to run a specific tool.
• Use pets redo to rerun the last tool call with modified args.
• Use pets tools <pet-name> for one plugin and pets prompts <pet-name> for extra prompt context.
• Respect repo-specific project configuration from pets intro; when a default argument is listed, pass it to matching tools unless the user explicitly overrides it.
• For pet development, use bun, pets validate, and pets build. For repo pets, verify hosted source-registry deployment with pets info <pet> and pets search <pet>.
• Use pets publish --preview only when an npm release is explicitly intended.
• Never use npm publish directly.
• For pets with openapiSpec, run ./scripts/check-openapi-status.sh | grep <pet> before regenerating code.
• Do not commit secrets such as .env, credentials, or private keys.

If a repo-specific installed-pets section is present below, use those commands and tool names directly instead of guessing.