@openhands/extensions 0.31.0 → 0.32.1

package/.claude-plugin/marketplace.json

@@ -97,6 +97,7 @@
       "source": "./skills/software-factory",
       "description": "Set up a GitHub software factory fast: ask only for the repositories and the ticket source (GitHub issues, Jira or Linear), create a working issue-to-PR and PR-review pipeline from catalog automations with defaults, then let the user stop or extend it step by step.",
       "category": "automations",
+      "defaultEnabled": true,
       "keywords": [
         "onboarding",
         "software-factory",

package/.codex-plugin/marketplace.json

@@ -97,6 +97,7 @@
       "source": "./skills/software-factory",
       "description": "Set up a GitHub software factory fast: ask only for the repositories and the ticket source (GitHub issues, Jira or Linear), create a working issue-to-PR and PR-review pipeline from catalog automations with defaults, then let the user stop or extend it step by step.",
       "category": "automations",
+      "defaultEnabled": true,
       "keywords": [
         "onboarding",
         "software-factory",

package/.plugin/marketplace.json

@@ -97,6 +97,7 @@
       "source": "./skills/software-factory",
       "description": "Set up a GitHub software factory fast: ask only for the repositories and the ticket source (GitHub issues, Jira or Linear), create a working issue-to-PR and PR-review pipeline from catalog automations with defaults, then let the user stop or extend it step by step.",
       "category": "automations",
+      "defaultEnabled": true,
       "keywords": [
         "onboarding",
         "software-factory",

package/.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "0.31.0"
+  ".": "0.32.1"
 }

package/automations/README.md

@@ -42,7 +42,7 @@ two records of the same fact from drifting apart, and it is why the file is as s
 | The setup route | `/automations/new/<id>` |
 | The integrations the card lists | `requires.integrations`, which every entry carries |
 | The capabilities endpoint | The host queries it for every automation |
-| The trigger variants a deployment can offer | The keys of `setup.form.triggers`; an entry with multiple keys is usable when at least one variant is supported |
+| The trigger variants a deployment can offer | The keys of `setup.form.triggers`; an entry with multiple keys is usable when at least one variant is supported. An entry without a setup form states its kind in `triggers` instead |
 | Schedule limits, timezone list, event choices, and model profiles | The `cron`, `timezone`, `event-source`, `event-type`, and `llm-profile` field types |
 | Local validation rules | The `required` flag and `constraints` on each field, applied to the selected trigger variant |
 | The preflight call | `POST /v1/validate` with the entry id, the create endpoint, and the rendered payload |
@@ -101,6 +101,12 @@ That way a skill can rename its trigger without leaving a stale copy behind in t
 `setup` is optional. Entries that carry one never repeat `id`, `name`, `category`, or `description`.
 `setup.version` selects how the block is interpreted; a future format ships a new constant.
 
+`triggers` is stated only by an entry whose setup does not declare `form.triggers`, which otherwise already
+names the variants: `cron`, `event`, or both, describing how the automation runs once it has been set up.
+An entry lists both when its skill can set up either, for example an event trigger on a deployment that can
+receive events and cron polling elsewhere. Agent Canvas renders it as the card's trigger badge and filter.
+The schema rejects an entry that states it both ways, so the fact stays in one place.
+
 ### Triggers and args
 
 `form` separates the two things a user is configuring, and both are keyed by field name:
@@ -115,7 +121,8 @@ That way a skill can rename its trigger without leaving a stale copy behind in t
   the endpoint implied by the action key: `prompt` -> `/v1/preset/prompt`, `plugin` -> `/v1/preset/plugin`,
   and `upload` -> `/v1/uploads` followed by `/v1`.
 
-An assisted entry declares no triggers, because the trigger is settled during the conversation.
+An assisted entry declares no `form.triggers`, because the trigger is settled during the conversation. It may
+still list the kinds that conversation can set up in the top-level `triggers`.
 
 ### What the form produces