@openhands/agent-canvas 1.8.0 → 1.9.0

package/dist/manifests/types.d.ts

@@ -0,0 +1,227 @@
+/**
+ * Host-owned shape of an extension-authored setup experience.
+ *
+ * A catalog entry is declarative data published by `@openhands/extensions`. Its
+ * optional `setup` block says what to ask a user for; everything derivable from
+ * that — the request to send, the route, the review screen, the analytics — is
+ * this host's to generate, so none of it appears here.
+ *
+ * The names mirror `@openhands/extensions/automations`' own declarations, so an
+ * entry from the published package assigns without an adapter.
+ */
+export declare const SETUP_VERSION = "1.0";
+export type SetupMode = "direct" | "assisted";
+export type SetupFieldType = "text" | "textarea" | "select" | "cron" | "timezone" | "repo-picker";
+export type SetupGitProvider = "github" | "gitlab" | "bitbucket";
+export type SetupTriggerKind = "cron" | "event";
+/** Placeholder namespaces a setup block may reference inside `{{...}}`. */
+export declare const SETUP_PLACEHOLDER_NAMESPACES: readonly ["form", "automation"];
+export interface SetupFieldOption {
+    value: string;
+    label: string;
+}
+export interface SetupFieldConstraints {
+    minLength?: number;
+    maxLength?: number;
+    /**
+     * A host-implemented check named from a closed set. Entries supply no regex
+     * of their own, so they cannot hand the host a pathological pattern.
+     */
+    format?: "safeExpressionLiteral";
+}
+export interface SetupFormField {
+    type: SetupFieldType;
+    label: string;
+    help: string;
+    placeholder?: string;
+    default?: string;
+    required: boolean;
+    provider?: SetupGitProvider;
+    options?: SetupFieldOption[];
+    constraints?: SetupFieldConstraints;
+}
+/** Keyed by field name, which is what `{{form.<name>}}` resolves against. */
+export type SetupFormFields = Record<string, SetupFormField>;
+export interface SetupForm {
+    note?: string;
+    /** Inputs that decide when the automation runs, keyed by trigger kind. */
+    triggers?: Partial<Record<SetupTriggerKind, SetupFormFields>>;
+    /** Every other input: the arguments to the automation itself. */
+    args: SetupFormFields;
+}
+export interface SetupBlock {
+    version: typeof SETUP_VERSION;
+    mode: SetupMode;
+    form: SetupForm;
+    /** direct only. What the automation is told to do. */
+    prompt?: string;
+    /** direct only, event trigger only. Which delivered events belong to it. */
+    filter?: string;
+    /**
+     * Setup context for the conversation that finishes setup. Required for
+     * assisted mode. Optional for direct mode, where it seeds the fallback
+     * conversation offered when the deployment cannot run the direct path.
+     */
+    message?: string;
+}
+export interface SetupIntegrationRequirement {
+    /** Why this entry needs the integration. */
+    message: string;
+    /** Defaults to true. `false` lets setup continue while it is unconnected. */
+    required?: false;
+}
+export interface SetupPrerequisites {
+    /** Keyed by integration catalog id. */
+    integrations: Record<string, SetupIntegrationRequirement>;
+    /** Deployment capabilities this entry cannot run without. */
+    features?: string[];
+}
+/**
+ * The part of a catalog entry this host reads. An admitted entry always has a
+ * `setup` block; entries without one are simply not setup entries.
+ */
+export interface SetupEntry {
+    id: string;
+    name: string;
+    description: string;
+    requires: SetupPrerequisites;
+    /** The skill that owns the launch command. Defaults to `id`. */
+    skill?: string;
+    setup: SetupBlock;
+}
+export type SetupPayloadValue = string | number | boolean | null | SetupPayloadValue[] | {
+    [key: string]: SetupPayloadValue;
+};
+export interface SetupRequestBody {
+    [key: string]: SetupPayloadValue;
+}
+/** Form values are collected as strings; the payload mapping shapes them. */
+export type SetupFormValues = Record<string, string>;
+/** `GET /v1/capabilities` — what this deployment supports. */
+export interface DeploymentCapabilities {
+    ready: boolean;
+    triggerKinds: string[];
+    eventSources: string[];
+    eventTypes: string[];
+    triggers: {
+        cron?: {
+            minIntervalSeconds: number;
+            timezones: string[];
+        };
+        event?: {
+            filterLanguage: string;
+            filterFunctions: string[];
+        };
+    };
+    features: string[];
+}
+/** A single problem with a draft, addressed to the field that caused it. */
+export interface DraftValidationError {
+    /** Dotted path into the draft. Null when the problem spans the whole draft. */
+    field: string | null;
+    code: string;
+    message: string;
+}
+/** `POST /v1/validate` — an invalid draft is still a 200. */
+export interface ValidateDraftResponse {
+    valid: boolean;
+    errors: DraftValidationError[];
+    sampleEventMatched?: boolean | null;
+}
+/**
+ * Host-owned shape of the production Automation interface manifest, published
+ * by `@openhands/extensions/automations` as `AUTOMATION_INTERFACE`.
+ *
+ * The catalog states what varies per automation; this states the domain-level
+ * facts of the interface itself. As with setup entries, the published data is
+ * validated at admission rather than trusted, and a package that predates the
+ * manifest simply leaves the host on its own defaults.
+ */
+export declare const INTERFACE_VERSION = "1.0";
+/** The closed set of runtime-model properties a client may offer for setting. */
+export type AutomationAttributeName = "name" | "prompt" | "model" | "timeout" | "schedule";
+export type InterfaceAttributeType = "text" | "textarea" | "number" | "llm-profile" | "schedule";
+/** How one settable attribute of an existing Automation is offered. */
+export interface InterfaceAttribute {
+    type: InterfaceAttributeType;
+    label: string;
+    help?: string;
+    required: boolean;
+    /** Only a `number` attribute carries constraints. */
+    constraints?: {
+        min?: number;
+        max?: number;
+    };
+}
+export interface InterfaceRoutes {
+    list: string;
+    /** Carries the `:automationId` segment the host substitutes. */
+    setup: string;
+    /** Carries the `:automationId` segment the host substitutes. */
+    detail: string;
+}
+/**
+ * Service-relative paths the host calls. The base path, methods, headers, and
+ * auth remain the host's. `{id}` marks where the automation id is substituted.
+ */
+export interface InterfaceEndpoints {
+    list: string;
+    detail: string;
+    dispatch: string;
+    runs: string;
+    tarball: string;
+    health: string;
+    capabilities: string;
+    validate: string;
+    createPrompt: string;
+    createPlugin: string;
+}
+export type InterfaceEndpointName = keyof InterfaceEndpoints;
+export interface InterfaceImportExport {
+    fileKind: string;
+    fileVersion: number;
+    filenameSuffix: string;
+    importDefaults: {
+        /** Provider inferred for short owner/repo repository URLs on import. */
+        repoProvider: SetupGitProvider;
+        /** Event source of the placeholder trigger that keeps an import inert. */
+        placeholderEventSource: string;
+    };
+}
+export interface InterfaceManifest {
+    version: typeof INTERFACE_VERSION;
+    routes: InterfaceRoutes;
+    navigation: {
+        sidebar: {
+            label: string;
+        };
+        commandMenu: {
+            title: string;
+            description: string;
+            keywords: string;
+        };
+    };
+    pages: {
+        list: {
+            title: string;
+            subtitle: string;
+        };
+        detail: {
+            backLabel: string;
+        };
+        edit: {
+            title: string;
+        };
+    };
+    docsUrl: string;
+    /**
+     * The input surface of an existing Automation, keyed by the runtime-model
+     * property the host sends. Rendering it as an edit dialog is this host's
+     * choice, not stated here.
+     */
+    attributes: Partial<Record<AutomationAttributeName, InterfaceAttribute>>;
+    importExport: InterfaceImportExport;
+    endpoints: InterfaceEndpoints;
+    featuredAutomationIds: string[];
+    responderIntegrationIds: string[];
+}

