UTF16 Surrogate Slice Tests Audio Scene

Act as an audio producer. Using [string slicing interface], [Unicode fixtures] and [indexing contract], create a 35–45 second original audio piece to support this task: design tests for slicing at UTF-16 surrogate boundaries; distinguish code units, code points and grapheme clusters and state whether broken surrogate output is rejected or preserved by contract. Translate this visual idea into audible cues or concise narration: one supplementary character occupies two code-unit boxes while a boundary marker shows a potentially invalid split. Return a timed script with voice, pause and optional sound-effect columns. State facts plainly; do not use sounds as the only way to communicate an essential distinction. Limit spoken copy to 85 words.

Use only the supplied facts and approved wording. If a necessary script or timing reference is missing, ask for it first. Produce the audio when supported; otherwise return the complete spoken script with pauses and a short production cue sheet, clearly labeled as a script. Use original voices and keep speech intelligible without music. Never claim an audio file exists unless it was generated.