[yzhautouskay]

What does this PR do?

Route TP shard resolution and hook installation through _get_tp_plan(). It returns the existing class-level plan by default, preserving current behavior.

This enables configuration-dependent plans without modifying the class attribute. Cosmos 3 needs this because SiLU uses gate_proj layers while ReLU2 does not – differs between model flavors. Extracted from #15137, needed here https://github.com/huggingface/diffusers/pull/15137/changes#diff-2e4d21f189d670c5f6d027711540b335373c8ab2eaff5bf10471ec8dc2e945b5R405, as requested in review

Before submitting

• Did you use an AI agent (Claude Code, Codex, Cursor, etc.) to help with this PR? If so:
  • Did you read the Coding with AI agents guide?
  • Did you run the self-review skill on the diff?
  • Did you share the final self-review notes in the PR description or a comment?
• Did you read the contributor guideline?
• Did you read our philosophy doc? (important for complex PRs)
• Was this discussed/approved via a GitHub issue or the forum? Please add a link to it if that's the case.
• Did you make sure to update the documentation with your changes? Here are the
  documentation guidelines, and
  here are tips on formatting docstrings.
• Did you write any new necessary tests?
• Are you the author (or part of the team) of the model/pipeline (only applicable for model/pipeline related PRs)?

Who can review?

@sayakpaul

Core library:

• Schedulers: @yiyixuxu @dg845
• Pipelines and models: @yiyixuxu @dg845 and @asomoza
• Training examples: @sayakpaul @linoytsaban
• Docs: @stevhliu and @sayakpaul
• MPS: @pcuenca
• General functionalities: @sayakpaul @yiyixuxu @DN6

Integrations:

• deepspeed: HF Trainer/Accelerate: @SunMarc
• PEFT: @sayakpaul @BenjaminBossan

HF projects:

• accelerate: different repo
• datasets: different repo
• transformers: different repo
• safetensors: different repo

-->

[sayakpaul]

Thanks!

Could you also preserve the contribution history?

[HuggingFaceDocBuilderDev]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

[github-actions]

Hi @yzhautouskay, thanks for the PR! It does not appear to link an issue it fixes.

• If this PR addresses an existing issue, please add a closing keyword (e.g. Fixes #1234) to the PR description so the issue is linked.
• If you are the author of the model/pipeline this PR relates to, or part of the team we work with on it, tick the Are you the author (or part of the team we work with) of the model/pipeline this PR relates to? box in the PR description (if you removed the template, paste that line back, checked). This reminder then no longer applies.
• Otherwise there is nothing you need to do: a maintainer will look at the PR and add the no-issue-needed label to silence this reminder if it should stay open without an issue.

See the contribution guide for more details.

Please note that PRs without a linked issue are likely to be automatically closed 10 days after this notice.

Once the PR links an existing issue, the author box is ticked, or the no-issue-needed label is added, you can ignore this message — it stays here as a comment, but it no longer applies.