package/dist/manifests/types.js

@@ -0,0 +1,6 @@
+//#region src/manifests/types.ts
+var e = ["form", "automation"];
+//#endregion
+export { e as SETUP_PLACEHOLDER_NAMESPACES };
+
+//# sourceMappingURL=types.js.map

package/dist/manifests/types.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"types.js","names":[],"sources":["../../src/manifests/types.ts"],"sourcesContent":["/**\n * Host-owned shape of an extension-authored setup experience.\n *\n * A catalog entry is declarative data published by `@openhands/extensions`. Its\n * optional `setup` block says what to ask a user for; everything derivable from\n * that — the request to send, the route, the review screen, the analytics — is\n * this host's to generate, so none of it appears here.\n *\n * The names mirror `@openhands/extensions/automations`' own declarations, so an\n * entry from the published package assigns without an adapter.\n */\n\nexport const SETUP_VERSION = \"1.0\";\n\nexport type SetupMode = \"direct\" | \"assisted\";\n\nexport type SetupFieldType =\n  | \"text\"\n  | \"textarea\"\n  | \"select\"\n  | \"cron\"\n  | \"timezone\"\n  | \"repo-picker\";\n\nexport type SetupGitProvider = \"github\" | \"gitlab\" | \"bitbucket\";\n\nexport type SetupTriggerKind = \"cron\" | \"event\";\n\n/** Placeholder namespaces a setup block may reference inside `{{...}}`. */\nexport const SETUP_PLACEHOLDER_NAMESPACES = [\"form\", \"automation\"] as const;\n\nexport interface SetupFieldOption {\n  value: string;\n  label: string;\n}\n\nexport interface SetupFieldConstraints {\n  minLength?: number;\n  maxLength?: number;\n  /**\n   * A host-implemented check named from a closed set. Entries supply no regex\n   * of their own, so they cannot hand the host a pathological pattern.\n   */\n  format?: \"safeExpressionLiteral\";\n}\n\nexport interface SetupFormField {\n  type: SetupFieldType;\n  label: string;\n  help: string;\n  placeholder?: string;\n  default?: string;\n  required: boolean;\n  provider?: SetupGitProvider;\n  options?: SetupFieldOption[];\n  constraints?: SetupFieldConstraints;\n}\n\n/** Keyed by field name, which is what `{{form.<name>}}` resolves against. */\nexport type SetupFormFields = Record<string, SetupFormField>;\n\nexport interface SetupForm {\n  note?: string;\n  /** Inputs that decide when the automation runs, keyed by trigger kind. */\n  triggers?: Partial<Record<SetupTriggerKind, SetupFormFields>>;\n  /** Every other input: the arguments to the automation itself. */\n  args: SetupFormFields;\n}\n\nexport interface SetupBlock {\n  version: typeof SETUP_VERSION;\n  mode: SetupMode;\n  form: SetupForm;\n  /** direct only. What the automation is told to do. */\n  prompt?: string;\n  /** direct only, event trigger only. Which delivered events belong to it. */\n  filter?: string;\n  /**\n   * Setup context for the conversation that finishes setup. Required for\n   * assisted mode. Optional for direct mode, where it seeds the fallback\n   * conversation offered when the deployment cannot run the direct path.\n   */\n  message?: string;\n}\n\nexport interface SetupIntegrationRequirement {\n  /** Why this entry needs the integration. */\n  message: string;\n  /** Defaults to true. `false` lets setup continue while it is unconnected. */\n  required?: false;\n}\n\nexport interface SetupPrerequisites {\n  /** Keyed by integration catalog id. */\n  integrations: Record<string, SetupIntegrationRequirement>;\n  /** Deployment capabilities this entry cannot run without. */\n  features?: string[];\n}\n\n/**\n * The part of a catalog entry this host reads. An admitted entry always has a\n * `setup` block; entries without one are simply not setup entries.\n */\nexport interface SetupEntry {\n  id: string;\n  name: string;\n  description: string;\n  requires: SetupPrerequisites;\n  /** The skill that owns the launch command. Defaults to `id`. */\n  skill?: string;\n  setup: SetupBlock;\n}\n\nexport type SetupPayloadValue =\n  | string\n  | number\n  | boolean\n  | null\n  | SetupPayloadValue[]\n  | { [key: string]: SetupPayloadValue };\n\nexport interface SetupRequestBody {\n  [key: string]: SetupPayloadValue;\n}\n\n/** Form values are collected as strings; the payload mapping shapes them. */\nexport type SetupFormValues = Record<string, string>;\n\n/** `GET /v1/capabilities` — what this deployment supports. */\nexport interface DeploymentCapabilities {\n  ready: boolean;\n  triggerKinds: string[];\n  eventSources: string[];\n  eventTypes: string[];\n  triggers: {\n    cron?: { minIntervalSeconds: number; timezones: string[] };\n    event?: { filterLanguage: string; filterFunctions: string[] };\n  };\n  features: string[];\n}\n\n/** A single problem with a draft, addressed to the field that caused it. */\nexport interface DraftValidationError {\n  /** Dotted path into the draft. Null when the problem spans the whole draft. */\n  field: string | null;\n  code: string;\n  message: string;\n}\n\n/** `POST /v1/validate` — an invalid draft is still a 200. */\nexport interface ValidateDraftResponse {\n  valid: boolean;\n  errors: DraftValidationError[];\n  sampleEventMatched?: boolean | null;\n}\n\n/**\n * Host-owned shape of the production Automation interface manifest, published\n * by `@openhands/extensions/automations` as `AUTOMATION_INTERFACE`.\n *\n * The catalog states what varies per automation; this states the domain-level\n * facts of the interface itself. As with setup entries, the published data is\n * validated at admission rather than trusted, and a package that predates the\n * manifest simply leaves the host on its own defaults.\n */\n\nexport const INTERFACE_VERSION = \"1.0\";\n\n/** The closed set of runtime-model properties a client may offer for setting. */\nexport type AutomationAttributeName =\n  | \"name\"\n  | \"prompt\"\n  | \"model\"\n  | \"timeout\"\n  | \"schedule\";\n\nexport type InterfaceAttributeType =\n  | \"text\"\n  | \"textarea\"\n  | \"number\"\n  | \"llm-profile\"\n  | \"schedule\";\n\n/** How one settable attribute of an existing Automation is offered. */\nexport interface InterfaceAttribute {\n  type: InterfaceAttributeType;\n  label: string;\n  help?: string;\n  required: boolean;\n  /** Only a `number` attribute carries constraints. */\n  constraints?: { min?: number; max?: number };\n}\n\nexport interface InterfaceRoutes {\n  list: string;\n  /** Carries the `:automationId` segment the host substitutes. */\n  setup: string;\n  /** Carries the `:automationId` segment the host substitutes. */\n  detail: string;\n}\n\n/**\n * Service-relative paths the host calls. The base path, methods, headers, and\n * auth remain the host's. `{id}` marks where the automation id is substituted.\n */\nexport interface InterfaceEndpoints {\n  list: string;\n  detail: string;\n  dispatch: string;\n  runs: string;\n  tarball: string;\n  health: string;\n  capabilities: string;\n  validate: string;\n  createPrompt: string;\n  createPlugin: string;\n}\n\nexport type InterfaceEndpointName = keyof InterfaceEndpoints;\n\nexport interface InterfaceImportExport {\n  fileKind: string;\n  fileVersion: number;\n  filenameSuffix: string;\n  importDefaults: {\n    /** Provider inferred for short owner/repo repository URLs on import. */\n    repoProvider: SetupGitProvider;\n    /** Event source of the placeholder trigger that keeps an import inert. */\n    placeholderEventSource: string;\n  };\n}\n\nexport interface InterfaceManifest {\n  version: typeof INTERFACE_VERSION;\n  routes: InterfaceRoutes;\n  navigation: {\n    sidebar: { label: string };\n    commandMenu: { title: string; description: string; keywords: string };\n  };\n  pages: {\n    list: { title: string; subtitle: string };\n    detail: { backLabel: string };\n    edit: { title: string };\n  };\n  docsUrl: string;\n  /**\n   * The input surface of an existing Automation, keyed by the runtime-model\n   * property the host sends. Rendering it as an edit dialog is this host's\n   * choice, not stated here.\n   */\n  attributes: Partial<Record<AutomationAttributeName, InterfaceAttribute>>;\n  importExport: InterfaceImportExport;\n  endpoints: InterfaceEndpoints;\n  featuredAutomationIds: string[];\n  responderIntegrationIds: string[];\n}\n"],"mappings":";AA6BA,IAAa,IAA+B,CAAC,QAAQ,YAAY"}

