@openhands/extensions 0.13.0 → 0.14.0

package/.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "0.13.0"
+  ".": "0.14.0"
 }

package/README.md

@@ -89,7 +89,7 @@ The JS and Python versions are kept in lock-step by `release-please` and guarded
 ## Extensions Catalog
 
 <!-- BEGIN AUTO-GENERATED CATALOG -->
-This repository contains **2 marketplace(s)** with **63 extensions** (53 skills, 10 plugins).
+This repository contains **2 marketplace(s)** with **64 extensions** (54 skills, 10 plugins).
 
 ### large-codebase
 
@@ -108,7 +108,7 @@ OpenHands skills for interacting, improving, and refactoring large codebases
 
 Official skills and plugins for OpenHands — the open-source AI software engineer.
 
-**59 extensions** (51 skills, 8 plugins)
+**60 extensions** (52 skills, 8 plugins)
 
 | Name | Type | Description | Commands |
 |------|------|-------------|----------|
@@ -168,6 +168,7 @@ Official skills and plugins for OpenHands — the open-source AI software engine
 | swift-linux | skill | Install and configure Swift programming language on Debian Linux for server-side development. Use when building Swift... | — |
 | technical-writing | skill | Write and revise technical explanations in flowing, direct, conversational prose that stays concise without becoming ... | — |
 | theme-factory | skill | Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc.... | — |
+| upstream-fork-sync | skill | Keep a long-lived fork in sync with its upstream. Creates a cron automation that fetches upstream changes, rebases lo... | `/upstream-fork-sync:setup` |
 | uv | skill | Common project, dependency, and environment operations using uv. | — |
 | vercel | skill | Deploy and manage applications on Vercel, including preview deployments and deployment protection. | — |
 | vulnerability-remediation | plugin | Automated security vulnerability scanning and AI-powered remediation. Scans repositories, skips when no issues found,... | — |

package/automations/catalog/upstream-fork-sync/manifest.json

@@ -0,0 +1,85 @@
+{
+  "id": "upstream-fork-sync",
+  "name": "Upstream fork sync",
+  "category": "Developer tools",
+  "description": "Keep a long-lived fork current with its upstream by re-running a nightly job that fetches upstream changes, rebases local customizations on top, verifies the software still works, and replaces the running version when it does.",
+  "requires": {
+    "integrations": {
+      "github": {
+        "message": "Used to fetch upstream changes and push the rebased fork."
+      }
+    },
+    "features": [
+      "repoClone",
+      "presetPrompt"
+    ]
+  },
+  "popularityRank": 80,
+  "estimatedSetupMinutes": 4,
+  "exampleImplementation": "Trigger: cron, nightly (configurable)\nRequired secret: GITHUB_PERSONAL_ACCESS_TOKEN\n\n1. Clone the fork repository and fetch the latest from its upstream remote.\n2. Rebase every local customization commit on top of the newest upstream HEAD.\n3. Run the configured verification command to confirm the software works as intended.\n4. If verification passes, force-push the rebased branch and replace the currently deployed version with the freshly built one.\n5. If verification fails, leave the running version untouched and report the conflict.",
+  "setup": {
+    "version": "1.0",
+    "mode": "direct",
+    "form": {
+      "triggers": {
+        "cron": {
+          "schedule": {
+            "type": "cron",
+            "label": "Sync schedule",
+            "help": "How often to fetch upstream and rebase local changes. Nightly is the default.",
+            "default": "0 3 * * *",
+            "required": true
+          },
+          "timezone": {
+            "type": "timezone",
+            "label": "Timezone",
+            "help": "Timezone the schedule is interpreted in.",
+            "default": "UTC",
+            "required": true
+          }
+        }
+      },
+      "args": {
+        "repository": {
+          "type": "repo-picker",
+          "label": "Repository",
+          "help": "The long-lived fork to keep synchronized with upstream.",
+          "provider": "github",
+          "required": true
+        },
+        "upstreamRemote": {
+          "type": "text",
+          "label": "Upstream remote",
+          "help": "The remote (URL or owner/repo) the fork tracks. Defaults to the repository's parent.",
+          "default": "",
+          "required": false,
+          "constraints": {
+            "maxLength": 255
+          }
+        },
+        "localChanges": {
+          "type": "text",
+          "label": "Local changes",
+          "help": "Plain-language description of the customizations to preserve across rebase.",
+          "default": "",
+          "required": false,
+          "constraints": {
+            "maxLength": 2000
+          }
+        },
+        "verifyCommand": {
+          "type": "text",
+          "label": "Verify command",
+          "help": "The command that confirms the software works as intended (e.g. `make test`). If blank, the agent infers a sensible check.",
+          "default": "",
+          "required": false,
+          "constraints": {
+            "maxLength": 500
+          }
+        }
+      }
+    },
+    "prompt": "Fetch the latest upstream changes for the fork {{form.repository}} and rebase all local changes on top of upstream. Local changes to preserve: {{form.localChanges}}. Check that the software works as intended; if it does, replace the current version, otherwise leave the running version untouched and report what failed.",
+    "message": "This deployment cannot run the scheduled fork-sync automation directly. Set it up in this conversation instead: confirm the fork repository, the upstream remote, the local changes to preserve, the verification command, and the nightly schedule, then create the automation."
+  }
+}

