[Bugfix] Fix granite speech shape validation

[DarkLight1337]

Essential Elements of an Effective PR Description Checklist

• The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
• The test plan, such as providing test command.
• The test results, such as pasting the results comparison before and after, or e2e results
• (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.

Purpose

Yeah we really need #21754 to avoid this issue...

Test Plan

Test Result

(Optional) Documentation Update

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

[gemini-code-assist]

Code Review

This pull request correctly fixes a shape validation issue in GraniteSpeechAudioInputs by updating the TensorShape for input_features_mask. The change from nf to fi and the introduction of fo also improve clarity. I have one suggestion to make the documentation for the new fo dimension even clearer to prevent future confusion.

[gemini-code-assist]

The term "embedding size" is ambiguous. It is commonly used to refer to the dimensionality of an embedding vector (e.g., the hidden size), but here fo represents the number of output feature vectors (i.e., the sequence length of the embeddings). This could cause confusion for future developers.

To improve clarity, I suggest rephrasing this to avoid ambiguity.

Suggested change

	- fo: Number of output features, i.e. the embedding size.
	- fo: Number of output features (i.e., number of embeddings).

[bbeckca]

@DarkLight1337 Acknowledging bug introduced from changes. Thanks for the fix!