feat(tools/e2e): limits harness saturation probe (verdict from an observation window) - #397
Merged
Minipada merged 2 commits intoAug 19, 2026
Conversation
… observation window) A pure function over a chronologically ordered window of ack-latency, unacked-window-depth, disk-buffer, and outage-declared observations, deciding saturated/not-saturated/insufficient-data and naming the binding signal in the PRD's stated priority order: latency crossing its bound and staying there, then unacked-window growth, then disk-buffer growth at steady state — buffer growth during a declared outage never trips it, matching the PRD's explicit rejection of buffer utilisation as a signal. No container, no ramp controller yet — this issue is the verdict function alone, unit-tested in isolation. Closes #377 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011iv7L8vX7KgrAukeeXKfa6 Signed-off-by: David Bensoussan <d.bensoussan@proton.me>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011iv7L8vX7KgrAukeeXKfa6 Signed-off-by: David Bensoussan <d.bensoussan@proton.me>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## jazzy #397 +/- ##
=======================================
Coverage 68.09% 68.09%
=======================================
Files 102 102
Lines 6320 6320
=======================================
Hits 4303 4303
Misses 2017 2017
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
6 tasks
Minipada
deleted the
feature/377-limits-harness-saturation-probe-verdict
branch
September 2, 2026 12:45
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
tools/e2e/scripts/saturation_probe.py, a pure verdict function for Limits harness: measure where the pipeline saturates, on four axes #323's limits harness: given a chronologically ordered window of ack-latency / unacked-window-depth / disk-buffer / outage-declared observations, decides saturated / not-saturated / insufficient-data and names the binding signal.outage_declaredflag, matching the PRD's explicit rejection of a level threshold.min_observationsreturns an explicitINSUFFICIENT_DATAverdict, never a default healthy/saturated one.Closes #377
Test plan
uv run pytest tools/e2e/test/test_saturation_probe.py -v— 13/13 passing, covering all six acceptance criteria plus signal-priority ordering and the utilisation-vs-trend distinctionuv run pytest tools/e2e/test/— full suite (37 tests) still greenuv run ruff check/ruff format --diffcleanprek runon the changed files — all hooks pass🤖 Generated with Claude Code
https://claude.ai/code/session_011iv7L8vX7KgrAukeeXKfa6