feat(libsy): add routed client callbacks

[sabhatinas]

Summary

• Add generic RouterCallback<D> hooks to the libsy routed-client loop.
• Add RoutedClientBuilder::callback(...) so clients register callbacks once, independent of the selected algorithm.
• Verify one callback implementation observes both random routing and LLM-classifier routing.

Validation

• cargo test -p libsy
• cargo fmt --all --check
• cargo clippy -p libsy --all-targets -- -D warnings
• git diff --check -- crates/libsy/src/client.rs crates/libsy/src/lib.rs

[nv-msvoboda]

@sir-merge-a-lot groom

[nv-sir-merge-a-lot]

Previous updates (collapsed)

🤖 sir-merge-a-lot

Resolving conflicts

🔄 sir-merge-a-lot is resolving conflicts on this MR.

Detected 2 conflicting file(s) (LOW). I'll update this comment with the result. This can take a couple of minutes.

---

🤖 sir-merge-a-lot

Merge analysis

Strategy: cherry_pick_with_resolution
Overall risk: LOW

Commits:

• e42e33cf feat(libsy): add routed client callbacks

Conflicts:

File	Type	Risk
crates/libsy/src/client.rs	modify/delete	low
crates/libsy/src/lib.rs	content	low

Resolution ladder trace

Rung	Result	Details
Server-side rebase	skipped	Skipped because conflicts were detected during local analysis; GitLab rebase would not produce a clean branch. Files: crates/libsy/src/client.rs, crates/libsy/src/lib.rs
Client-side rebase	skipped	Skipped because conflicts were detected during local analysis; using the conflict-resolution ladder instead of force-pushing a conflicted rebase. Files: crates/libsy/src/client.rs, crates/libsy/src/lib.rs
Rerere	miss	No cached rerere resolution matched the remaining conflicts. Files: crates/libsy/src/client.rs, crates/libsy/src/lib.rs
Mergiraf	resolved	Mergiraf resolved conflicts structurally. Files: crates/libsy/src/client.rs
Mergiraf	declined	Mergiraf ran but left conflicts in the remaining files. Files: crates/libsy/src/lib.rs
LLM	invoked	Escalating remaining files to LLM for bounded LLM resolution. Files: crates/libsy/src/lib.rs
LLM	failed	LLM could not produce an accepted resolution for the remaining files. Failure reason: llm_timeout. Files: crates/libsy/src/lib.rs
Human escalation	required	Resolution ladder exhausted; human intervention is required. Files: crates/libsy/src/lib.rs

Final failure reason: llm_timeout.

Why now: I analyzed 2 conflict(s) on sabhatinas/libsy-callbacks against grclark/feat/libsy-routers-poc (trigger: groom).
What I checked: file-level risk classification (2 LOW); conflict shapes (1 content, 1 modify/delete); commit spread (2 source-commit touch(es) across 2 conflicted file(s) (1 source commit(s) total)). Automated resolution ladder steps are captured in the trace below.
What I changed: nothing - automated resolution did not update the branch; the ladder exhausted and this PR needs human intervention.
Recovery: N/A - branch unchanged.

📖 The resolution ladder · How strategy is selected

---

🤖 sir-merge-a-lot

Resolving conflicts

🔄 sir-merge-a-lot is resolving conflicts on this MR.

Detected 5 conflicting file(s) (REGENERATE). I'll update this comment with the result. This can take a couple of minutes.

---

🤖 sir-merge-a-lot

Could not auto-resolve

⏱️ sir-merge-a-lot could not auto-resolve this MR in time.

I stopped after ~3 minute(s) because the automated resolution path was too slow or unavailable on this conflict, so I will not be resolving this MR automatically. It needs manual conflict resolution.

Resolved 4 of 5 file(s) before stopping. Re-invoke @sir-merge-a-lot-bot groom to have me try again now, or push new commits to the branch and I will retry automatically.

---

🤖 sir-merge-a-lot

Resolving conflicts

🔄 sir-merge-a-lot is resolving conflicts on this MR.

Detected 5 conflicting file(s) (REGENERATE). I'll update this comment with the result. This can take a couple of minutes.

---

🤖 sir-merge-a-lot

Could not auto-resolve

⏱️ sir-merge-a-lot could not auto-resolve this MR in time.

I stopped after ~3 minute(s) because the automated resolution path was too slow or unavailable on this conflict, so I will not be resolving this MR automatically. It needs manual conflict resolution.

Resolved 4 of 5 file(s) before stopping. Re-invoke @sir-merge-a-lot-bot groom to have me try again now, or push new commits to the branch and I will retry automatically.

---

🤖 sir-merge-a-lot

Resolving conflicts

🔄 sir-merge-a-lot is resolving conflicts on this MR.

Detected 5 conflicting file(s) (REGENERATE). I'll update this comment with the result. This can take a couple of minutes.

---

🤖 sir-merge-a-lot

Could not auto-resolve

⏱️ sir-merge-a-lot could not auto-resolve this MR in time.

I stopped after ~3 minute(s) because the automated resolution path was too slow or unavailable on this conflict, so I will not be resolving this MR automatically. It needs manual conflict resolution.

Resolved 4 of 5 file(s) before stopping. Re-invoke @sir-merge-a-lot-bot groom to have me try again now, or push new commits to the branch and I will retry automatically.

---

🤖 sir-merge-a-lot

Resolving conflicts

🔄 sir-merge-a-lot is resolving conflicts on this MR.

Detected 5 conflicting file(s) (REGENERATE). I'll update this comment with the result. This can take a couple of minutes.

🤖 sir-merge-a-lot

Could not auto-resolve

⏱️ sir-merge-a-lot could not auto-resolve this MR in time.

I stopped after ~3 minute(s) because the automated resolution path was too slow or unavailable on this conflict, so I will not be resolving this MR automatically. It needs manual conflict resolution.

Resolved 4 of 5 file(s) before stopping. Re-invoke @sir-merge-a-lot-bot groom to have me try again now, or push new commits to the branch and I will retry automatically.

[nv-msvoboda]

@sir-merge-a-lot groom

[nv-msvoboda]

@sir-merge-a-lot groom

[nv-msvoboda]

@sir-merge-a-lot groom

[nv-msvoboda]

@sir-merge-a-lot groom