coulomb/activity-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Normalize Glas execution evidence
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
Build and Publish Container Image / build-and-push (push) Successful in 20s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a028de-e2c8-7732-8521-46a7fc5db82f
This commit is contained in:
tegwick 2026-08-22 23:11:52 +02:00
parent b933cf52c8
commit 7e81545b24
13 changed files with 528 additions and 33 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/runbook.md
View file

@ -465,6 +465,15 @@ curl -sS -X POST "http://localhost:8010/ops-runs/expire-leases" \
| `OPS_RUN_SLA_HOURS` | `1` | Stuck threshold in status |
| `ACTIVITY_CORE_WORKER_TOKEN` | unset | Harness claim auth |
Glas-backed workers may return the Glas 1.0 `GatewayResult` on complete or
fail. Activity Core persists only `result.execution_evidence` plus the existing
compact artifact fields; direct tool/model output and unknown provider blobs
are dropped. The run detail API and UI expose profile, rein, model, sandbox,
outcome, failure stage, duration, token counts, and commit/artifact references
from that safe envelope. If those fields are missing, inspect the executor
payload before assuming Glas ran; do not paste raw provider output into
`ops_runs.result`.
**Railiance rollout (T07):** full checklist with image import, migrate job,
smoke trigger, claim test, and dual-path residual: