feat: re-enable session lifecycle CRs with session_end outcome
Broker now supports session-scoped ACs that stay active across multiple CRs. Session start posts 'completed' CR, session end posts 'session_end' CR which consumes the AC. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
740fcdb3b5
commit
ff16b5642e
1 changed files with 2 additions and 3 deletions
|
|
@ -30,8 +30,7 @@ pub fn run_human_mode(
|
|||
// Post SESSION_STARTED CR if broker available:
|
||||
if let Some(ref base) = broker_url {
|
||||
if let Ok(client) = build_client(token) {
|
||||
// Session start CR skipped — broker consumes AC on first CR,
|
||||
// which would block per-command CRs. Needs session-scoped AC model.
|
||||
let _ = post_cr(&client, base, &session.ac_id, "completed");
|
||||
}
|
||||
}
|
||||
|
||||
|
|
@ -122,7 +121,7 @@ pub fn run_human_mode(
|
|||
// Post SESSION_ENDED CR:
|
||||
if let Some(ref base) = broker_url {
|
||||
if let Ok(client) = build_client(token) {
|
||||
// Session end CR skipped — same AC consumption issue as session start.
|
||||
let _ = post_cr(&client, base, &session.ac_id, "session_end");
|
||||
}
|
||||
}
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue