[Misc] Reorganize inputs

[DarkLight1337]

Purpose

• Renamed ProcessorInputs -> EngineInput to avoid confusion about where it should be inputted.
  • Standardized engine input naming, e.g.:
    • TokenInputs -> TokensInput
    • token_inputs-> tokens_input
    • EmbedsInputs -> EmbedsInput
    • SingletonInputs -> SingletonInput
• Split up vllm.inputs.data.
  • LLM API inputs go into vllm.inputs.llm.
  • Engine inputs go into vllm.inputs.engine.
  • Moved vllm.inputs.parse.split_enc_dec_inputs -> vllm.inputs.engine.split_enc_dec_input.
• Moved the following MM input definitions to avoid circular imports and also make them more accessible to users:
  • vllm.multimodal.inputs.ModalityData -> vllm.inputs.llm.ModalityData
  • vllm.multimodal.inputs.MultiModalDataBuiltins -> vllm.inputs.llm.MultiModalDataBuiltins
  • vllm.multimodal.inputs.MultiModalDataDict -> vllm.inputs.llm.MultiModalDataDict
  • vllm.multimodal.inputs.MultiModalUUIDDict -> vllm.inputs.llm.MultiModalUUIDDict
  • vllm.multimodal.inputs.MultiModalHashes -> vllm.inputs.engine.MultiModalHashes
  • vllm.multimodal.inputs.MultiModalPlaceholderDict -> vllm.inputs.engine.MultiModalPlaceholders
  • vllm.multimodal.inputs.MultiModalInputs -> vllm.inputs.engine.MultiModalInput
  • vllm.multimodal.inputs.mm_inputs -> vllm.inputs.engine.mm_input
  • vllm.multimodal.inputs.MultiModalEncDecInputs -> vllm.inputs.engine.MultiModalEncDecInput
  • vllm.multimodal.inputs.mm_enc_dec_inputs -> vllm.inputs.engine.mm_enc_dec_input
• Updated associated variable names
• Updated relevant docs

Test Plan

Test Result

---

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.
• (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

[mergify]

Documentation preview: https://vllm--35182.org.readthedocs.build/en/35182/

[mergify]

Hi @DarkLight1337, the pre-commit checks have failed. Please run:

uv pip install pre-commit
pre-commit install
pre-commit run --all-files

Then, commit the changes and push to your branch.

For future commits, pre-commit will run automatically on changed files before each commit.

Tip

Is mypy or markdownlint failing?

mypy and markdownlint are run differently in CI. If the failure is related to either of these checks, please use the following commands to run them locally:

# For mypy (substitute "3.10" with the failing version if needed)
pre-commit run --hook-stage manual mypy-3.10
# For markdownlint
pre-commit run --hook-stage manual markdownlint

[ywang96]

cc @njhill - the fundamental change to this PR is that we want to avoid using EngineCoreRequest as the public interface for the input of AsyncLLM but EngineInput instead, and EngineInput -> EngineCoreRequest (which adds request_id validation) takes place inside AsyncLLM.

I'd like to make sure we decide on an interface for token-in-token-out and stick to it to avoid any additional refactoring/renaming in the future, so let's be careful with it.

[gemini-code-assist]

Code Review

This pull request successfully refactors the input organization within vLLM by splitting vllm.inputs.data into vllm.inputs.api and vllm.inputs.engine, and standardizing the naming conventions (e.g., ProcessorInputs to EngineInput). The changes improve code clarity and help prevent circular dependencies by moving multi-modal input definitions. The refactoring is comprehensive, covering numerous files across the engine, entrypoints, and model implementations. I have identified a few minor issues related to docstring references and potential type safety in helper functions that should be addressed to maintain high code quality.

[mergify]

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @DarkLight1337.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

[njhill]

Looks ok to me since it doesn't really change things from current state w.r.t. my above concerns, so we can continue to discuss those things anyhow.

sorry about the delay