tking/gsh
SHA256
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix: skip session lifecycle CRs, fix CR evidence schema

Browse source 
Session start/end CRs used invalid outcome values (session_started,
session_ended) not in broker's Outcome enum, causing 422. Also, broker
consumes AC on first CR, blocking subsequent per-command CRs.

Skipped session lifecycle CRs until session-scoped AC model is
implemented. Per-command CRs still post on governed command completion.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Tyler J King 2026-04-02 23:15:34 -04:00
parent e7bc2ee2b4
commit 740fcdb3b5
1 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
gsh/src/human.rs
View file

@ -30,7 +30,8 @@ pub fn run_human_mode(
// Post SESSION_STARTED CR if broker available: // Post SESSION_STARTED CR if broker available:
if let Some(ref base) = broker_url { if let Some(ref base) = broker_url {
if let Ok(client) = build_client(token) { if let Ok(client) = build_client(token) {
let _ = post_cr(&client, base, &session.ac_id, "session_started"); // Session start CR skipped — broker consumes AC on first CR,
// which would block per-command CRs. Needs session-scoped AC model.
} }
} }
@ -121,7 +122,7 @@ pub fn run_human_mode(
// Post SESSION_ENDED CR: // Post SESSION_ENDED CR:
if let Some(ref base) = broker_url { if let Some(ref base) = broker_url {
if let Ok(client) = build_client(token) { if let Ok(client) = build_client(token) {
let _ = post_cr(&client, base, &session.ac_id, "session_ended"); // Session end CR skipped — same AC consumption issue as session start.
} }
} }