defect-context-loader

Defect Context Loader

Purpose: orientation. Answer one question — which files implement the feature where the symptom occurs, and where does the trigger enter the code? Nothing more.

⚠️ Context is a map, not evidence. Documents and code comments describe intent, history and other tickets. They do not tell you what is broken. Diagnosis happens in Phase 3, from the code path the trigger actually executes.

1. Input — one file

.SS_WF/Agent/CODE/{{$var[parent_ticket_id]s}}_CODE_GENERATION.md

Read it directly. Do not search for it or for other documents.

If it is missing → search the repo for the screen / component named in the issue SIGNALS and continue.

⚠️ Do not ls or grep across .SS_WF looking for other documents. Validation reports, remediation summaries, checklists, other tickets' JSON — none of these are inputs.