A prediction routine returned a valid result. The command then failed before it could save that result.
This happened in spec-lane , a CLI I maintain that can estimate token usage for AI-assisted development from previous observations.
The command ran two related paths: estimate/v2 , which selects observations with matching conditions, followed by a v1 estimator over a broader population. The second path could throw even after the first had produced a prediction.
The surprising part was an assumption in the error handler: because v2's population was a subset of v1's, a v1 failure supposedly meant v2 must also have abstained.
That does not follow when the two paths select their nearest neighbors from different populations.
Eight observations worked.…