get_blueprint_info should still report md data if UE editor closed

[kvirani]

Currently it doesn't even proxy the cached md back. It should do that
And then of course for the rest of the data it can, for now, say that the Editor is not open so 🖕🏽

[kvirani]

Investigation & Plan

I traced the full get_blueprint_info flow through the Rider plugin. Here's what's happening and what to fix.

Current Behavior (editor closed)

The handler (BlueprintInfoHandler.cs) does three things per blueprint:

1. Audit data (line 61) - calls FindAuditEntry() which reads cached .md files from Saved/Fathom/Audit/v7/. This works offline, no editor needed.
2. Dependencies (lines 69-75) - proxied to UE editor via AssetRefProxyService. Skipped when IsAvailable() is false, leaving the field null.
3. Referencers (lines 78-84) - same proxy pattern, also null when offline.

So the audit data IS being fetched from disk cache. But two problems make the response misleading:

Problem 1: JSON response omits EditorAvailable
The BlueprintInfoJsonEntry model (line 248) has Audit, AuditContent, Dependencies, Referencers but no EditorAvailable flag. A JSON consumer sees Dependencies: null, Referencers: null with no way to tell if that means "editor is off" vs "this blueprint has no deps."

Problem 2: Markdown buries the audit data
The markdown output shows the audit section (good), but then Dependencies and Referencers sections each say "UE editor not running. Start the editor with FathomUELink plugin to see asset references." An MCP/AI consumer reading this may interpret the overall response as "unavailable" rather than recognizing the audit data above is valid and useful.

Proposed Fix (1 file: BlueprintInfoHandler.cs)

1. Add EditorAvailable to JSON response - Add the field to BlueprintInfoJsonEntry so JSON consumers can distinguish "editor off" from "no results."

2. Add a top-level status line in markdown when editor is offline - Before the per-blueprint sections, add something like:

   Note: UE editor is not running. Audit data shown below is from cache. Dependencies and referencers require a live editor connection.

3. Simplify the per-section offline message - Instead of repeating the full "Start the editor..." message in both Dependencies and Referencers sections, use a shorter note like "Requires live editor connection (see note above)."

4. Ensure audit staleness is surfaced - If the cached audit entry IsStale, include that in the response so consumers know the data may be outdated.

Difficulty

Low. Single-file change, straightforward model/formatting updates. No architectural changes needed. The audit retrieval path already works offline; this is about making the response clearer about what's cached vs what's unavailable.