From 55c7c2a96d0fb21e627b64056bb66bb334603b68 Mon Sep 17 00:00:00 2001 From: tupe12334 Date: Mon, 5 Oct 2026 20:54:27 +0300 Subject: [PATCH] docs: describe back-to-back ack.sh calls in the README Since #223 (0.2.1) ack.sh can advance several states without the hook firing in between, so the README claim that the agent cannot skip ahead is no longer true. Document the actual guarantee: in-order, one state per ack, every ack audited. Closes #225 Co-Authored-By: Claude Opus 5.5 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f7ada58..f7213f5 100644 --- a/README.md +++ b/README.md @@ -49,7 +49,7 @@ agent retries → next item shown action approved ``` -Each checklist item requires one full hook invocation to acknowledge. The agent cannot skip ahead. +Items must be acknowledged in flow order: each `ack.sh` call advances exactly one state. `ack.sh` may be run several times in a row without retrying the gated action in between (since 0.2.1), so the hook does not guarantee the agent was shown every question before acknowledging it. The audit log records every ack. ---