Cs Issue Analyze

This is stage 2 of a three-stage bug workflow: it reads the issue report from stage 1, digs into actual code to find root cause, and presents you with 2-3 fix options before touching anything. The workflow is opinionated about not guessing. It forces file:line pinpointing, requires walking through the failure path versus normal path to find where things diverge, and won't let you skip to implementation without choosing a repair strategy. You'd trigger it after cs-issue-report confirms a bug is real. The checkpoint design is interesting: it makes you review root cause and pick a fix approach before moving to stage 3, which keeps you from autopilot merge disasters.