Different treatment for parakeetTdtCtc110m with other parakeet models of folder name

[Josscii]

FluidAudio/Sources/FluidAudio/ModelNames.swift

Lines 152 to 156 in e13ffe2

	case .parakeetTdtCtc110m:
	return "parakeet-tdt-ctc-110m"
	default:
	return name
	}

Is this a bug or specific reason?

[Alex-Wengg]

parakeetTdtCtc110m is a new parakeet model simpler and smaller than parakeet tdt

[Josscii]

@Alex-Wengg Hi, I understand that, but looking at the code, why it is not using the name as the folder name while other parakeet models just return the name?

[Alex-Wengg]

@Josscii it was offered suggested by another dev but good call out i will update the structure as part of #434

[Josscii]

Thanks, I think it is more consistent.

[Alex-Wengg]

After investigating, the special case for parakeetTdtCtc110m appears to be intentional. The test at ModelNamesTests.swift:129 explicitly expects folderName to return "parakeet-tdt-ctc-110m" (without the -coreml suffix), with a comment indicating this is a "simplified local folder name".

Changing this to match other Parakeet models would be a breaking change - existing users who have already downloaded the model would have it cached in parakeet-tdt-ctc-110m but the code would look for parakeet-tdt-ctc-110m-coreml, causing re-downloads.

The design rationale seems to be:

• name: Full repo name with -coreml suffix
• folderName: Simplified local cache folder name (some models omit the -coreml suffix for brevity)

So this appears to be working as designed rather than being an inconsistency that needs fixing.