log-tail-qa

What problem does it solve?

Verifying that an asynchronous system actually emitted a specific log line (and doing so reliably) is hard, because the log may already contain historical entries, may buffer output, may rotate, or may stop growing without the expected event.

Core Features & Use Cases

• Bounded log waiting: Tails a log with a configurable timeout and fails deterministically instead of waiting forever.
• History vs tail semantics: Chooses include/exclude behaviour so the check correctly matches either “already happened” or “must happen after this starts”.
• Occurrence counting: Supports asserting N occurrences using line-based accumulation rather than first-match-only grep patterns.
• No-progress fail-fast: Detects when the log file stops growing across polls and rejects early when the system appears stuck or writes elsewhere.
• Evidence capture for audits: Saves the matched lines, surrounding context, and verdict details into the oracle evidence directory.

Quick Start

Use the log-tail-qa skill to verify that a regex pattern appears in the target log within a bounded time window and capture the matching lines plus tail context for audit evidence.