package/dist/node_modules/@openhands/extensions/automations/catalog/github-pr-reviewer/manifest.cjs

@@ -0,0 +1,9 @@
+require("../../../../../../_virtual/_rolldown/runtime.cjs");var e={id:`github-pr-reviewer`,name:`GitHub Code Review Agent`,category:`Code review`,description:`Watch for a configurable label on GitHub pull requests, inspect full PR and repository context, and post an AI review comment once per label event.`,requires:{integrations:{github:{message:`Used to read pull requests and post review comments.`}},features:[`repoClone`,`presetPrompt`]},popularityRank:100,estimatedSetupMinutes:4,exampleImplementation:`Trigger: cron polling for open GitHub PRs with a configured label such as openhands-review
+Required secret: GITHUB_PERSONAL_ACCESS_TOKEN
+
+1. Read repository, trigger label, review tone, and polling schedule from setup.
+2. List open PRs and find the latest matching GitHub labeled issue event for each labeled PR.
+3. Deduplicate on the label event ID so every label application queues exactly one review.
+4. Start an OpenHands conversation that clones the repo, checks out the exact PR head SHA, and inspects PR discussion, review comments, changed files, diff, and surrounding code.
+5. Post an acknowledgement with the conversation link, then post the final AI review comment only if the PR is still open and the head SHA has not changed.`,setup:{version:`1.0`,mode:`direct`,form:{triggers:{cron:{schedule:{type:`cron`,label:`Check frequency`,help:`How often to look for newly labelled pull requests.`,default:`*/15 * * * *`,required:!0},timezone:{type:`timezone`,label:`Timezone`,help:`Timezone the schedule is interpreted in.`,default:`UTC`,required:!0}}},args:{repository:{type:`repo-picker`,label:`Repository`,help:`The repository whose pull requests will be reviewed.`,provider:`github`,required:!0},triggerLabel:{type:`text`,label:`Trigger label`,help:`Only pull requests carrying this label are reviewed.`,default:`openhands-review`,required:!0,constraints:{minLength:1,maxLength:50}},reviewTone:{type:`select`,label:`Review tone`,help:`How detailed the review comments should be.`,default:`concise`,required:!0,options:[{value:`concise`,label:`Concise`},{value:`thorough`,label:`Thorough`}]}}},prompt:`Review pull requests labeled '{{form.triggerLabel}}' in {{form.repository}}. Review tone: {{form.reviewTone}}.`,message:`This deployment cannot run the scheduled review automation directly. Set it up in this conversation instead: confirm the repository to review, the trigger label, the review tone, and the polling schedule, then create the automation.`}};exports.default=e;
+//# sourceMappingURL=manifest.cjs.map

