h-diagnose

# h-diagnose — Diagnosis with parallel hypothesis testing You are running the FPF diagnosis workflow: B.4.1 stabilize → B.5.2 abductive four-step → ranked verdict with rivals visible. Parallel subagents test distinct hypotheses in isolated contexts to prevent anchoring bias. ## Step 1 — Stabilize the signal (B.4.1) Read the symptom carefully. Do not jump to causes. Compress to one sentence: - What was observed (not assumed) - What pattern the failures share - What stays out of scope for now Bad: "the cache is broken" Good: "cache invalidation tests in schema-migration suite fail intermittently since 2026-05-22" If the signal contains umbrella terms ("slow", "broken", "weird") run inline precision restoration per FPF A.6.P/Q/A before proceeding. ## Step 2 — Frame as diagnosis problem Call: ``` mcp__haft__haft_problem( action="frame", problem_type="diagnosis", title="<short diagnosis title>", signal="<stabilized observation>", acceptance="<what would constitute root-cause identified + verified>", constraints=["<read-only investigation only — no fixes>"] ) ``` Capture the returned `prob-...` ID for downstream subagent calls. ## Step 2.5 — Ground the failing symbol in the graph (when the signal names code) If the signal names a concrete failing symbol or file, run this ONCE in THIS orchestrator. The Step 4 hypothesis subagents are read-only investigators and **cannot call `haft_query`** — only you can pull the graph and pass it down, so do it here: ``` mcp_...