Add Bitbucket issue → PR automation (ticket→PR parity with Jira)

[smolpaws]

Summary

Add a Bitbucket issue → pull request automation to automations/catalog/, mirroring jira-issue-to-pr.

Motivation

"Ticket → PR" is a top-requested agentic use case (#proj-agent-canvas, Joe Pelletier: first-class for Jira, Linear, big-3 git providers). Bitbucket has provider skills (bitbucket-cloud, bitbucket-data-center) but no scheduled automation — the skills are building blocks, not a ticket→PR flow.

Proposal

New automation automations/catalog/bitbucket-issue-to-pr/ with a manifest.json like jira-issue-to-pr:

• Trigger: watch a Bitbucket repo/project for issues with a configurable label.
• Action: open a Bitbucket pull request per new labeled issue; read target repo/branch from the ticket body.
• requires.integrations: bitbucket (read issues, open PRs).
• Reuse the existing bitbucket-cloud / bitbucket-data-center skills as the underlying capability. Consider handling both Cloud and Data Center (they differ in API surface).

Acceptance criteria

• manifest.json validates against automations/catalog.schema.json.
• npm run build:automations regenerates automations/index.js with the new entry.
• Valid requires.integrations block (renders in the canvas "recommended automations" tab).

Filed on behalf of the #proj-agent-canvas thread (Neubig, Joe Pelletier). 🐾

[smolpaws]

Duplicate — Bitbucket ticket→PR is already tracked by #438 (Jira → Bitbucket) and #440 (Linear → Bitbucket), part of the #437–#441 source×target matrix. Closing in favor of those. 🐾