package/dist/node_modules/@openhands/extensions/automations/catalog/github-pr-reviewer/manifest.cjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"manifest.cjs","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/github-pr-reviewer/manifest.json"],"sourcesContent":["{\n  \"id\": \"github-pr-reviewer\",\n  \"name\": \"GitHub Code Review Agent\",\n  \"category\": \"Code review\",\n  \"description\": \"Watch for a configurable label on GitHub pull requests, inspect full PR and repository context, and post an AI review comment once per label event.\",\n  \"requires\": {\n    \"integrations\": {\n      \"github\": {\n        \"message\": \"Used to read pull requests and post review comments.\"\n      }\n    },\n    \"features\": [\n      \"repoClone\",\n      \"presetPrompt\"\n    ]\n  },\n  \"popularityRank\": 100,\n  \"estimatedSetupMinutes\": 4,\n  \"exampleImplementation\": \"Trigger: cron polling for open GitHub PRs with a configured label such as openhands-review\\nRequired secret: GITHUB_PERSONAL_ACCESS_TOKEN\\n\\n1. Read repository, trigger label, review tone, and polling schedule from setup.\\n2. List open PRs and find the latest matching GitHub labeled issue event for each labeled PR.\\n3. Deduplicate on the label event ID so every label application queues exactly one review.\\n4. Start an OpenHands conversation that clones the repo, checks out the exact PR head SHA, and inspects PR discussion, review comments, changed files, diff, and surrounding code.\\n5. Post an acknowledgement with the conversation link, then post the final AI review comment only if the PR is still open and the head SHA has not changed.\",\n  \"setup\": {\n    \"version\": \"1.0\",\n    \"mode\": \"direct\",\n    \"form\": {\n      \"triggers\": {\n        \"cron\": {\n          \"schedule\": {\n            \"type\": \"cron\",\n            \"label\": \"Check frequency\",\n            \"help\": \"How often to look for newly labelled pull requests.\",\n            \"default\": \"*/15 * * * *\",\n            \"required\": true\n          },\n          \"timezone\": {\n            \"type\": \"timezone\",\n            \"label\": \"Timezone\",\n            \"help\": \"Timezone the schedule is interpreted in.\",\n            \"default\": \"UTC\",\n            \"required\": true\n          }\n        }\n      },\n      \"args\": {\n        \"repository\": {\n          \"type\": \"repo-picker\",\n          \"label\": \"Repository\",\n          \"help\": \"The repository whose pull requests will be reviewed.\",\n          \"provider\": \"github\",\n          \"required\": true\n        },\n        \"triggerLabel\": {\n          \"type\": \"text\",\n          \"label\": \"Trigger label\",\n          \"help\": \"Only pull requests carrying this label are reviewed.\",\n          \"default\": \"openhands-review\",\n          \"required\": true,\n          \"constraints\": {\n            \"minLength\": 1,\n            \"maxLength\": 50\n          }\n        },\n        \"reviewTone\": {\n          \"type\": \"select\",\n          \"label\": \"Review tone\",\n          \"help\": \"How detailed the review comments should be.\",\n          \"default\": \"concise\",\n          \"required\": true,\n          \"options\": [\n            {\n              \"value\": \"concise\",\n              \"label\": \"Concise\"\n            },\n            {\n              \"value\": \"thorough\",\n              \"label\": \"Thorough\"\n            }\n          ]\n        }\n      }\n    },\n    \"prompt\": \"Review pull requests labeled '{{form.triggerLabel}}' in {{form.repository}}. Review tone: {{form.reviewTone}}.\",\n    \"message\": \"This deployment cannot run the scheduled review automation directly. Set it up in this conversation instead: confirm the repository to review, the trigger label, the review tone, and the polling schedule, then create the automation.\"\n  }\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/github-pr-reviewer/manifest.js

@@ -0,0 +1,75 @@
+var e = {
+	id: "github-pr-reviewer",
+	name: "GitHub Code Review Agent",
+	category: "Code review",
+	description: "Watch for a configurable label on GitHub pull requests, inspect full PR and repository context, and post an AI review comment once per label event.",
+	requires: {
+		integrations: { github: { message: "Used to read pull requests and post review comments." } },
+		features: ["repoClone", "presetPrompt"]
+	},
+	popularityRank: 100,
+	estimatedSetupMinutes: 4,
+	exampleImplementation: "Trigger: cron polling for open GitHub PRs with a configured label such as openhands-review\nRequired secret: GITHUB_PERSONAL_ACCESS_TOKEN\n\n1. Read repository, trigger label, review tone, and polling schedule from setup.\n2. List open PRs and find the latest matching GitHub labeled issue event for each labeled PR.\n3. Deduplicate on the label event ID so every label application queues exactly one review.\n4. Start an OpenHands conversation that clones the repo, checks out the exact PR head SHA, and inspects PR discussion, review comments, changed files, diff, and surrounding code.\n5. Post an acknowledgement with the conversation link, then post the final AI review comment only if the PR is still open and the head SHA has not changed.",
+	setup: {
+		version: "1.0",
+		mode: "direct",
+		form: {
+			triggers: { cron: {
+				schedule: {
+					type: "cron",
+					label: "Check frequency",
+					help: "How often to look for newly labelled pull requests.",
+					default: "*/15 * * * *",
+					required: !0
+				},
+				timezone: {
+					type: "timezone",
+					label: "Timezone",
+					help: "Timezone the schedule is interpreted in.",
+					default: "UTC",
+					required: !0
+				}
+			} },
+			args: {
+				repository: {
+					type: "repo-picker",
+					label: "Repository",
+					help: "The repository whose pull requests will be reviewed.",
+					provider: "github",
+					required: !0
+				},
+				triggerLabel: {
+					type: "text",
+					label: "Trigger label",
+					help: "Only pull requests carrying this label are reviewed.",
+					default: "openhands-review",
+					required: !0,
+					constraints: {
+						minLength: 1,
+						maxLength: 50
+					}
+				},
+				reviewTone: {
+					type: "select",
+					label: "Review tone",
+					help: "How detailed the review comments should be.",
+					default: "concise",
+					required: !0,
+					options: [{
+						value: "concise",
+						label: "Concise"
+					}, {
+						value: "thorough",
+						label: "Thorough"
+					}]
+				}
+			}
+		},
+		prompt: "Review pull requests labeled '{{form.triggerLabel}}' in {{form.repository}}. Review tone: {{form.reviewTone}}.",
+		message: "This deployment cannot run the scheduled review automation directly. Set it up in this conversation instead: confirm the repository to review, the trigger label, the review tone, and the polling schedule, then create the automation."
+	}
+};
+//#endregion
+export { e as default };
+
+//# sourceMappingURL=manifest.js.map

package/dist/node_modules/@openhands/extensions/automations/catalog/github-pr-reviewer/manifest.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"manifest.js","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/github-pr-reviewer/manifest.json"],"sourcesContent":["{\n  \"id\": \"github-pr-reviewer\",\n  \"name\": \"GitHub Code Review Agent\",\n  \"category\": \"Code review\",\n  \"description\": \"Watch for a configurable label on GitHub pull requests, inspect full PR and repository context, and post an AI review comment once per label event.\",\n  \"requires\": {\n    \"integrations\": {\n      \"github\": {\n        \"message\": \"Used to read pull requests and post review comments.\"\n      }\n    },\n    \"features\": [\n      \"repoClone\",\n      \"presetPrompt\"\n    ]\n  },\n  \"popularityRank\": 100,\n  \"estimatedSetupMinutes\": 4,\n  \"exampleImplementation\": \"Trigger: cron polling for open GitHub PRs with a configured label such as openhands-review\\nRequired secret: GITHUB_PERSONAL_ACCESS_TOKEN\\n\\n1. Read repository, trigger label, review tone, and polling schedule from setup.\\n2. List open PRs and find the latest matching GitHub labeled issue event for each labeled PR.\\n3. Deduplicate on the label event ID so every label application queues exactly one review.\\n4. Start an OpenHands conversation that clones the repo, checks out the exact PR head SHA, and inspects PR discussion, review comments, changed files, diff, and surrounding code.\\n5. Post an acknowledgement with the conversation link, then post the final AI review comment only if the PR is still open and the head SHA has not changed.\",\n  \"setup\": {\n    \"version\": \"1.0\",\n    \"mode\": \"direct\",\n    \"form\": {\n      \"triggers\": {\n        \"cron\": {\n          \"schedule\": {\n            \"type\": \"cron\",\n            \"label\": \"Check frequency\",\n            \"help\": \"How often to look for newly labelled pull requests.\",\n            \"default\": \"*/15 * * * *\",\n            \"required\": true\n          },\n          \"timezone\": {\n            \"type\": \"timezone\",\n            \"label\": \"Timezone\",\n            \"help\": \"Timezone the schedule is interpreted in.\",\n            \"default\": \"UTC\",\n            \"required\": true\n          }\n        }\n      },\n      \"args\": {\n        \"repository\": {\n          \"type\": \"repo-picker\",\n          \"label\": \"Repository\",\n          \"help\": \"The repository whose pull requests will be reviewed.\",\n          \"provider\": \"github\",\n          \"required\": true\n        },\n        \"triggerLabel\": {\n          \"type\": \"text\",\n          \"label\": \"Trigger label\",\n          \"help\": \"Only pull requests carrying this label are reviewed.\",\n          \"default\": \"openhands-review\",\n          \"required\": true,\n          \"constraints\": {\n            \"minLength\": 1,\n            \"maxLength\": 50\n          }\n        },\n        \"reviewTone\": {\n          \"type\": \"select\",\n          \"label\": \"Review tone\",\n          \"help\": \"How detailed the review comments should be.\",\n          \"default\": \"concise\",\n          \"required\": true,\n          \"options\": [\n            {\n              \"value\": \"concise\",\n              \"label\": \"Concise\"\n            },\n            {\n              \"value\": \"thorough\",\n              \"label\": \"Thorough\"\n            }\n          ]\n        }\n      }\n    },\n    \"prompt\": \"Review pull requests labeled '{{form.triggerLabel}}' in {{form.repository}}. Review tone: {{form.reviewTone}}.\",\n    \"message\": \"This deployment cannot run the scheduled review automation directly. Set it up in this conversation instead: confirm the repository to review, the trigger label, the review tone, and the polling schedule, then create the automation.\"\n  }\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/github-repo-monitor/manifest.cjs

@@ -0,0 +1,9 @@
+require("../../../../../../_virtual/_rolldown/runtime.cjs");var e={id:`github-repo-monitor`,name:`GitHub repository monitor`,category:`Developer tools`,description:`Watch a repository for @OpenHands mentions in issues and PR comments, start a conversation, and post the agent's reply back to GitHub.`,requires:{integrations:{github:{message:`Used to read issue and pull request comments and post replies.`}},features:[`repoClone`,`presetPrompt`,`webhookDelivery`]},popularityRank:98,estimatedSetupMinutes:5,exampleImplementation:`Trigger: cron, every minute (configurable)
+Required secret: GITHUB_PERSONAL_ACCESS_TOKEN
+
+1. Poll GitHub for new issue and PR comments since the last run.
+2. Match comments containing the trigger phrase (case-insensitive, default: @OpenHands).
+3. Post an acknowledgment comment with a link to the new OpenHands conversation.
+4. Forward follow-up replies in the same thread to the running conversation.
+5. Post the agent's final response back to GitHub when the conversation completes.`,setup:{version:`1.0`,mode:`direct`,form:{triggers:{event:{on:{type:`select`,label:`Respond to`,help:`Which GitHub comment event starts a conversation.`,default:`issue_comment.created`,required:!0,options:[{value:`issue_comment.created`,label:`Comments on issues and pull requests`},{value:`pull_request_review_comment.created`,label:`Pull request review comments only`}]},triggerPhrase:{type:`text`,label:`Trigger phrase`,help:`Only comments containing this phrase start a conversation. Matched case-insensitively. Quotes and backslashes are not allowed, because the phrase becomes part of the event filter expression.`,default:`@openhands`,required:!0,constraints:{minLength:2,maxLength:50,format:`safeExpressionLiteral`}}}},args:{repository:{type:`repo-picker`,label:`Repository`,help:`The repository or repositories to watch for mentions.`,provider:`github`,required:!0},ref:{type:`text`,label:`Base branch`,help:`Branch checked out when the agent responds.`,default:`main`,required:!0,constraints:{minLength:1,maxLength:255}}}},prompt:`A comment in {{form.repository}} mentions '{{form.triggerPhrase}}'. Read the surrounding issue or pull request context from the event payload, then post a helpful reply as a comment on the same thread.`,filter:`icontains(comment.body, '{{form.triggerPhrase}}') && glob(repository.full_name, '{{form.repository}}')`,message:`This deployment cannot run the webhook-driven monitor directly. Set it up in this conversation instead: confirm the repository to watch, the comment event, and the trigger phrase, then create the automation. If webhook delivery is unavailable here, build the polling variant this skill supports.`}};exports.default=e;
+//# sourceMappingURL=manifest.cjs.map

package/dist/node_modules/@openhands/extensions/automations/catalog/github-repo-monitor/manifest.cjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"manifest.cjs","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/github-repo-monitor/manifest.json"],"sourcesContent":["{\n  \"id\": \"github-repo-monitor\",\n  \"name\": \"GitHub repository monitor\",\n  \"category\": \"Developer tools\",\n  \"description\": \"Watch a repository for @OpenHands mentions in issues and PR comments, start a conversation, and post the agent's reply back to GitHub.\",\n  \"requires\": {\n    \"integrations\": {\n      \"github\": {\n        \"message\": \"Used to read issue and pull request comments and post replies.\"\n      }\n    },\n    \"features\": [\n      \"repoClone\",\n      \"presetPrompt\",\n      \"webhookDelivery\"\n    ]\n  },\n  \"popularityRank\": 98,\n  \"estimatedSetupMinutes\": 5,\n  \"exampleImplementation\": \"Trigger: cron, every minute (configurable)\\nRequired secret: GITHUB_PERSONAL_ACCESS_TOKEN\\n\\n1. Poll GitHub for new issue and PR comments since the last run.\\n2. Match comments containing the trigger phrase (case-insensitive, default: @OpenHands).\\n3. Post an acknowledgment comment with a link to the new OpenHands conversation.\\n4. Forward follow-up replies in the same thread to the running conversation.\\n5. Post the agent's final response back to GitHub when the conversation completes.\",\n  \"setup\": {\n    \"version\": \"1.0\",\n    \"mode\": \"direct\",\n    \"form\": {\n      \"triggers\": {\n        \"event\": {\n          \"on\": {\n            \"type\": \"select\",\n            \"label\": \"Respond to\",\n            \"help\": \"Which GitHub comment event starts a conversation.\",\n            \"default\": \"issue_comment.created\",\n            \"required\": true,\n            \"options\": [\n              {\n                \"value\": \"issue_comment.created\",\n                \"label\": \"Comments on issues and pull requests\"\n              },\n              {\n                \"value\": \"pull_request_review_comment.created\",\n                \"label\": \"Pull request review comments only\"\n              }\n            ]\n          },\n          \"triggerPhrase\": {\n            \"type\": \"text\",\n            \"label\": \"Trigger phrase\",\n            \"help\": \"Only comments containing this phrase start a conversation. Matched case-insensitively. Quotes and backslashes are not allowed, because the phrase becomes part of the event filter expression.\",\n            \"default\": \"@openhands\",\n            \"required\": true,\n            \"constraints\": {\n              \"minLength\": 2,\n              \"maxLength\": 50,\n              \"format\": \"safeExpressionLiteral\"\n            }\n          }\n        }\n      },\n      \"args\": {\n        \"repository\": {\n          \"type\": \"repo-picker\",\n          \"label\": \"Repository\",\n          \"help\": \"The repository or repositories to watch for mentions.\",\n          \"provider\": \"github\",\n          \"required\": true\n        },\n        \"ref\": {\n          \"type\": \"text\",\n          \"label\": \"Base branch\",\n          \"help\": \"Branch checked out when the agent responds.\",\n          \"default\": \"main\",\n          \"required\": true,\n          \"constraints\": {\n            \"minLength\": 1,\n            \"maxLength\": 255\n          }\n        }\n      }\n    },\n    \"prompt\": \"A comment in {{form.repository}} mentions '{{form.triggerPhrase}}'. Read the surrounding issue or pull request context from the event payload, then post a helpful reply as a comment on the same thread.\",\n    \"filter\": \"icontains(comment.body, '{{form.triggerPhrase}}') && glob(repository.full_name, '{{form.repository}}')\",\n    \"message\": \"This deployment cannot run the webhook-driven monitor directly. Set it up in this conversation instead: confirm the repository to watch, the comment event, and the trigger phrase, then create the automation. If webhook delivery is unavailable here, build the polling variant this skill supports.\"\n  }\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/github-repo-monitor/manifest.js

@@ -0,0 +1,78 @@
+var e = {
+	id: "github-repo-monitor",
+	name: "GitHub repository monitor",
+	category: "Developer tools",
+	description: "Watch a repository for @OpenHands mentions in issues and PR comments, start a conversation, and post the agent's reply back to GitHub.",
+	requires: {
+		integrations: { github: { message: "Used to read issue and pull request comments and post replies." } },
+		features: [
+			"repoClone",
+			"presetPrompt",
+			"webhookDelivery"
+		]
+	},
+	popularityRank: 98,
+	estimatedSetupMinutes: 5,
+	exampleImplementation: "Trigger: cron, every minute (configurable)\nRequired secret: GITHUB_PERSONAL_ACCESS_TOKEN\n\n1. Poll GitHub for new issue and PR comments since the last run.\n2. Match comments containing the trigger phrase (case-insensitive, default: @OpenHands).\n3. Post an acknowledgment comment with a link to the new OpenHands conversation.\n4. Forward follow-up replies in the same thread to the running conversation.\n5. Post the agent's final response back to GitHub when the conversation completes.",
+	setup: {
+		version: "1.0",
+		mode: "direct",
+		form: {
+			triggers: { event: {
+				on: {
+					type: "select",
+					label: "Respond to",
+					help: "Which GitHub comment event starts a conversation.",
+					default: "issue_comment.created",
+					required: !0,
+					options: [{
+						value: "issue_comment.created",
+						label: "Comments on issues and pull requests"
+					}, {
+						value: "pull_request_review_comment.created",
+						label: "Pull request review comments only"
+					}]
+				},
+				triggerPhrase: {
+					type: "text",
+					label: "Trigger phrase",
+					help: "Only comments containing this phrase start a conversation. Matched case-insensitively. Quotes and backslashes are not allowed, because the phrase becomes part of the event filter expression.",
+					default: "@openhands",
+					required: !0,
+					constraints: {
+						minLength: 2,
+						maxLength: 50,
+						format: "safeExpressionLiteral"
+					}
+				}
+			} },
+			args: {
+				repository: {
+					type: "repo-picker",
+					label: "Repository",
+					help: "The repository or repositories to watch for mentions.",
+					provider: "github",
+					required: !0
+				},
+				ref: {
+					type: "text",
+					label: "Base branch",
+					help: "Branch checked out when the agent responds.",
+					default: "main",
+					required: !0,
+					constraints: {
+						minLength: 1,
+						maxLength: 255
+					}
+				}
+			}
+		},
+		prompt: "A comment in {{form.repository}} mentions '{{form.triggerPhrase}}'. Read the surrounding issue or pull request context from the event payload, then post a helpful reply as a comment on the same thread.",
+		filter: "icontains(comment.body, '{{form.triggerPhrase}}') && glob(repository.full_name, '{{form.repository}}')",
+		message: "This deployment cannot run the webhook-driven monitor directly. Set it up in this conversation instead: confirm the repository to watch, the comment event, and the trigger phrase, then create the automation. If webhook delivery is unavailable here, build the polling variant this skill supports."
+	}
+};
+//#endregion
+export { e as default };
+
+//# sourceMappingURL=manifest.js.map

package/dist/node_modules/@openhands/extensions/automations/catalog/github-repo-monitor/manifest.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"manifest.js","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/github-repo-monitor/manifest.json"],"sourcesContent":["{\n  \"id\": \"github-repo-monitor\",\n  \"name\": \"GitHub repository monitor\",\n  \"category\": \"Developer tools\",\n  \"description\": \"Watch a repository for @OpenHands mentions in issues and PR comments, start a conversation, and post the agent's reply back to GitHub.\",\n  \"requires\": {\n    \"integrations\": {\n      \"github\": {\n        \"message\": \"Used to read issue and pull request comments and post replies.\"\n      }\n    },\n    \"features\": [\n      \"repoClone\",\n      \"presetPrompt\",\n      \"webhookDelivery\"\n    ]\n  },\n  \"popularityRank\": 98,\n  \"estimatedSetupMinutes\": 5,\n  \"exampleImplementation\": \"Trigger: cron, every minute (configurable)\\nRequired secret: GITHUB_PERSONAL_ACCESS_TOKEN\\n\\n1. Poll GitHub for new issue and PR comments since the last run.\\n2. Match comments containing the trigger phrase (case-insensitive, default: @OpenHands).\\n3. Post an acknowledgment comment with a link to the new OpenHands conversation.\\n4. Forward follow-up replies in the same thread to the running conversation.\\n5. Post the agent's final response back to GitHub when the conversation completes.\",\n  \"setup\": {\n    \"version\": \"1.0\",\n    \"mode\": \"direct\",\n    \"form\": {\n      \"triggers\": {\n        \"event\": {\n          \"on\": {\n            \"type\": \"select\",\n            \"label\": \"Respond to\",\n            \"help\": \"Which GitHub comment event starts a conversation.\",\n            \"default\": \"issue_comment.created\",\n            \"required\": true,\n            \"options\": [\n              {\n                \"value\": \"issue_comment.created\",\n                \"label\": \"Comments on issues and pull requests\"\n              },\n              {\n                \"value\": \"pull_request_review_comment.created\",\n                \"label\": \"Pull request review comments only\"\n              }\n            ]\n          },\n          \"triggerPhrase\": {\n            \"type\": \"text\",\n            \"label\": \"Trigger phrase\",\n            \"help\": \"Only comments containing this phrase start a conversation. Matched case-insensitively. Quotes and backslashes are not allowed, because the phrase becomes part of the event filter expression.\",\n            \"default\": \"@openhands\",\n            \"required\": true,\n            \"constraints\": {\n              \"minLength\": 2,\n              \"maxLength\": 50,\n              \"format\": \"safeExpressionLiteral\"\n            }\n          }\n        }\n      },\n      \"args\": {\n        \"repository\": {\n          \"type\": \"repo-picker\",\n          \"label\": \"Repository\",\n          \"help\": \"The repository or repositories to watch for mentions.\",\n          \"provider\": \"github\",\n          \"required\": true\n        },\n        \"ref\": {\n          \"type\": \"text\",\n          \"label\": \"Base branch\",\n          \"help\": \"Branch checked out when the agent responds.\",\n          \"default\": \"main\",\n          \"required\": true,\n          \"constraints\": {\n            \"minLength\": 1,\n            \"maxLength\": 255\n          }\n        }\n      }\n    },\n    \"prompt\": \"A comment in {{form.repository}} mentions '{{form.triggerPhrase}}'. Read the surrounding issue or pull request context from the event payload, then post a helpful reply as a comment on the same thread.\",\n    \"filter\": \"icontains(comment.body, '{{form.triggerPhrase}}') && glob(repository.full_name, '{{form.repository}}')\",\n    \"message\": \"This deployment cannot run the webhook-driven monitor directly. Set it up in this conversation instead: confirm the repository to watch, the comment event, and the trigger phrase, then create the automation. If webhook delivery is unavailable here, build the polling variant this skill supports.\"\n  }\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/incident-retrospective-drafter/manifest.cjs

@@ -0,0 +1,17 @@
+require("../../../../../../_virtual/_rolldown/runtime.cjs");var e={id:`incident-retrospective-drafter`,name:`Incident retrospective drafter`,category:`Reliability`,description:`Collect incident chatter and issue updates, then draft a timeline and follow-up checklist.`,requires:{integrations:{slack:{message:`Reads incident discussion and timestamps.`},linear:{message:`Reads follow-up tickets, owners, and status.`},notion:{message:`Publishes the drafted retrospective. Can be connected later during setup.`,required:!1}},features:[`mcpTools`,`conversationDispatch`]},popularityRank:78,estimatedSetupMinutes:8,skill:`incident-retrospective`,exampleImplementation:`Trigger: manual, cron, or incident label added
+Required MCPs: Slack, Linear, Notion
+
+1. Gather incident messages, timestamps, and linked issue references.
+2. Pull Linear follow-up tickets, owners, and status.
+3. TODO: define the incident identifier format and approved Notion template.
+4. Build a timeline, impact summary, root-cause hypotheses, and action items.
+5. Publish a draft retrospective and notify the incident owner.`,setup:{version:`1.0`,mode:`assisted`,form:{note:`These answers start the conversation. Anything left blank is something the agent will ask about.`,args:{incidentChannel:{type:`text`,label:`Incident channel`,help:`The Slack channel where incidents are discussed.`,placeholder:`#incidents`,required:!1,constraints:{maxLength:100}},linearTeam:{type:`text`,label:`Linear team`,help:`The team whose follow-up tickets belong in the retrospective.`,required:!1,constraints:{maxLength:100}},notionDestination:{type:`text`,label:`Notion destination`,help:`Page or database where drafts should be published. Leave blank to decide during setup.`,required:!1,constraints:{maxLength:200}},triggerPreference:{type:`select`,label:`How should it run?`,help:`A starting preference only. The agent confirms the exact trigger before creating anything.`,default:`undecided`,required:!1,options:[{value:`undecided`,label:`Let the agent recommend one`},{value:`scheduled`,label:`On a schedule`},{value:`onIncidentLabel`,label:`When an incident is labelled`},{value:`manual`,label:`Only when I run it`}]},notes:{type:`textarea`,label:`Anything else the agent should know?`,help:`Incident naming conventions, an existing retro template, who should be notified.`,required:!1,constraints:{maxLength:2e3}}}},message:`The user supplied these starting points. Confirm each one, ask about anything left blank, then create the automation.
+
+- Incident channel: {{form.incidentChannel}}
+- Linear team: {{form.linearTeam}}
+- Notion destination: {{form.notionDestination}}
+- Preferred trigger: {{form.triggerPreference}}
+- Notes: {{form.notes}}
+
+Still undecided and required before creation: the incident identifier format and the approved Notion retrospective template.`}};exports.default=e;
+//# sourceMappingURL=manifest.cjs.map

package/dist/node_modules/@openhands/extensions/automations/catalog/incident-retrospective-drafter/manifest.cjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"manifest.cjs","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/incident-retrospective-drafter/manifest.json"],"sourcesContent":["{\n  \"id\": \"incident-retrospective-drafter\",\n  \"name\": \"Incident retrospective drafter\",\n  \"category\": \"Reliability\",\n  \"description\": \"Collect incident chatter and issue updates, then draft a timeline and follow-up checklist.\",\n  \"requires\": {\n    \"integrations\": {\n      \"slack\": {\n        \"message\": \"Reads incident discussion and timestamps.\"\n      },\n      \"linear\": {\n        \"message\": \"Reads follow-up tickets, owners, and status.\"\n      },\n      \"notion\": {\n        \"message\": \"Publishes the drafted retrospective. Can be connected later during setup.\",\n        \"required\": false\n      }\n    },\n    \"features\": [\n      \"mcpTools\",\n      \"conversationDispatch\"\n    ]\n  },\n  \"popularityRank\": 78,\n  \"estimatedSetupMinutes\": 8,\n  \"skill\": \"incident-retrospective\",\n  \"exampleImplementation\": \"Trigger: manual, cron, or incident label added\\nRequired MCPs: Slack, Linear, Notion\\n\\n1. Gather incident messages, timestamps, and linked issue references.\\n2. Pull Linear follow-up tickets, owners, and status.\\n3. TODO: define the incident identifier format and approved Notion template.\\n4. Build a timeline, impact summary, root-cause hypotheses, and action items.\\n5. Publish a draft retrospective and notify the incident owner.\",\n  \"setup\": {\n    \"version\": \"1.0\",\n    \"mode\": \"assisted\",\n    \"form\": {\n      \"note\": \"These answers start the conversation. Anything left blank is something the agent will ask about.\",\n      \"args\": {\n        \"incidentChannel\": {\n          \"type\": \"text\",\n          \"label\": \"Incident channel\",\n          \"help\": \"The Slack channel where incidents are discussed.\",\n          \"placeholder\": \"#incidents\",\n          \"required\": false,\n          \"constraints\": {\n            \"maxLength\": 100\n          }\n        },\n        \"linearTeam\": {\n          \"type\": \"text\",\n          \"label\": \"Linear team\",\n          \"help\": \"The team whose follow-up tickets belong in the retrospective.\",\n          \"required\": false,\n          \"constraints\": {\n            \"maxLength\": 100\n          }\n        },\n        \"notionDestination\": {\n          \"type\": \"text\",\n          \"label\": \"Notion destination\",\n          \"help\": \"Page or database where drafts should be published. Leave blank to decide during setup.\",\n          \"required\": false,\n          \"constraints\": {\n            \"maxLength\": 200\n          }\n        },\n        \"triggerPreference\": {\n          \"type\": \"select\",\n          \"label\": \"How should it run?\",\n          \"help\": \"A starting preference only. The agent confirms the exact trigger before creating anything.\",\n          \"default\": \"undecided\",\n          \"required\": false,\n          \"options\": [\n            {\n              \"value\": \"undecided\",\n              \"label\": \"Let the agent recommend one\"\n            },\n            {\n              \"value\": \"scheduled\",\n              \"label\": \"On a schedule\"\n            },\n            {\n              \"value\": \"onIncidentLabel\",\n              \"label\": \"When an incident is labelled\"\n            },\n            {\n              \"value\": \"manual\",\n              \"label\": \"Only when I run it\"\n            }\n          ]\n        },\n        \"notes\": {\n          \"type\": \"textarea\",\n          \"label\": \"Anything else the agent should know?\",\n          \"help\": \"Incident naming conventions, an existing retro template, who should be notified.\",\n          \"required\": false,\n          \"constraints\": {\n            \"maxLength\": 2000\n          }\n        }\n      }\n    },\n    \"message\": \"The user supplied these starting points. Confirm each one, ask about anything left blank, then create the automation.\\n\\n- Incident channel: {{form.incidentChannel}}\\n- Linear team: {{form.linearTeam}}\\n- Notion destination: {{form.notionDestination}}\\n- Preferred trigger: {{form.triggerPreference}}\\n- Notes: {{form.notes}}\\n\\nStill undecided and required before creation: the incident identifier format and the approved Notion retrospective template.\"\n  }\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/incident-retrospective-drafter/manifest.js

@@ -0,0 +1,89 @@
+var e = {
+	id: "incident-retrospective-drafter",
+	name: "Incident retrospective drafter",
+	category: "Reliability",
+	description: "Collect incident chatter and issue updates, then draft a timeline and follow-up checklist.",
+	requires: {
+		integrations: {
+			slack: { message: "Reads incident discussion and timestamps." },
+			linear: { message: "Reads follow-up tickets, owners, and status." },
+			notion: {
+				message: "Publishes the drafted retrospective. Can be connected later during setup.",
+				required: !1
+			}
+		},
+		features: ["mcpTools", "conversationDispatch"]
+	},
+	popularityRank: 78,
+	estimatedSetupMinutes: 8,
+	skill: "incident-retrospective",
+	exampleImplementation: "Trigger: manual, cron, or incident label added\nRequired MCPs: Slack, Linear, Notion\n\n1. Gather incident messages, timestamps, and linked issue references.\n2. Pull Linear follow-up tickets, owners, and status.\n3. TODO: define the incident identifier format and approved Notion template.\n4. Build a timeline, impact summary, root-cause hypotheses, and action items.\n5. Publish a draft retrospective and notify the incident owner.",
+	setup: {
+		version: "1.0",
+		mode: "assisted",
+		form: {
+			note: "These answers start the conversation. Anything left blank is something the agent will ask about.",
+			args: {
+				incidentChannel: {
+					type: "text",
+					label: "Incident channel",
+					help: "The Slack channel where incidents are discussed.",
+					placeholder: "#incidents",
+					required: !1,
+					constraints: { maxLength: 100 }
+				},
+				linearTeam: {
+					type: "text",
+					label: "Linear team",
+					help: "The team whose follow-up tickets belong in the retrospective.",
+					required: !1,
+					constraints: { maxLength: 100 }
+				},
+				notionDestination: {
+					type: "text",
+					label: "Notion destination",
+					help: "Page or database where drafts should be published. Leave blank to decide during setup.",
+					required: !1,
+					constraints: { maxLength: 200 }
+				},
+				triggerPreference: {
+					type: "select",
+					label: "How should it run?",
+					help: "A starting preference only. The agent confirms the exact trigger before creating anything.",
+					default: "undecided",
+					required: !1,
+					options: [
+						{
+							value: "undecided",
+							label: "Let the agent recommend one"
+						},
+						{
+							value: "scheduled",
+							label: "On a schedule"
+						},
+						{
+							value: "onIncidentLabel",
+							label: "When an incident is labelled"
+						},
+						{
+							value: "manual",
+							label: "Only when I run it"
+						}
+					]
+				},
+				notes: {
+					type: "textarea",
+					label: "Anything else the agent should know?",
+					help: "Incident naming conventions, an existing retro template, who should be notified.",
+					required: !1,
+					constraints: { maxLength: 2e3 }
+				}
+			}
+		},
+		message: "The user supplied these starting points. Confirm each one, ask about anything left blank, then create the automation.\n\n- Incident channel: {{form.incidentChannel}}\n- Linear team: {{form.linearTeam}}\n- Notion destination: {{form.notionDestination}}\n- Preferred trigger: {{form.triggerPreference}}\n- Notes: {{form.notes}}\n\nStill undecided and required before creation: the incident identifier format and the approved Notion retrospective template."
+	}
+};
+//#endregion
+export { e as default };
+
+//# sourceMappingURL=manifest.js.map

package/dist/node_modules/@openhands/extensions/automations/catalog/incident-retrospective-drafter/manifest.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"manifest.js","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/incident-retrospective-drafter/manifest.json"],"sourcesContent":["{\n  \"id\": \"incident-retrospective-drafter\",\n  \"name\": \"Incident retrospective drafter\",\n  \"category\": \"Reliability\",\n  \"description\": \"Collect incident chatter and issue updates, then draft a timeline and follow-up checklist.\",\n  \"requires\": {\n    \"integrations\": {\n      \"slack\": {\n        \"message\": \"Reads incident discussion and timestamps.\"\n      },\n      \"linear\": {\n        \"message\": \"Reads follow-up tickets, owners, and status.\"\n      },\n      \"notion\": {\n        \"message\": \"Publishes the drafted retrospective. Can be connected later during setup.\",\n        \"required\": false\n      }\n    },\n    \"features\": [\n      \"mcpTools\",\n      \"conversationDispatch\"\n    ]\n  },\n  \"popularityRank\": 78,\n  \"estimatedSetupMinutes\": 8,\n  \"skill\": \"incident-retrospective\",\n  \"exampleImplementation\": \"Trigger: manual, cron, or incident label added\\nRequired MCPs: Slack, Linear, Notion\\n\\n1. Gather incident messages, timestamps, and linked issue references.\\n2. Pull Linear follow-up tickets, owners, and status.\\n3. TODO: define the incident identifier format and approved Notion template.\\n4. Build a timeline, impact summary, root-cause hypotheses, and action items.\\n5. Publish a draft retrospective and notify the incident owner.\",\n  \"setup\": {\n    \"version\": \"1.0\",\n    \"mode\": \"assisted\",\n    \"form\": {\n      \"note\": \"These answers start the conversation. Anything left blank is something the agent will ask about.\",\n      \"args\": {\n        \"incidentChannel\": {\n          \"type\": \"text\",\n          \"label\": \"Incident channel\",\n          \"help\": \"The Slack channel where incidents are discussed.\",\n          \"placeholder\": \"#incidents\",\n          \"required\": false,\n          \"constraints\": {\n            \"maxLength\": 100\n          }\n        },\n        \"linearTeam\": {\n          \"type\": \"text\",\n          \"label\": \"Linear team\",\n          \"help\": \"The team whose follow-up tickets belong in the retrospective.\",\n          \"required\": false,\n          \"constraints\": {\n            \"maxLength\": 100\n          }\n        },\n        \"notionDestination\": {\n          \"type\": \"text\",\n          \"label\": \"Notion destination\",\n          \"help\": \"Page or database where drafts should be published. Leave blank to decide during setup.\",\n          \"required\": false,\n          \"constraints\": {\n            \"maxLength\": 200\n          }\n        },\n        \"triggerPreference\": {\n          \"type\": \"select\",\n          \"label\": \"How should it run?\",\n          \"help\": \"A starting preference only. The agent confirms the exact trigger before creating anything.\",\n          \"default\": \"undecided\",\n          \"required\": false,\n          \"options\": [\n            {\n              \"value\": \"undecided\",\n              \"label\": \"Let the agent recommend one\"\n            },\n            {\n              \"value\": \"scheduled\",\n              \"label\": \"On a schedule\"\n            },\n            {\n              \"value\": \"onIncidentLabel\",\n              \"label\": \"When an incident is labelled\"\n            },\n            {\n              \"value\": \"manual\",\n              \"label\": \"Only when I run it\"\n            }\n          ]\n        },\n        \"notes\": {\n          \"type\": \"textarea\",\n          \"label\": \"Anything else the agent should know?\",\n          \"help\": \"Incident naming conventions, an existing retro template, who should be notified.\",\n          \"required\": false,\n          \"constraints\": {\n            \"maxLength\": 2000\n          }\n        }\n      }\n    },\n    \"message\": \"The user supplied these starting points. Confirm each one, ask about anything left blank, then create the automation.\\n\\n- Incident channel: {{form.incidentChannel}}\\n- Linear team: {{form.linearTeam}}\\n- Notion destination: {{form.notionDestination}}\\n- Preferred trigger: {{form.triggerPreference}}\\n- Notes: {{form.notes}}\\n\\nStill undecided and required before creation: the incident identifier format and the approved Notion retrospective template.\"\n  }\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/jira-issue-to-pr/manifest.cjs

@@ -0,0 +1,10 @@
+require("../../../../../../_virtual/_rolldown/runtime.cjs");var e={id:`jira-issue-to-pr`,name:`Jira issue to GitHub PR`,category:`Project management`,description:`Watch a Jira Cloud project for issues with a configurable label and automatically open a GitHub pull request for each new issue found. The target GitHub repo is read from the ticket body - no repo parameter required at deploy time.`,requires:{integrations:{jira:{message:`Reads the project for issues carrying the trigger label.`},github:{message:`Opens a pull request on the repository named in the ticket.`}}},popularityRank:85,estimatedSetupMinutes:5,exampleImplementation:`Trigger: cron polling (e.g. every 5 minutes)
+Required secrets: Jira API token, GitHub personal access token (repo + workflow scope)
+
+1. Collect Jira base URL, email, API token secret name, label to watch, and cron schedule from the user. No GitHub repo is needed at deploy time - each ticket must include the target repo (owner/repo) in its body.
+2. Poll POST /rest/api/3/search/jql on the Jira Cloud instance to find open issues carrying the configured label.
+3. Deduplicate against a KV-store-backed set of already-processed issue keys so re-runs never create duplicate PRs.
+4. For each new issue, start an independent OpenHands agent conversation that extracts the GitHub repo from the ticket body, clones it, creates a branch named after the Jira key, implements or scaffolds the requested change, and opens a pull request.
+5. Immediately after the conversation is created, post a Jira comment on the issue: 'I'm on it: <conversation URL>'.
+6. Persist the processed issue key immediately after dispatching so the next poll skips it.`};exports.default=e;
+//# sourceMappingURL=manifest.cjs.map