Tests pin down chain ordering (including ties), BaseAdvisor stream behaviour, redaction order versus memory and logging, the tool loop, and how a refusal surfaces on calls, streams and over HTTP. Co-Authored-By: Claude Sonnet 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Ja4jkzrbQ4LQZBNrb5mkZE
9 lines
347 B
Plaintext
9 lines
347 B
Plaintext
# Advisor chain: what decides who runs first
|
|
|
|
registered as C300, A100, B200 (the number is HIGHEST_PRECEDENCE + n)
|
|
call: A100> B200> C300> model C300< B200< A100<
|
|
stream: A100> B200> C300> model C300< B200< A100<
|
|
|
|
plus one advisor added on the request with .advisors(...) at n=150:
|
|
call: A100> R150> B200> C300> model C300< B200< R150< A100<
|