Extend fv-serve to read saved file transcriptions, and eventually initiate them

[xkrogen]

Problem

The bundled fv-serve interface is useful for letting coding agents read FluidMeet recordings through meet list, meet show, and meet search. Could it also expose transcripts already saved in the File Transcription tab?

The immediate use case is read-only: transcribe a file in FluidVoice, then let a local agent read the result to summarize it or extract action items. This should not require manual exports, clipboard access, GUI focus changes, or reading FluidVoice's private storage format.

Proposed direction

First: read existing file transcripts. Provide the equivalent of the meeting commands, with illustrative names such as:

fv-serve file list --limit 10 --json
fv-serve file show <id|latest> --json
fv-serve file search "search text"

Listing could return stable IDs, titles/source filenames, dates, and durations; reading could return the saved text and any existing speaker-attributed segments. Include the commands in the generated agent skill. Access should be explicitly authorized, following the existing integration permission model.

Later, separately: initiate file transcription. An optional command such as fv-serve file transcribe <path> could reuse the existing transcription machinery, with a way to obtain completion/results and clear errors when the engine is busy. Reading saved results should remain usable without granting permission to initiate transcription.

Command names are only examples; the main request is a supported interface alongside the existing meeting access, not a particular CLI design.

Existing related work

• 1.6.12: hidden launch fix, meeting summaries on this Mac, Fluid Server #1110 introduced the Fluid Server/agent integration for meetings.
• [FEATURE] Local API / CLI / Webhook access to share the loaded STT Engine #871 was closed as completed and points to existing local API capabilities.
• Local API for File Transcription and Backlog Management #179 proposed file transcription and job management; it was closed unmerged, with a maintainer noting that a flavor of the API already exists.
• Discussions Expose Local API controls in Settings and revisit the 5-minute file transcription limit #584 and Expose Local API controls in Settings #639 cover the Local API's file-transcription limit and settings controls.

The current Local API router already exposes POST /v1/transcribe, so initiating transcription is not a request for an entirely new capability. However, GET /v1/history reads TranscriptionHistoryStore, while the File Transcription tab has a separate FileTranscriptionHistoryStore; I did not find a corresponding saved-file-transcript route in the current router.

If there is already a supported way to read that history through fv-serve or another official interface, documenting it would address the immediate need. Otherwise, read-only file-transcript parity would be a useful first increment.