decision(speech-to-text): transcoded .wav lands in a different Storage location

[cabljac]

The extension derived the transcoded .wav Storage destination from the local /tmp path. The kit derives it from the object name and normalises the prefix separator. Migrated users find their transcoded audio in a different location.

Extension:

storagePath: config.outputStoragePath
  ? `${config.outputStoragePath}${transcodeResult.outputPath}` // "transcriptions" + "/tmp/a.mp3.wav"
  : transcodeResult.outputPath.slice(1);                       // "tmp/a.mp3.wav"

Kit:

const transcodedObjectName = `${filePath}.wav`;
storagePath: config.outputStoragePath
  ? `${config.outputStoragePath.replace(/\/$/, "")}/${transcodedObjectName}`
  : transcodedObjectName;

For an input object named a.mp3:

OUTPUT_STORAGE_PATH	Extension writes	Kit writes
unset	tmp/a.mp3.wav	a.mp3.wav
transcriptions	transcriptions/tmp/a.mp3.wav	transcriptions/a.mp3.wav
transcriptions/	transcriptions//tmp/a.mp3.wav	transcriptions/a.mp3.wav

The .txt transcript path had a related remnant (replace("tmp/", "")), fixed in #3073 (#3026). The .wav location itself is still open.

Decide one of:

• Parity: reproduce the extension's tmp/-prefixed paths, double slash included, so existing consumers keep finding files where they were.
• Keep the kit's path: the extension's tmp/ segment is an artefact of the local download path, not a design. Document the change and the old-vs-new matrix in the kit README and the Notes entries (docs(kits): write the Notes entries for accepted divergences #3035).

Parity ledger: #2974, speech-to-text §1.

DECISION: go with Parity