Submodule Pointer Review Brief

Create a 40-second code review briefing from [parent diff], [submodule revision summary] and [test evidence]. Say whether the pointer changed, identify the intended revision by approved short label and separate submodule changes from parent changes. Omit credentials and private URLs. Explicitly call out missing validation instead of describing the update as safe by default.

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.