fix: Merge conflict build error

[grahamking]

It moved packages

Signed-off-by: Graham King grahamk@nvidia.com

Summary by CodeRabbit

• Refactor
  • Updated internal classification imports without changing any user-visible behavior.

[github-actions]

PR Preview Action v1.8.1
🚀 View preview at https://NVIDIA-NeMo.github.io/Switchyard/pr-preview/pr-500/
Built to branch gh-pages at 2026-08-20 17:38 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: f7c984e5-ce2e-4283-b9d2-92395c583de6

📥 Commits

Reviewing files that changed from the base of the PR and between 7cc517f and 2c19e86.

📒 Files selected for processing (1)

• crates/libsy/src/algorithms/passthrough.rs

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

Walkthrough

The passthrough algorithm now imports ClassifyTrigger from util::affinity instead of util::turn_pin. The AffinityRouter import remains unchanged.

Changes

Passthrough import update

Layer / File(s)	Summary
Update ClassifyTrigger import crates/libsy/src/algorithms/passthrough.rs	The import source for ClassifyTrigger changes to util::affinity. The AffinityRouter import remains unchanged.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 2c19e

This is a small localized package-related change, and no actionable merge-blocking risk remains after normal checks and review.

Poem

I’m a rabbit with a tidy ear,
Watching imports hop and steer.
ClassifyTrigger found its place,
In affinity’s proper space.
One small change, the path is clear!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the merge-conflict build error fixed by the import change.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

_{Comment @coderabbitai help to get the list of available commands.}