Get the dependency graph showing which backend API routes each frontend route calls. Ask: "Which backend routes does /dashboard call?"

Get the QA report with route scores and root causes. Ask: "Show me all broken routes" or "What is the overall score?"

Live-probe a single endpoint right now and return its status. Ask: "Is GET /alerts returning data right now?"

Explain in plain English why a specific frontend route is showing no data or failing. Ask: "Why is /rules showing no data?"

Get a step-by-step fix guide for a root cause category. Ask: "What do I do about feature_flag_disabled issues?"

Find out how many frontend routes would break if a backend endpoint goes down. Ask: "What pages break if GET /alerts goes down?"

Trigger a full qa-probe pipeline (analyze + probe + report) and return a summary. Ask: "Run a full QA check and give me the summary."

Record feedback on an endpoint diagnosis so qa-probe reapplies it on future runs. Use this to teach the tool: mark a result as expected/known (suppresses the finding) or confirm it as a real bug. Example: "mark the empty GET /alerts result as expected".