v0.19.1 - Per-Channel Hit Counts in Scan Summary (2026-03-18)¶

What Changed?¶

This release adds per-channel hit counts (hit1, hit2, hit3) to the thresholds_scanned.jsonl summary file generated by get_thresholds.py. Previously only the total event count was recorded. This change enables fit_thresholds.py to consume the summary file directly without loading individual event files.

What's New¶

Main Feature: Per-Channel Hit Counts in `thresholds_scanned.jsonl`¶

What it does: Each scan summary record now includes hit1, hit2, hit3 fields alongside the existing threshold1, threshold2, threshold3 fields. These count the number of events where each channel registered a hit (hit > 0) during that measurement run.

Summary record format:

{
  "type": "threshold",
  "status": "ok",
  "timestamp": "2026-03-18T12:00:00+09:00",
  "file_id": 0,
  "events": 38,
  "threshold1": 285, "hit1": 35,
  "threshold2": 1000, "hit2": 0,
  "threshold3": 1000, "hit3": 0,
  "mac_address": "aabbccddeeff",
  "kurikintons": "1.0.0",
  "kazunoko": "0.19.1"
}

Installation¶

Quick Start¶

# Get the release
git checkout v0.19.1

# Setup
task env:setup

# Run CLI
uv run kazunoko --help

What's Different from the Last Version?¶

🔧 Changed¶

get_thresholds.py: scan summary records now include hit1, hit2, hit3 per-channel hit counts alongside threshold1, threshold2, threshold3

Is It Safe to Upgrade?¶

Backward Compatible: Yes

Existing fields are unchanged; hit1/hit2/hit3 are added fields only
Scripts that read thresholds_scanned.jsonl and ignore unknown fields are unaffected

Tests Passed¶

✅ Builds without errors
✅ commitizen consistency check passed

Release Details¶

Date: 2026-03-18
Version: v0.19.1
Files Changed: 1
Commits: a36aa0a, 016a0a6

Next Steps¶

Update fit_thresholds.py to support reading thresholds_scanned.jsonl directly as an alternative input source