Unverified50% confidenceEventExact time
The 'transaction count preservation' check added by the author is a kind of property test, and within 30 seconds it caught the bug that had taken 3 days of manual investigation to find.
1
Sources
50%
Confidence
Long-term
Relevance
10/14/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedOne week the scanner gave a CRITICAL-level verdict on a completely harmless design skill repository—29 findings, the highest severity, but after manual review all 29 were false positives.69% similarUnverifiedFor one PR, the worker agent's tests, the independent verifier's tests, and the hidden evaluation tests all passed, but the reviewer found while reading the diff that creating two links within the same millisecond would cause the return order to be wrong, and reproduced the bug.67% similarUnverifiedLayered testing approaches for Agents include: unit-testing loop termination decisions with fixed inputs, replacing tools with stubs to verify the orchestrator's error handling, and regression-testing policy interception rules with recorded historical tool results.66% similarUnverifiedThree checks carry most of the evaluation work: comparing actual step counts against expected ranges, where runs that hit the step limit are cleanly separated from runs that finish in four steps; checking tool calls, where tools that were called but returned no usable result, and tools that should have been triggered but never were, have nowhere to hide; and checking the trajectory, i.e. the action sequence, which catches reruns, skipped steps and loops.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1029578API
curl https://kongchang.com/api/v1/knowledge/claims/1029578MCP
get_claim(id=1029578)