Problem
Legacy ACP sessions now receive standing context once per live Buzz session. If the provider compacts that context away while the session remains live, Buzz has no signal or threshold that causes the persona/base/system context to be sent again.
Desired outcome
Choose and implement a policy for legacy providers, such as:
- re-deliver standing context after a turn/token threshold;
- configure a non-zero session rotation default; or
- use a provider capability/signal when available.
The policy must avoid restoring the old behavior of repeating all standing context on every turn.
Follow-up from #5342 session-context delivery work; this is a product/session-lifecycle decision rather than a defect in the bounded delivery-state change.
Problem
Legacy ACP sessions now receive standing context once per live Buzz session. If the provider compacts that context away while the session remains live, Buzz has no signal or threshold that causes the persona/base/system context to be sent again.
Desired outcome
Choose and implement a policy for legacy providers, such as:
The policy must avoid restoring the old behavior of repeating all standing context on every turn.
Follow-up from #5342 session-context delivery work; this is a product/session-lifecycle decision rather than a defect in the bounded delivery-state change.