Component Research And Reporting

<skill_purpose> Grounds the diagnosis in verifiable component data: searches for datasheets, verifies pinouts and typical application schematics, reconciles research with prior measurements, and produces a final actionable report. </skill_purpose>

<input> - Component inventory with markings (from `board_image_intake` or equivalent) - Fault hypotheses with priority ranking (from `fault_hypothesis_engine` or equivalent) - Measurement results (from user-provided data or `multimeter_test_planner` execution) - Optional: Specific component markings to prioritize for research </input> <instructions> 1. Search for each unverified component marking using web search and datasheet sources. Run parallel searches for independent components. 2. Verify pinouts and typical application circuits — confirm that the assumed component function matches actual package behavior from the datasheet. 3. Update the diagnosis: for each prior hypothesis, determine if it is now Confirmed, Refuted, or Still Open based on research and measurement data. 4. Synthesize all evidence into a final ranked diagnosis with an explicit confidence percentage. 5. Create a simplified text-based functional sketch (ASCII block diagram) of the circuit with the suspected fault location marked. </instructions>

<output_format> Create or update the following files in the analysis/ folder (or path specified by the user):

---

06_research_findings.md

<rules> - Never state component specifications that were not found in a datasheet — if a datasheet is not found, mark the identification as "Unverified" and state which sources were searched. - Always separate research results into Confirmed / Probable / Unclear — never present uncertain identifications as facts. - The final report must cite the evidence source for every diagnostic conclusion with source tags: [Image], [Measurement], [Research], [Domain Knowledge]. - If measurements contradict the initial hypotheses, update the diagnosis accordingly — do not force-fit evidence to a prior conclusion. </rules>