Jake
3770815fbf
Closes the code-side v0.1 ship gate. All quality gates green: cargo fmt/clippy/test (~327 tests), npm check (0/0), vitest 13/13, scripts/dogfood-rebrand-drill.sh 8/8. Phase F — first-run onboarding promoted to v0.1 - FirstRunPage with skip-to-main + failure recovery + event recording - Six onboarding commands (record/list/has-completed + lumotia_events) - Storage migration v17 (onboarding_events + lumotia_events tables) UI hardening (in-scope items from v0.1-ui-hardening.md) - StatusPill + PostCaptureCard components, 21st preview entry - Sidebar recording-as-sacred-state (opacity + aria-disabled, reduced-motion) - Settings 6-section regroup + Help section + Activation log + Privacy toggle - Error-state copy sweep (DictationPage + SettingsPage, plain-language) - Global :focus-visible rule, textarea outlines restored - Ctrl+K / Ctrl+, / Escape bindings in +layout LLM resilience - rule_based_extract_tasks (regex-free imperative-verb extractor) + extract_tasks_with_fallback wrapper — task extraction never returns zero - tokio::time::timeout(120s) wraps cleanup/tags/tasks commands Release artefacts - LICENSE (canonical AGPL-3.0), CHANGELOG (Keep-a-Changelog format) - v0.1-release-notes, privacy-and-ai-use, install-warnings, tester-onboarding-kit, tester-acceptance-runbook, code-signing-setup, apple-silicon-rb08-runbook, virtual-audio-setup, v0.1-contrast-audit - Workspace versioning + AGPL spdx; npm exact-pin (10 ranges removed) - AppImage SHA-256 sidecar in build.yml - README v0.1 section + Reporting-issues; canonical repo slug Closure pass — items moved from human-required to code-complete - KI-02 Linux idle inhibit: zbus 5 → org.freedesktop.login1.Manager.Inhibit - KI-03 Windows sleep prevention: SetThreadExecutionState(ES_CONTINUOUS|...) - acquire/release_idle_inhibit Tauri commands, wired in DictationPage - Diagnostic-bundle frontend wire-up (Settings → Help button) - WCAG-AA contrast fix via .btn-filled-text utility (no token changes) - 8 destructive-action sites wrapped in plain-language confirm() guards - KNOWN-ISSUES.md + v0.1-known-limitations.md updated (KI-02/03 fixed) Scripts - pre-tag-verify.sh, tag-day.sh, smoke-linux + driver - parse-diagnostic-bundle.sh, parse-activation-log.py Per-item audit trail: docs/release/v0.1-completion-status.md Remaining: W-01…W-08 (signing certs, hardware probes, smoke matrix, tester recruitment) — see docs/release/v0.1-known-limitations.md.
3.8 KiB
name, type, tags, description
| name | type | tags | description | |||||||
|---|---|---|---|---|---|---|---|---|---|---|
| virtual-audio-setup | release |
|
How to set up a virtual audio source so the smoke harness can run audio-dependent cells unattended — without you speaking into a microphone. |
Virtual audio setup for smoke testing
Why
Lumotia's smoke driver (scripts/smoke-linux-driver.sh) can automate the Capture cell — pressing the record hotkey, waiting, stopping — but the recording pipeline needs an audio signal to produce a transcript. Without one it records silence, Whisper returns nothing, and the Cleanup and History cells have nothing to assert against.
A virtual audio source feeds a synthetic signal into the recording pipeline so the smoke harness can run the audio-dependent cells without you talking. You set it up once before a test run and tear it down after.
Setup on Linux (PulseAudio or PipeWire-pulse)
PipeWire ships a PulseAudio compatibility layer on all major distros since 2022, so the pactl commands below work on both.
Option A — sine-wave tone (always available, no extra files)
pactl load-module module-sine-source source_name=lumotia-test frequency=440
This creates a virtual microphone that emits a 440 Hz tone continuously. Whisper will transcribe it as something like "A" or ambient noise — enough to produce a non-empty transcript row and exercise the pipeline.
Option B — WAV file (closer to real speech)
First generate a test file. If espeak is installed you get a synthetic voice; otherwise ffmpeg generates a tone:
# With espeak (sounds like speech — better for Whisper)
espeak -v en -s 150 "Lumotia smoke test one two three" \
--stdout | ffmpeg -i pipe:0 -ar 16000 -ac 1 -f s16le /tmp/lumotia-test.raw 2>/dev/null
ffmpeg -f s16le -ar 16000 -ac 1 -i /tmp/lumotia-test.raw /tmp/lumotia-test.wav 2>/dev/null
# Without espeak (synthetic tone — still exercises the pipeline)
ffmpeg -f lavfi -i "sine=frequency=440:duration=5" -ar 16000 -ac 1 /tmp/lumotia-test.wav 2>/dev/null
Then load the pipe-source:
pactl load-module module-pipe-source \
source_name=lumotia-test \
file=/tmp/lumotia-test.wav \
format=s16le rate=16000 channels=1
Wire it into Lumotia
Open Lumotia → Settings → Start Here → Microphone and pick lumotia-test from the dropdown. Save. Then run the smoke driver:
./scripts/smoke-linux-driver.sh [/path/to/AppImage]
Tear down after the run
pactl unload-module $(pactl list short modules | grep lumotia-test | awk '{print $1}')
The smoke driver does not automatically unload the module, so your regular microphone is unaffected by the test run.
macOS
Use BlackHole (open-source, free from Existential Audio). Install via Homebrew:
brew install --cask blackhole-2ch
After installing, open Audio MIDI Setup (Applications → Utilities), create a Multi-Output Device that includes both BlackHole 2ch and your speakers if you want to hear output. Set BlackHole 2ch as the input in Lumotia → Settings → Start Here → Microphone.
To feed audio into BlackHole during the test, route any audio player's output to the BlackHole device, or use ffmpeg with the AVFoundation backend (note: macOS xdotool equivalents are outside the current smoke-driver scope — these steps are manual on macOS).
Windows
Use VB-CABLE (free from VB-Audio). Download from vb-audio.com/Cable, run the installer with admin rights, reboot. Set CABLE Output as the recording device in Lumotia → Settings → Start Here → Microphone. Route audio to CABLE Input from any player to feed the pipeline.
Windows smoke-test automation (UI driving) is not currently in scope for v0.1 — these instructions document the audio-loopback pattern for when it is.