v0.6.0 — progress reporting, loop log, status command
Highlights
- Progress and reporting rules: loops report at round and state-transition boundaries, never on a clock — no surveyed harness reports on a fixed time interval. The loop announces once where to look, and progress is checked by reading the executor's trail (files, receipts, commit history), never by interrupting the executor.
- The loop log: durable and orchestrated loops keep an append-only
loop-log.jsonlbeside the contract card — one JSON event per line, recording structure rather than content, with a machinestatuspaired with a narrativereasonper event. loopuccino status <card-file>: prints the loop's state, latest events, and next action from the card and the loop log.- Research basis: observability — OpenTelemetry GenAI agent spans, Langfuse's data model, community loop harnesses, and Anthropic's context-engineering guidance, each verified live.
Full changelog: CHANGELOG.md