futpib / slopd / 25628443091

85%

Build Type

push

github

Committed by futpib

Commit Message

feat: jq-style payload paths for --until and new --where

The --until predicate on `wait` (and existing payload_match wire field
on EventFilter) only handled flat key-equality. That made cases like
"the next assistant message that contains a text block" unworkable,
since `message.content` is an array and the text block's index
depends on whether Claude emitted thinking blocks first.

The path syntax now mirrors a useful subset of jq:
- `foo` or `.foo` — object key (leading `.` optional)
- `foo.bar` — nested object access
- `foo[]` — any element of an array (succeeds if any element matches
  the rest of the path)
- `foo[3]` — specific index
- combinations: `messages[].content[].type`

Comparison stays string-equal against the reachable scalar; arrays
and objects never match a scalar value. Added scalar normalisation
for null/bool/numbers so users can write --until 'b=true' or
--until 'n=42' without surprises.

Same syntax is now exposed as `--where KEY=VALUE` on both `listen`
and `wait`. --where pushes the predicate down to slopd via a new
EventFilter::payload_path_match wire field (additive, defaults to
empty so old daemons and clients keep working). Use --where when you
want non-matching events filtered out at the daemon; use --until on
wait when you want to see every event but stop on a specific one.

Path validation runs before the daemon connection so a typo'd
predicate now produces a clear error rather than the misleading "no
such socket".

Tests: 11 new libslop unit tests for the path parser/matcher; 3
integration tests covering the motivating array-path case for
--until, server-side enforcement of --where, and pre-connection
predicate validation.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Coverage Stats

182 of 186 new or added lines in 3 files covered. (97.85%)

205 existing lines in 5 files now uncovered.

3360 of 3934 relevant lines covered (85.41%)

1091963.73 hits per line