Choose a Sapat transcription provider in Daytona

[antaloaalonso]

/claim #13

Summary

• Add a distinct long-form Daytona guide for choosing and validating Sapat transcription providers inside a Daytona workspace.
• Cover OpenAI, Groq, and Azure OpenAI provider setup from the current Sapat source, including --api, --quality, --language, --prompt, --temperature, and --correct behavior.
• Add a provider comparison and failover runbook workflow, an original SVG diagram, a Daytona-style definition, and a first-time contributor author profile.

Validation

• npx --yes markdownlint-cli authors/antonio_alonso.md definitions/20260511_definition_transcription_provider_failover.md guides/20260511_choose_sapat_transcription_provider_in_daytona.md --ignore node_modules
• git diff --check
• python -m compileall src in the current Sapat repository
• python -m pip install -e . in the current Sapat repository
• sapat --help
• python -m sapat.script --help
• ffmpeg -version
• Verified referenced links return HTTP 200: Sapat, Daytona docs, Daytona environment configuration, OpenAI speech-to-text, Groq speech-to-text, and Azure OpenAI audio docs

Notes

• This submission is intentionally scoped away from the active batch QA, privacy/redaction, and generic transcription pipeline PRs. It focuses on provider selection, provider comparison, and operational failover.
• npm run lint:md currently reports pre-existing markdownlint issues in older repository files outside this PR; the changed files pass markdownlint with the repo configuration.

[antaloaalonso]

Quick review/reward check-in: the changed files were validated locally and the linked Algora claim is pending. Happy to make any focused changes needed to get this merged/rewarded.