From a1e35eceaf4d17409db1cf987525b378df597fee Mon Sep 17 00:00:00 2001 From: tegwick Date: Sun, 26 Jul 2026 13:52:42 +0200 Subject: [PATCH] Note live-proven coarse glas-harness integration on HARNESS-WP-0002-T03 The whole-run-as-one-dispatch_tool-call wrapper is live-proven now; the per-tool-call hook refactor this task describes remains open. Co-Authored-By: Claude Sonnet 5 --- ...SS-WP-0002-rename-and-glas-harness-alignment.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/workplans/HARNESS-WP-0002-rename-and-glas-harness-alignment.md b/workplans/HARNESS-WP-0002-rename-and-glas-harness-alignment.md index 0994ff6..8107382 100644 --- a/workplans/HARNESS-WP-0002-rename-and-glas-harness-alignment.md +++ b/workplans/HARNESS-WP-0002-rename-and-glas-harness-alignment.md @@ -58,9 +58,21 @@ repo's `runner.py`/`adapter.py` to expose it, so glas-harness can call into `rein-aharness` instead of `rein-aharness` only running itself via its own CLI/poll loop. +**Partially done, live-proven at the coarse level (2026-07-26):** +glas-harness's `glas_harness/reins/rein_aharness.py` implements the +contract today by shelling out to `agent-harness run --task-file ...` +as one opaque `dispatch_tool` call — proven live end-to-end (real +`ext.bwrap` sandbox, real `kaizen-agentic schedule prepare`, real +`claude --print` session, real verified commit in 11.4s). **Still +open:** this repo does not itself expose per-tool-call hooks — glas-harness +cannot yet intercept/policy-check individual tool calls mid-session, +only the whole run as a unit. That deeper refactor (runner.py driving +the Claude Code session turn-by-turn rather than one `claude --print` +call) is what remains of this task. + ```task id: HARNESS-WP-0002-T03 -status: todo +status: progress priority: high state_hub_task_id: "228e999c-807b-4456-a286-4e3ab4fc8e90" ```