refactor(cron): rebrand Cron Recipes -> Automation Blueprints

Product rename across every surface: module/file names (blueprint_catalog,
tools/blueprints, blueprint_cmd), slash command /cron-recipe -> /blueprint
(alias /bp), dashboard API /api/cron/blueprints, desktop deep-link
hermes://blueprint/<key>, docs catalog page + extract script, and the
skill frontmatter block metadata.hermes.blueprint. No behavior change.

website/docs/reference/automation-blueprints-catalog.mdx

@@ -0,0 +1,36 @@
+---
+sidebar_position: 7
+title: "Automation Blueprints Catalog"
+description: "Ready-to-run automation templates — set one up from the dashboard, CLI, TUI, any messenger, or the desktop app."
+---
+
+import AutomationBlueprintsCatalog from '@site/src/components/AutomationBlueprintsCatalog';
+
+# Automation Blueprints
+
+Automation Blueprints are ready-to-run automation templates. Pick one, fill in a couple
+of fields, and Hermes schedules it as a cron job — no cron syntax required.
+
+Every blueprint works from **every surface**:
+
+- **Dashboard / desktop app** — open the Cron page, switch to the **Blueprints**
+  tab, fill the form, and click *Schedule it*.
+- **CLI, TUI, and messengers** — type `/blueprint <name>` (e.g.
+  `/blueprint morning-brief`) and Hermes asks you for what it needs, one
+  question at a time, then schedules it. The name match is forgiving — a
+  prefix or near-spelling resolves. Power users can skip the questions by
+  passing values inline: `/blueprint morning-brief time=08:00`.
+- **Desktop app** — click **Send to App** on any blueprint and it opens with the
+  command pre-loaded in your composer.
+
+Blueprints never schedule anything silently — you always confirm before the job
+is created. Manage created jobs anytime with `/cron`.
+
+<AutomationBlueprintsCatalog />
+
+## Writing your own
+
+A blueprint is just a skill with a `metadata.hermes.blueprint` block in its
+`SKILL.md` frontmatter. See
+[Creating Skills → Automation Blueprints](../developer-guide/creating-skills.md) for the
+slot schema and how to publish one.

website/docs/reference/cron-recipes-catalog.mdx

@@ -1,36 +0,0 @@
----
-sidebar_position: 7
-title: "Cron Recipes Catalog"
-description: "Ready-to-run automation templates — set one up from the dashboard, CLI, TUI, any messenger, or the desktop app."
----
-
-import CronRecipesCatalog from '@site/src/components/CronRecipesCatalog';
-
-# Cron Recipes
-
-Cron Recipes are ready-to-run automation templates. Pick one, fill in a couple
-of fields, and Hermes schedules it as a cron job — no cron syntax required.
-
-Every recipe works from **every surface**:
-
-- **Dashboard / desktop app** — open the Cron page, switch to the **Recipes**
-  tab, fill the form, and click *Schedule it*.
-- **CLI, TUI, and messengers** — type `/cron-recipe <name>` (e.g.
-  `/cron-recipe morning-brief`) and Hermes asks you for what it needs, one
-  question at a time, then schedules it. The name match is forgiving — a
-  prefix or near-spelling resolves. Power users can skip the questions by
-  passing values inline: `/cron-recipe morning-brief time=08:00`.
-- **Desktop app** — click **Send to App** on any recipe and it opens with the
-  command pre-loaded in your composer.
-
-Recipes never schedule anything silently — you always confirm before the job
-is created. Manage created jobs anytime with `/cron`.
-
-<CronRecipesCatalog />
-
-## Writing your own
-
-A recipe is just a skill with a `metadata.hermes.recipe` block in its
-`SKILL.md` frontmatter. See
-[Creating Skills → Cron Recipes](../developer-guide/creating-skills.md) for the
-slot schema and how to publish one.