the transcription goes beside the audio, and nothing else moves

it created a dated directory, moved the recording into it and wrote the
markdown alongside. nobody asked for an archive. the thing you want from a
transcription is the text next to the recording, which is exactly what the
file viewer's transcribe button did — POST with saveNextTo, sibling .md,
done.

overwrites a previous transcription of the same file on purpose: it is
derived, running it again means you wanted it again, and a -2 beside it is
only a second file to choose between.

inline: true, so the file browser runs it and waits rather than making a
background job out of a call that takes seconds.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Officer-Session: 656f5c85-e49a-4f1f-b9f3-042a04b4d043

tasks/transcribe-audio-file/TASK.md

@@ -4,7 +4,7 @@ description: Transcribe an audio file to text over your own whisper.cpp server,
 category: Media
 version: 1
 mode: script
-inline: false
+inline: true
 language: typescript
 tags:
   - audio
@@ -38,11 +38,11 @@ model call spent re-deriving what the plugin already returns.
    (`GET /api/user/settings`).
 2. `POST` the file to `/api/transcribe/transcribe`. The plugin detects the language and transcribes
    faithfully in it — see `plugins/transcribe/skills/transcribe/SKILL.md` for the contract.
-3. Create a sibling directory named `<date>_<slug>`, where `<date>` is today in `YYYYMMDD` and `<slug>`
-   is derived from the original file's own name (not a generated title — a script task gets no model
-   turn to ask for one).
-4. Move the original audio file into that directory and save the transcription beside it as a
-   Markdown file with the same base name.
+3. Write the transcription beside the audio file, same name, `.md`. Nothing is moved and nothing is
+   created around it.
+
+It overwrites a previous transcription of the same file, deliberately: a transcription is derived, and
+running it again means you wanted it again.
 
 ## Before it runs