ktsu.DelegateTransform references ktsu.ScopedAction but never uses it, so every consumer pulls in an unused transitive package

[matt-edmondson]

What's wrong

DelegateTransform/DelegateTransform.csproj:5 has <PackageReference Include="ktsu.ScopedAction" />, with its version pinned in Directory.Packages.props:6, but no source file uses anything from ScopedAction. A search of every .cs file in the repo finds no ScopedAction reference.

Why it matters

The reference isn't PrivateAssets="all", so it flows into the published nuspec. Every consumer of ktsu.DelegateTransform restores ktsu.ScopedAction and its own dependency closure for nothing. That also means every ScopedAction release triggers a dependency bump here, and a version conflict for consumers who pin ScopedAction themselves.

Suggested fix

• Remove the PackageReference from DelegateTransform.csproj and the PackageVersion from Directory.Packages.props, if nothing else in the solution needs it.
• Drop it from the dependency list in CLAUDE.md.
• Confirm the build and tests still pass on all target frameworks.

[matt-edmondson]

Triage

• Category: Improvement
• Priority: Low. Nothing is broken. It adds an unused transitive package to every consumer, and it causes dependency-bump churn every time ScopedAction is released.
• Area / suggested assignee: DelegateTransform.csproj and Directory.Packages.props. @matt-edmondson. This fits the clean-package-refs sweep.
• Duplicates: None. It is unrelated to DelegateTransform.With(...) fails to compile (CS0234) from any code in a ktsu.* namespace, and the README's mapping example can't compile anywhere #76 (the CS0234 namespace clash).
• In progress: No open PR covers it.
• Notes: Removing a dependency from the nuspec is technically visible to consumers who relied on it transitively. That is unlikely here, but it is worth noting in the release notes.

---

Generated by Claude Code