Confirm, drop, reject · nth Labs help

A finding without a verdict is a suggestion. The verdicts are what turn the list into a record, and they are the only thing calibrating the confidence numbers.

The four

Verdict	Means	Effect
`confirm`	Real, and it is work.	Mints a standing re-check. Counts as the tool being right.
`wontfix`	Real, and you are not fixing it.	Still counts as the tool being right. Leaves the ledger.
`reject`	A false positive.	Costs precision, and calibrates future runs against the mistake.
`done`	Fixed.	Waits for a re-check to prove it, rather than closing on your word.

Reject is the valuable one

It is the only verdict that costs the tool something, and the only one that changes what it does next. A rejected finding is recorded as a miss, drags the precision figure down, and is fed back so the same class of mistake is scored lower on this product in future.

The review screen: one finding at a time, with keyboard shortcuts to confirm, drop or skip it. — One finding at a time. Confirming is what mints a standing check; dropping is recorded rather than silent.

Which means: reject things. A list you only ever confirm teaches nothing, and the confidence percentages stay uncalibrated no matter how many runs you do.

Wontfix is not reject

The distinction is deliberate and it matters to the numbers. “This is real and I am not doing it” is the tool being correct; “this is not a thing” is the tool being wrong. Collapsing them into one button would make the precision figure meaningless.

Doing it

In the console, the Review screen does one at a time, keyboard-first. From the command line:

node cli.cjs actions list
node cli.cjs actions confirm <id>
node cli.cjs actions wontfix <id> "known, tracked in LIN-402"
node cli.cjs actions reject  <id> "the field is hidden on purpose"
node cli.cjs actions why     <id>

The note on wontfix and reject is optional and worth writing: it is what the next person reads instead of asking you.