Mention Automations in README intro

The opening description covered runtimes and mentions but not the
Automations feature; add a sentence on scheduled/manual prompt files with
exportable per-run history. Docs only.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

.prompt-hub/memory.md

@@ -73,3 +73,4 @@
 | 2026-05-19 23:46:00 CEST | agent | Expanded the generated example automation (`EXAMPLE_AUTOMATION_CONTENT`) to exhaustively document every option: per-field type/default comments, interval-vs-cron exclusivity, 5 worked cron examples, runtime id/name matching, appendNewline behaviour. Verified the content still parses (interval active, cron/runtime commented). Bumped 0.2.4 → 0.2.5, rebuilt dist bundle. | `main.ts`, `manifest.json`, `.prompt-hub/version.md`, `.prompt-hub/releases.md`, `main.js` (rebuilt), `dist/`, `npm run lint`, `npm run build` | success | Commit and push to `feature/automation`. |
 | 2026-05-19 23:52:00 CEST | agent | Per user feedback ("il manque le runtime"), uncommented the `runtime` field in the generated example automation so it ships as an active field (`runtime: Claude`), with the comment retained explaining how to remove it to target any runtime. Verified frontmatter parses with runtime active. Bumped 0.2.5 → 0.2.6, rebuilt dist. | `main.ts`, `manifest.json`, `.prompt-hub/version.md`, `.prompt-hub/releases.md`, `main.js` (rebuilt), `dist/`, `npm run build` | success | Commit and push to `feature/automation`. |
 | 2026-05-20 00:09:00 CEST | agent | History "Export as markdown" now always creates a fresh date-stamped file: filename includes export date + time (`automations-history-YYYY-MM-DD-HHMMSS.md`) with a numeric-suffix collision guard, so repeated same-day exports no longer fail on `vault.create` existing-file error. Export heading shows readable timestamp. Bumped 0.2.6 → 0.2.7, rebuilt dist. | `automations-modal.ts`, `manifest.json`, `.prompt-hub/version.md`, `.prompt-hub/releases.md`, `main.js` (rebuilt), `dist/`, `npm run lint`, `npm run build`, `npm test` (55 pass) | success | Commit and push to `feature/automation`. |
+| 2026-05-20 00:18:00 CEST | agent | Updated README intro paragraph to describe the Automations feature (scheduled/manual prompt files + exportable per-run history) alongside runtime/mention features. Docs only — no code or bundle change; manifest left at 0.2.7. Bumped prompt-hub version 0.2.7 → 0.2.8. | `README.md`, `.prompt-hub/version.md`, `.prompt-hub/releases.md` | success | Commit and push to `feature/automation`. |

.prompt-hub/releases.md

@@ -1,5 +1,8 @@
 # Releases
 
+## 0.2.8 - 2026-05-20
+- Updated the README intro paragraph to describe the Automations feature (scheduled/manual prompt files with exportable per-run history) alongside the existing runtime and mention features. Docs only — no code or bundle change.
+
 ## 0.2.7 - 2026-05-20
 - History "Export as markdown" now always creates a fresh date-stamped file. The filename includes the export date and time (`automations-history-YYYY-MM-DD-HHMMSS.md`) with a numeric suffix guard, so repeated same-day exports no longer fail on an existing-file clash. The export note heading also shows the readable export timestamp.
 

.prompt-hub/version.md

@@ -1 +1 @@
-0.2.7
+0.2.8

README.md

@@ -4,7 +4,7 @@
 
 Run any local AI coding CLI — Claude, Codex, or your own — inside a right sidebar terminal in Obsidian.
 
-The plugin embeds a real PTY-backed terminal in the sidebar and lets you declare an unlimited list of CLI runtimes from settings (each with a display name and a launch command). Pick one from a dropdown to start it in your active vault folder, switch between them on the fly, and inject the active file or folder as a mention with one click.
+The plugin embeds a real PTY-backed terminal in the sidebar and lets you declare an unlimited list of CLI runtimes from settings (each with a display name and a launch command). Pick one from a dropdown to start it in your active vault folder, switch between them on the fly, and inject the active file or folder as a mention with one click. You can also schedule reusable prompts: drop markdown files in a vault folder and the plugin fires them into the running CLI on an interval or cron — or run them on demand from the Automations panel, with a per-run history you can export.
 
 ## Features