package/automations/catalog-index.js

@@ -9,7 +9,8 @@ import entry3 from "./catalog/slack-channel-monitor/manifest.json" with { type:
 import entry4 from "./catalog/linear-triage-assistant/manifest.json" with { type: "json" };
 import entry5 from "./catalog/jira-issue-to-pr/manifest.json" with { type: "json" };
 import entry6 from "./catalog/research-brief-writer/manifest.json" with { type: "json" };
-import entry7 from "./catalog/incident-retrospective-drafter/manifest.json" with { type: "json" };
+import entry7 from "./catalog/upstream-fork-sync/manifest.json" with { type: "json" };
+import entry8 from "./catalog/incident-retrospective-drafter/manifest.json" with { type: "json" };
 
 export const AUTOMATION_CATALOG_ENTRIES = [
   entry0,
@@ -20,4 +21,5 @@ export const AUTOMATION_CATALOG_ENTRIES = [
   entry5,
   entry6,
   entry7,
+  entry8,
 ];

package/marketplaces/openhands-extensions.json

@@ -603,6 +603,20 @@
         "venv"
       ]
     },
+    {
+      "name": "upstream-fork-sync",
+      "source": "./skills/upstream-fork-sync",
+      "description": "Keep a long-lived fork in sync with its upstream. Creates a cron automation that fetches upstream changes, rebases local customizations on top, verifies the software works, and replaces the running version when the rebase is clean.",
+      "category": "integration",
+      "keywords": [
+        "fork",
+        "upstream",
+        "rebase",
+        "sync",
+        "automation",
+        "long-lived-fork"
+      ]
+    },
     {
       "name": "vercel",
       "source": "./skills/vercel",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openhands/extensions",
-  "version": "0.13.0",
+  "version": "0.14.0",
   "description": "Public OpenHands extension catalogs for skills, plugins, integrations, and automation templates.",
   "license": "MIT",
   "type": "module",

package/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "openhands-extensions"
-version = "0.13.0"
+version = "0.14.0"
 description = "OpenHands extensions, plugins, and skills (Python bindings for the integration catalog)"
 requires-python = ">=3.12"
 dependencies = [

package/python/openhands_extensions/_version.py

@@ -18,7 +18,7 @@ from importlib.metadata import PackageNotFoundError, version
 #: Kept in lock-step with pyproject.toml/package.json by the version test.
 #: release-please only rewrites a semver found on the annotated line itself, so
 #: the annotation must stay on the assignment; on its own line it is a no-op.
-_FALLBACK_VERSION = "0.13.0"  # x-release-please-version
+_FALLBACK_VERSION = "0.14.0"  # x-release-please-version
 
 try:
     __version__: str = version("openhands-extensions")

package/skills/index.js

@@ -499,6 +499,14 @@ export const SKILLS_CATALOG = [
     "content": "# Theme Factory Skill\n\nThis skill provides a curated collection of professional font and color themes themes, each with carefully selected color palettes and font pairings. Once a theme is chosen, it can be applied to any artifact.\n\n## Purpose\n\nTo apply consistent, professional styling to presentation slide decks, use this skill. Each theme includes:\n- A cohesive color palette with hex codes\n- Complementary font pairings for headers and body text\n- A distinct visual identity suitable for different contexts and audiences\n\n## Usage Instructions\n\nTo apply styling to a slide deck or other artifact:\n\n1. **Show the theme showcase**: Display the `theme-showcase.pdf` file to allow users to see all available themes visually. Do not make any modifications to it; simply show the file for viewing.\n2. **Ask for their choice**: Ask which theme to apply to the deck\n3. **Wait for selection**: Get explicit confirmation about the chosen theme\n4. **Apply the theme**: Once a theme has been chosen, apply the selected theme's colors and fonts to the deck/artifact\n\n## Themes Available\n\nThe following 10 themes are available, each showcased in `theme-showcase.pdf`:\n\n1. **Ocean Depths** - Professional and calming maritime theme\n2. **Sunset Boulevard** - Warm and vibrant sunset colors\n3. **Forest Canopy** - Natural and grounded earth tones\n4. **Modern Minimalist** - Clean and contemporary grayscale\n5. **Golden Hour** - Rich and warm autumnal palette\n6. **Arctic Frost** - Cool and crisp winter-inspired theme\n7. **Desert Rose** - Soft and sophisticated dusty tones\n8. **Tech Innovation** - Bold and modern tech aesthetic\n9. **Botanical Garden** - Fresh and organic garden colors\n10. **Midnight Galaxy** - Dramatic and cosmic deep tones\n\n## Theme Details\n\nEach theme is defined in the `themes/` directory with complete specifications including:\n- Cohesive color palette with hex codes\n- Complementary font pairings for headers and body text\n- Distinct visual identity suitable for different contexts and audiences\n\n## Application Process\n\nAfter a preferred theme is selected:\n1. Read the corresponding theme file from the `themes/` directory\n2. Apply the specified colors and fonts consistently throughout the deck\n3. Ensure proper contrast and readability\n4. Maintain the theme's visual identity across all slides\n\n## Create your Own Theme\nTo handle cases where none of the existing themes work for an artifact, create a custom theme. Based on provided inputs, generate a new theme similar to the ones above. Give the theme a similar name describing what the font/color combinations represent. Use any basic description provided to choose appropriate colors/fonts. After generating the theme, show it for review and verification. Following that, apply the theme as described above.",
     "license": "Complete terms in LICENSE.txt"
   },
+  {
+    "name": "upstream-fork-sync",
+    "description": "This skill should be used when the user asks to \"keep a fork in sync\", \"rebase local changes on upstream\", \"sync my fork nightly\", \"long-lived fork\", or \"automate upstream rebases\". Guides the user through creating a cron automation that fetches upstream changes, rebases local customizations on top, verifies the software works, and replaces the running version when the rebase is clean.",
+    "triggers": [
+      "/upstream-fork-sync:setup"
+    ],
+    "content": "# Upstream Fork Sync Automation\n\nCreate a cron automation that keeps a long-lived fork current with its\nupstream source. On every run it fetches the latest upstream changes,\nrebases the fork's local customizations on top, runs a verification check,\nand replaces the deployed version only when the software still works.\n\nThis implements the \"long-lived fork\" pattern: instead of repeatedly\nre-deriving a customization, the local changes are preserved across\nupstream releases and kept working automatically.\n\nWindows PowerShell equivalents for the setup, packaging, upload, and API-check\nshell snippets are in `references/windows.md`.\n\n---\n\n## Prerequisites\n\n### Required secret\n\nVerify that the following secret is set in **OpenHands Settings -> Secrets**:\n\n| Secret name | Token type | Minimum permissions |\n|---|---|---|\n| `GITHUB_PERSONAL_ACCESS_TOKEN` | Classic PAT | `repo` |\n| `GITHUB_PERSONAL_ACCESS_TOKEN` | Fine-grained PAT | Contents: Read and Write, Metadata: Read |\n\nCheck with:\n```bash\ncurl -s https://api.github.com/user \\\n  -H \"Authorization: Bearer $GITHUB_PERSONAL_ACCESS_TOKEN\" \\\n  | python3 -c \"import json,sys; d=json.load(sys.stdin); print(d.get('login') or d.get('message'))\"\n```\n\nIf the token is missing or invalid, inform the user and stop.\n\n---\n\n## Setup Workflow\n\nFollow these steps in order.\n\n### Step 1 - Verify `GITHUB_PERSONAL_ACCESS_TOKEN`\n\nRun the `curl` check above.\n\n- If absent: *\"GITHUB_PERSONAL_ACCESS_TOKEN is not set. Please add it in\n  OpenHands Settings -> Secrets.\"* Stop.\n- If the API returns `{\"message\": \"Bad credentials\"}`: tell the user the\n  token is invalid and ask them to update it. Stop.\n\n### Step 2 - Collect configuration\n\nConfirm with the user:\n\n- **Repository** — the long-lived fork to keep synchronized (owner/repo).\n- **Upstream remote** (optional) — the remote the fork tracks. Defaults to\n  the repository's GitHub parent.\n- **Local changes** (optional) — a plain-language description of the\n  customizations to preserve across rebase.\n- **Verify command** (optional) — the command that confirms the software\n  works (e.g. `make test`). If blank, infer a sensible check from the\n  repository's build system.\n- **Sync schedule** — how often to run the sync. Default: nightly (`0 3 * * *`).\n\n### Step 3 - Create the automation\n\nCreate the automation via the prompt preset:\n\n```bash\ncurl -s -X POST \"$AUTOMATION_API_URL/v1/preset/prompt\" \\\n  -H \"Authorization: Bearer $OPENHANDS_AUTOMATION_API_KEY\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\n    \"name\": \"Upstream fork sync - '\"$REPO\"'\",\n    \"prompt\": \"Fetch the latest upstream changes for the fork '\"$REPO\"' and rebase all local changes on top of upstream. Local changes to preserve: '\"$LOCAL_CHANGES\"'. Check that the software works as intended; if it does, replace the current version, otherwise leave the running version untouched and report what failed.\",\n    \"repos\": [{\"url\": \"'\"$REPO\"'\", \"provider\": \"github\"}],\n    \"trigger\": {\"type\": \"cron\", \"schedule\": \"'\"$SCHEDULE\"'\", \"timezone\": \"'\"$TIMEZONE\"'\"}\n  }'\n```\n\nConfirm the automation was created (HTTP 201) and report its ID to the user.\n\n---\n\n## Runtime behavior\n\nOn each scheduled run the automation:\n\n1. Clones the fork and fetches the latest from its upstream remote.\n2. Rebases every local customization commit on top of the newest upstream\n   HEAD, resolving conflicts in favor of the local changes where the\n   description indicates intent.\n3. Runs the verification command. If none was supplied, infers one from the\n   repo's build system (e.g. `make test`, `npm test`, `pytest`).\n4. On success, force-pushes the rebased branch and replaces the currently\n   deployed version with the freshly built one.\n5. On failure, leaves the running version untouched and reports the conflict\n   or failing check so a human can intervene.\n\n---\n\n## Notes\n\n- The automation is idempotent: a clean upstream with no new commits is a\n  no-op.\n- Force-push targets the fork's working branch only, never upstream.\n- If a rebase conflict cannot be resolved automatically, the run fails safe\n  and the previously deployed version keeps running."
+  },
   {
     "name": "uv",
     "description": "If the project uses uv, use this skill. Use this skill to create/manage Python projects and environments with `uv`, add/remove dependencies, sync a project from `uv.lock`, and run commands in the project environment.",

package/skills/upstream-fork-sync/.plugin/plugin.json

@@ -0,0 +1,21 @@
+{
+  "name": "upstream-fork-sync",
+  "version": "1.0.0",
+  "description": "Create a cron automation that keeps a long-lived fork synchronized with its upstream. Fetches upstream changes, rebases local customizations on top, verifies the software works, and replaces the running version when the rebase is clean.",
+  "author": {
+    "name": "OpenHands",
+    "email": "contact@all-hands.dev"
+  },
+  "homepage": "https://github.com/OpenHands/extensions",
+  "repository": "https://github.com/OpenHands/extensions",
+  "license": "MIT",
+  "keywords": [
+    "fork",
+    "upstream",
+    "rebase",
+    "sync",
+    "cron",
+    "automation",
+    "long-lived-fork"
+  ]
+}

package/skills/upstream-fork-sync/README.md

@@ -0,0 +1,38 @@
+# Upstream Fork Sync Skill
+
+An OpenHands skill that creates a cron automation to keep a long-lived
+fork synchronized with its upstream source.
+
+## What it does
+
+1. **Fetches** the latest upstream changes for the fork on a schedule.
+2. **Rebases** the fork's local customizations on top of the newest
+   upstream HEAD.
+3. **Verifies** the software still works (using a configured command or an
+   inferred build check).
+4. **Replaces** the deployed version when verification passes, or
+   **fails safe** and reports the problem when it does not.
+
+## When to use
+
+Use this skill when a user wants to maintain customizations on top of an
+upstream project over time — the "long-lived fork" pattern — without
+manually redoing the work after every upstream release.
+
+## Files
+
+```
+upstream-fork-sync/
+├── SKILL.md   ← agent instructions (loaded automatically)
+└── README.md  ← this file
+```
+
+## Quick start
+
+Just tell OpenHands:
+
+> *"Set up an upstream fork sync for `owner/repo`"*
+
+The skill will walk through token verification, upstream-remote selection,
+local-changes description, verification command, and schedule, then create
+the automation automatically.

package/skills/upstream-fork-sync/SKILL.md

@@ -0,0 +1,122 @@
+---
+name: upstream-fork-sync
+description: >
+  This skill should be used when the user asks to "keep a fork in sync",
+  "rebase local changes on upstream", "sync my fork nightly",
+  "long-lived fork", or "automate upstream rebases". Guides the user through
+  creating a cron automation that fetches upstream changes, rebases local
+  customizations on top, verifies the software works, and replaces the
+  running version when the rebase is clean.
+triggers:
+  - /upstream-fork-sync:setup
+---
+
+# Upstream Fork Sync Automation
+
+Create a cron automation that keeps a long-lived fork current with its
+upstream source. On every run it fetches the latest upstream changes,
+rebases the fork's local customizations on top, runs a verification check,
+and replaces the deployed version only when the software still works.
+
+This implements the "long-lived fork" pattern: instead of repeatedly
+re-deriving a customization, the local changes are preserved across
+upstream releases and kept working automatically.
+
+Windows PowerShell equivalents for the setup, packaging, upload, and API-check
+shell snippets are in `references/windows.md`.
+
+---
+
+## Prerequisites
+
+### Required secret
+
+Verify that the following secret is set in **OpenHands Settings -> Secrets**:
+
+| Secret name | Token type | Minimum permissions |
+|---|---|---|
+| `GITHUB_PERSONAL_ACCESS_TOKEN` | Classic PAT | `repo` |
+| `GITHUB_PERSONAL_ACCESS_TOKEN` | Fine-grained PAT | Contents: Read and Write, Metadata: Read |
+
+Check with:
+```bash
+curl -s https://api.github.com/user \
+  -H "Authorization: Bearer $GITHUB_PERSONAL_ACCESS_TOKEN" \
+  | python3 -c "import json,sys; d=json.load(sys.stdin); print(d.get('login') or d.get('message'))"
+```
+
+If the token is missing or invalid, inform the user and stop.
+
+---
+
+## Setup Workflow
+
+Follow these steps in order.
+
+### Step 1 - Verify `GITHUB_PERSONAL_ACCESS_TOKEN`
+
+Run the `curl` check above.
+
+- If absent: *"GITHUB_PERSONAL_ACCESS_TOKEN is not set. Please add it in
+  OpenHands Settings -> Secrets."* Stop.
+- If the API returns `{"message": "Bad credentials"}`: tell the user the
+  token is invalid and ask them to update it. Stop.
+
+### Step 2 - Collect configuration
+
+Confirm with the user:
+
+- **Repository** — the long-lived fork to keep synchronized (owner/repo).
+- **Upstream remote** (optional) — the remote the fork tracks. Defaults to
+  the repository's GitHub parent.
+- **Local changes** (optional) — a plain-language description of the
+  customizations to preserve across rebase.
+- **Verify command** (optional) — the command that confirms the software
+  works (e.g. `make test`). If blank, infer a sensible check from the
+  repository's build system.
+- **Sync schedule** — how often to run the sync. Default: nightly (`0 3 * * *`).
+
+### Step 3 - Create the automation
+
+Create the automation via the prompt preset:
+
+```bash
+curl -s -X POST "$AUTOMATION_API_URL/v1/preset/prompt" \
+  -H "Authorization: Bearer $OPENHANDS_AUTOMATION_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "name": "Upstream fork sync - '"$REPO"'",
+    "prompt": "Fetch the latest upstream changes for the fork '"$REPO"' and rebase all local changes on top of upstream. Local changes to preserve: '"$LOCAL_CHANGES"'. Check that the software works as intended; if it does, replace the current version, otherwise leave the running version untouched and report what failed.",
+    "repos": [{"url": "'"$REPO"'", "provider": "github"}],
+    "trigger": {"type": "cron", "schedule": "'"$SCHEDULE"'", "timezone": "'"$TIMEZONE"'"}
+  }'
+```
+
+Confirm the automation was created (HTTP 201) and report its ID to the user.
+
+---
+
+## Runtime behavior
+
+On each scheduled run the automation:
+
+1. Clones the fork and fetches the latest from its upstream remote.
+2. Rebases every local customization commit on top of the newest upstream
+   HEAD, resolving conflicts in favor of the local changes where the
+   description indicates intent.
+3. Runs the verification command. If none was supplied, infers one from the
+   repo's build system (e.g. `make test`, `npm test`, `pytest`).
+4. On success, force-pushes the rebased branch and replaces the currently
+   deployed version with the freshly built one.
+5. On failure, leaves the running version untouched and reports the conflict
+   or failing check so a human can intervene.
+
+---
+
+## Notes
+
+- The automation is idempotent: a clean upstream with no new commits is a
+  no-op.
+- Force-push targets the fork's working branch only, never upstream.
+- If a rebase conflict cannot be resolved automatically, the run fails safe
+  and the previously deployed version keeps running.

package/skills/upstream-fork-sync/commands/upstream-fork-sync-setup.md

@@ -0,0 +1,8 @@
+---
+# auto-generated by sync_extensions.py
+description: This skill should be used when the user asks to "keep a fork in sync", "rebase local changes on upstream", "sync my fork nightly", "long-lived fork", or "automate upstream rebases". Guides the user through creating a cron automation that fetches upstream changes, rebases local customizations on top, verifies the software works, and replaces the running version when the rebase is clean.
+---
+
+Read and follow the complete instructions in the SKILL.md file located in this skill's directory.
+
+$ARGUMENTS

package/tests/fixtures/automations/upstream-fork-sync.json

@@ -0,0 +1,223 @@
+{
+  "automationId": "upstream-fork-sync",
+  "description": "Direct scheduled setup. Every create request body below is verified against the live CreatePromptAutomationRequest model in OpenHands/automation (openhands/automation/preset_router.py).",
+  "capabilities": "supported",
+  "blockedBy": [
+    "notReady"
+  ],
+  "scenarios": [
+    {
+      "id": "happy-path",
+      "description": "Defaults plus a repository, a description of the local changes, and a verify command. Preflight passes, the automation is created.",
+      "formValues": {
+        "repository": "OpenHands/agent-server-gui",
+        "upstreamRemote": "",
+        "localChanges": "high-contrast UI theme",
+        "verifyCommand": "make test",
+        "schedule": "0 3 * * *",
+        "timezone": "UTC"
+      },
+      "preflight": {
+        "request": {
+          "method": "POST",
+          "path": "/v1/validate",
+          "body": {
+            "automationId": "upstream-fork-sync",
+            "endpoint": "/v1/preset/prompt",
+            "draft": {
+              "name": "Upstream fork sync - OpenHands/agent-server-gui",
+              "prompt": "Fetch the latest upstream changes for the fork OpenHands/agent-server-gui and rebase all local changes on top of upstream. Local changes to preserve: high-contrast UI theme. Check that the software works as intended; if it does, replace the current version, otherwise leave the running version untouched and report what failed.",
+              "repos": [
+                {
+                  "url": "OpenHands/agent-server-gui",
+                  "provider": "github"
+                }
+              ],
+              "trigger": {
+                "type": "cron",
+                "schedule": "0 3 * * *",
+                "timezone": "UTC"
+              }
+            }
+          }
+        },
+        "response": {
+          "status": 200,
+          "body": {
+            "valid": true,
+            "errors": []
+          }
+        }
+      },
+      "create": {
+        "request": {
+          "method": "POST",
+          "path": "/v1/preset/prompt",
+          "body": {
+            "name": "Upstream fork sync - OpenHands/agent-server-gui",
+            "prompt": "Fetch the latest upstream changes for the fork OpenHands/agent-server-gui and rebase all local changes on top of upstream. Local changes to preserve: high-contrast UI theme. Check that the software works as intended; if it does, replace the current version, otherwise leave the running version untouched and report what failed.",
+            "repos": [
+              {
+                "url": "OpenHands/agent-server-gui",
+                "provider": "github"
+              }
+            ],
+            "trigger": {
+              "type": "cron",
+              "schedule": "0 3 * * *",
+              "timezone": "UTC"
+            }
+          }
+        },
+        "response": {
+          "status": 201,
+          "body": {
+            "id": "9a2c7b15-3c4d-4e5f-8a1b-4c9d0e1f2a33",
+            "user_id": "1a2b3c4d-0000-4000-8000-000000000001",
+            "org_id": "1a2b3c4d-0000-4000-8000-000000000002",
+            "model": null,
+            "name": "Upstream fork sync - OpenHands/agent-server-gui",
+            "prompt": "Fetch the latest upstream changes for the fork OpenHands/agent-server-gui and rebase all local changes on top of upstream. Local changes to preserve: high-contrast UI theme. Check that the software works as intended; if it does, replace the current version, otherwise leave the running version untouched and report what failed.",
+            "trigger": {
+              "type": "cron",
+              "schedule": "0 3 * * *",
+              "timezone": "UTC"
+            },
+            "tarball_path": "oh-internal://uploads/7e1b2c30-9f23-5b66-c2e3-7df1b4c5a990",
+            "setup_script_path": "setup.sh",
+            "entrypoint": ".venv/bin/python main.py",
+            "timeout": 600,
+            "keep_alive": null,
+            "enabled": true,
+            "last_triggered_at": null,
+            "created_at": "2026-08-03T12:00:00Z",
+            "updated_at": "2026-08-03T12:00:00Z"
+          }
+        }
+      }
+    },
+    {
+      "id": "interval-below-deployment-minimum",
+      "description": "A one-minute schedule. The create model accepts it, so only the deployment can reject it - this is precisely why preflight exists and why local validation is not authoritative.",
+      "formValues": {
+        "repository": "OpenHands/agent-server-gui",
+        "upstreamRemote": "",
+        "localChanges": "high-contrast UI theme",
+        "verifyCommand": "make test",
+        "schedule": "*/1 * * * *",
+        "timezone": "UTC"
+      },
+      "preflight": {
+        "request": {
+          "method": "POST",
+          "path": "/v1/validate",
+          "body": {
+            "automationId": "upstream-fork-sync",
+            "endpoint": "/v1/preset/prompt",
+            "draft": {
+              "name": "Upstream fork sync - OpenHands/agent-server-gui",
+              "prompt": "Fetch the latest upstream changes for the fork OpenHands/agent-server-gui and rebase all local changes on top of upstream. Local changes to preserve: high-contrast UI theme. Check that the software works as intended; if it does, replace the current version, otherwise leave the running version untouched and report what failed.",
+              "repos": [
+                {
+                  "url": "OpenHands/agent-server-gui",
+                  "provider": "github"
+                }
+              ],
+              "trigger": {
+                "type": "cron",
+                "schedule": "*/1 * * * *",
+                "timezone": "UTC"
+              }
+            }
+          }
+        },
+        "response": {
+          "status": 200,
+          "body": {
+            "valid": false,
+            "errors": [
+              {
+                "field": "trigger.schedule",
+                "code": "interval_too_short",
+                "message": "Minimum interval for this deployment is 5 minutes."
+              }
+            ]
+          }
+        }
+      },
+      "expectedFieldErrors": {
+        "schedule": "Minimum interval for this deployment is 5 minutes."
+      }
+    },
+    {
+      "id": "unfireable-cron-rejected-at-create",
+      "description": "31 February. Syntactically valid, so a local check passes, but the service rejects it. Shows the real 422 body: detail is a list and the loc path carries the trigger discriminator tag.",
+      "formValues": {
+        "repository": "OpenHands/agent-server-gui",
+        "upstreamRemote": "",
+        "localChanges": "high-contrast UI theme",
+        "verifyCommand": "make test",
+        "schedule": "0 0 31 2 *",
+        "timezone": "UTC"
+      },
+      "create": {
+        "request": {
+          "method": "POST",
+          "path": "/v1/preset/prompt",
+          "body": {
+            "name": "Upstream fork sync - OpenHands/agent-server-gui",
+            "prompt": "Fetch the latest upstream changes for the fork OpenHands/agent-server-gui and rebase all local changes on top of upstream. Local changes to preserve: high-contrast UI theme. Check that the software works as intended; if it does, replace the current version, otherwise leave the running version untouched and report what failed.",
+            "repos": [
+              {
+                "url": "OpenHands/agent-server-gui",
+                "provider": "github"
+              }
+            ],
+            "trigger": {
+              "type": "cron",
+              "schedule": "0 0 31 2 *",
+              "timezone": "UTC"
+            }
+          }
+        },
+        "response": {
+          "status": 422,
+          "body": {
+            "detail": [
+              {
+                "type": "value_error",
+                "loc": [
+                  "body",
+                  "trigger",
+                  "cron",
+                  "schedule"
+                ],
+                "msg": "Value error, Cron expression cannot produce any future fire times: 0 0 31 2 *"
+              }
+            ]
+          }
+        }
+      },
+      "expectedFieldErrors": {
+        "schedule": "Value error, Cron expression cannot produce any future fire times: 0 0 31 2 *"
+      }
+    },
+    {
+      "id": "fallback-conversation-when-direct-unavailable",
+      "description": "A cron-only deployment cannot run a webhook trigger, but this entry is cron-only and so runs directly; the assisted message seeds the conversation when the deployment is not ready.",
+      "formValues": {
+        "repository": "OpenHands/agent-server-gui",
+        "upstreamRemote": "",
+        "localChanges": "high-contrast UI theme",
+        "verifyCommand": "make test",
+        "schedule": "0 3 * * *",
+        "timezone": "UTC"
+      },
+      "conversation": {
+        "request": {
+          "message": "This deployment cannot run the scheduled fork-sync automation directly. Set it up in this conversation instead: confirm the fork repository, the upstream remote, the local changes to preserve, the verification command, and the nightly schedule, then create the automation."
+        }
+      }
+    }
+  ]
+}