Function TestParseInt_SignOnlyTripwire_KI2

parser_test.go:2456–2472

TestParseInt_SignOnlyTripwire_KI2 reproduces the live failure mode tracked as KnownIssue KI-2 / DEFECT-260726-3F95. It PASSES while the bug is present (ParseInt("-") returns (0, nil)) and FAILS the moment the one-line guard lands in bytes.go:parseInt, at which point KI-2 must be flipped to status: f

(t *testing.T)

//
// Reproduces: KI-2
func TestParseInt_SignOnlyTripwire_KI2(t *testing.T) {
	v, err := ParseInt([]byte("-"))
	// Tripwire: while the bug is present, the call returns (0, nil).
	if err != nil {
		t.Fatalf("KI-2 tripwire no longer reproduces: ParseInt(\"-\") err = %v (the bug has been FIXED — flip KI-2 to status: fixed and delete this tripwire)", err)
	}
	if v != 0 {
		t.Fatalf("KI-2 tripwire no longer reproduces: ParseInt(\"-\") v = %d (the bug has been FIXED — flip KI-2 to status: fixed and delete this tripwire)", v)
	}
	// Also exercise the `+`-prefixed variant for documentation: parseInt does
	// not treat `+` as a sign, so it hits the c < '0' branch and correctly
	// returns MalformedValueError. This row pins the asymmetry so a future
	// fix that accidentally widened the sign classifier surfaces here too.
	if _, err := ParseInt([]byte("+")); err == nil {
		t.Fatalf("ParseInt(\"+\") unexpectedly returned nil error — `+` is not a JSON number prefix")
	}
}

// Reproduces: KI-4
// TestSetTopLevelArrayBeyondLength_KI4 documents the open design gap