Code architecture inconsistencies, tech debt & out of place

[Alex-Wengg]

Living tracker for architectural debt, naming inconsistencies, and misplaced code in the repo. Add new items as comment replies.

Outline & Goals

• FA architecture should be both readable to humans and friendly for coding agents.
• The changes should be verified against the BenchmarkAMISubset.md or benchmarks100.md to ensure no wer, der nor rtfx regressions. using diarizer_subset_benchmark.sh and parakeet_subset_benchmark.sh
• TTS changes require human verification
• VAD is already quite simple

Priorities

• Out of place code
• consolidate repetitive code
• convoluted code that could be smoothen or simplified or elegant
• Inconsistent APIs
• Naming Purpose Distinctions
• Naming inconsistencies
• magic numbers

Testing

• verify changes are ok with this