Factory Triage

Investigate the source issue (GitHub, GitLab, Linear, Jira, or incident.io) behind this Factory work item, trace the history of related code, understand the architecture involved, and diagnose whether the issue is valid and what's actually causing it. Finish by posting your distilled understanding as a handoff and requesting the stage transition.

You are working in a bound Factory session. Complete the full investigation in one pass, then make factory_transition_work_item your terminal step, one transition request, repeated only if the governed transition rejects it and only with the rejection reason addressed. Never wait for or solicit human input mid-run; every decision point is yours to resolve.

Decision rule: at every fork, ambiguous reproduction, competing root-cause hypotheses, unclear issue framing, pick the answer the evidence best supports, proceed, and record the decision as an assumption for the terminal handoff. Reserve open questions for decisions a human genuinely must make (product intent, breaking-change tolerance, priorities); everything answerable from code, history, or common sense is an assumption, not a question.

Shell note: gh output often contains ANSI color codes that break jq. Use gh's built-in --jq flag instead of piping to jq, or prefix commands with NO_COLOR=1.