KofTwentyTwo/Jarvis
2
0 Fork 0
Code Issues 111 Pull Requests 16 Actions Packages Projects Releases 4 Wiki Activity

v1.1: WhisperKit STT fallback activation — feature flag flip + model fetch #78

New Issue
Open
opened 2026-05-12 19:30:07 +00:00 by KofTwentyTwo · 0 comments
KofTwentyTwo commented 2026-05-12 19:30:07 +00:00 (Migrated from github.com)
Copy link
Copy source

Summary

Activate the WhisperKit STT fallback path. The `argmaxinc/argmax-oss-swift v0.18.0` package is added, wiring code is present, and the path is behind `Settings.featureFlags.whisperKitSTT`. Activation requires the feature flag to flip, the `large-v3-v20240930_626MB` model fetched, and the SpeechAnalyzer fallback path tested end-to-end.

Distinct from #29/#39 which cover the bugs (hard-coded factory, camelCase mismatch, dead config). This issue covers the activation milestone once those bugs close.

Evidence

  • Migration plan: `.planning/architecture/JARVIS-API-MIGRATION-PLAN.md:593, 732` v1.1 milestone.
  • v1.0 spec lists with `[trigger: deferred]`.

Gap classification

"design-mapped but not built" — Settings command `setSTTBackend(.whisperKit)` mapped in contract; never lights up.

Recommended action

File against v1.1. Depends on #29 (STT backend hard-coded), #37 (constant mismatch), #39 (feature flag dead) closing first.

Cross-references

## Summary Activate the WhisperKit STT fallback path. The \`argmaxinc/argmax-oss-swift v0.18.0\` package is added, wiring code is present, and the path is behind \`Settings.featureFlags.whisperKitSTT\`. Activation requires the feature flag to flip, the \`large-v3-v20240930_626MB\` model fetched, and the SpeechAnalyzer fallback path tested end-to-end. Distinct from #29/#39 which cover the *bugs* (hard-coded factory, camelCase mismatch, dead config). This issue covers the *activation milestone* once those bugs close. ## Evidence - Migration plan: \`.planning/architecture/JARVIS-API-MIGRATION-PLAN.md:593, 732\` v1.1 milestone. - v1.0 spec lists with \`[trigger: deferred]\`. ## Gap classification \"design-mapped but not built\" — Settings command \`setSTTBackend(.whisperKit)\` mapped in contract; never lights up. ## Recommended action File against v1.1. Depends on #29 (STT backend hard-coded), #37 (constant mismatch), #39 (feature flag dead) closing first. ## Cross-references - Related: #29, #37, #39 - Migration plan §10 v1.1
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
area:agent
area:build
area:bus
area:devtool
area:hud
area:logging
area:mcp
area:memory
area:vision
area:voice
audit-finding
bug
Something isn't working
 carry-forward
comment-cleanup
Comment / docstring cleanup per .planning/code-commenting-guide.md
 dependencies
Dependency updates
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 epic
good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 javascript
Pull requests that update javascript code
 migration
question
Further information is requested
 severity:critical
severity:high
severity:low
severity:medium
wontfix
This will not be worked on
No labels area:voice carry-forward enhancement severity:medium
Milestone
No items
No Milestone v1.1 — Backlog (Orpheus, WhisperKit, Voice Log, presence, advanced)
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/Jarvis#78