Catch Go bugs that fuzzing misses with Gemini and a constraint solver

The author describes a workflow that compiles Go functions to RISC-V assembly, has Gemini 4 Argon translate the surviving runtime.panicBounds traps into Z3 constraints, and replays any satisfying input through go test to produce a real reproducer. The pipeline caught three planted bugs and three latent bugs in skill-lint, and the post explains why go test -fuzz missed two crashes because fuzz inputs usually have spare slice capacity, fixed by clipping capacity to length with a full slice expression. It also notes that an unsat result only means "maybe correct," since the LLM-written solver model is not a sound proof system.