gitea-admin/CASAN
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: keep goal failure reasons gate-specific

Browse Source
This commit is contained in:
thanhnv
2026-07-18 10:04:55 +07:00
parent 1ffe5fe3df
commit efb5a62f29
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/casan-harness/scripts/bash/goal-orchestrator.py
+7 -2
View File
@@ -802,8 +802,13 @@ def run(job_path: str) -> int:
job = load_json(job_path)
audit_hash = audit(job, "failed")
emit(goal_id, "H5-governance", "pass", "Failed decision anchored", {"audit_hash": audit_hash})
emit(goal_id, "H6-agentops", "error", "Orchestration failed", {"reason": reason, "latency_ms": int((time.monotonic() - started) * 1000)})
emit(goal_id, "H7-orchestration", "blocked", "Goal workflow stopped", {"reason": reason})
# Keep gate semantics distinct. H2 may report a patch-contract failure,
# while H6/H7 must report their own lifecycle state and retain the H2
# error only as causal evidence. Reusing `reason` here made the UI show
# goal_patch_missing as if telemetry and orchestration independently
# failed the patch contract.
emit(goal_id, "H6-agentops", "error", "goal_orchestration_failed", {"root_reason": reason, "latency_ms": int((time.monotonic() - started) * 1000)})
emit(goal_id, "H7-orchestration", "blocked", "goal_workflow_stopped", {"root_reason": reason})
update_job(job_path, audit_hash=audit_hash)
return 2