---
title: "The Gap Checker Called a Deliberate 0.1 Missing"
canonical: https://dxdev.com/everyday-ai/check-whether-the-bug-still-exists-first/
datePublished: 2026-10-13
---
The question on the ticket was whether a false alarm was real: our gap checker flagged a deliberate Story Points value of 0.1 as missing. The fix was already in, so the agent changed no code and made no commit.

## The false alarm

The old check flagged any value under 1, so the deliberate 0.1 default our tooling sets read as missing. One item on a larger ticket asked whether that false positive was real, and it turned out to be already fixed. I handed the question to an AI agent.

## What was already on main

A commit on origin/main had changed the gap-check script to flag only a blank or zero value, written in the code as `pts <= 0`. So 0.1 passes and zero still gets flagged.

The agent checked that against the live ticket as well as the code. The ticket holds `customfield_10022` = 0.1. A read-only scan of the last 30 days found no gaps at all, so there were no Story Points gaps and that ticket was not in the gap list.

The tests agreed. The false-positive test file passes, 13 tests, and it already has the 0.1 regression case and a case where zero stays flagged. The agent added nothing, so there was no fails-before/passes-after run and no gate.

## What the agent left alone

The state file for the close-gaps run still holds an old dedupe signature for that ticket's Story Points, last stamped 2026-09-23. It is stale history rather than an open gap row. The agent did not edit it, because whether to clear it is the manager's call, and it found no supported command for that.

It also did not run `close-gaps scan`, because without `--no-notify` that command can notify and touch state. Instead it used two read-only scripts: one fetches the raw [field from the ticket](/blog/2026-09-07_schema-visibility-enables-triage/), and one calls the gap finder over the last 30 days and reads the state file.

It posted its verdict as a comment on the larger ticket and did not transition or close it. Item 4 was the last open item on that ticket.

## Where it ended

The check flags only a blank or zero value, `pts <= 0`, and the ticket holds 0.1 in `customfield_10022` and sits in no gap list. The only trace of the false alarm left is a stale dedupe signature stamped 2026-09-23 in the state file, and clearing it is the manager's call.