Git Object Type Before Inspection Narration

Inputs: [repository path], [object identifier], [expected object kind]. Use read-only Git object inspection to determine whether an identifier resolves to a commit, tree, blob or tag before choosing how to display it. Explain type and size checks; bound output and avoid printing large blobs or credentials. Do not execute blob content, fetch objects, alter refs or assume a tag object is a commit. Produce a 40-second developer handoff naming the verified object kind before describing its contents. Adapt the presentation to [audience] and [tone]. Check the defining task detail against the inputs before finishing.

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.