feat(mingo): wire Guide Mode V3 source metadata and remote tools

[pavlo-flamingo]

Depends on flamingo-stack/openframe-oss-lib#2115. Pinned to its prerelease 0.0.610-2115.5931.1; swap to the plain release once that merges.

What this is

The lib half decodes an answer's GUIDE/SOURCES metadata and renders its citation strip and entity cards. This is the app half: fetching that metadata back on reload, gating the remote tools behind their flag, and giving the cards a working Display action.

It replaces the vibe-coded #313, which pinned the lib to a prerelease off an unmerged branch 45 commits behind main — regressing the package ~19 releases for the whole app.

History

dialogs-queries selects GuideData.payload, so a reloaded dialog shows the citations the live turn did.

Two constraints shaped the fragment:

• GuideData.text is deliberately not selected. Payload-only records persist it as an empty string, which replays as an empty text segment.
• SourcesData is not named at all. It is the contract the backend is moving to, but it is not in the tenant schema yet, and a fragment on a type the schema lacks fails the whole query — not just that selection. The lib decoder accepts both names, so switching later is a one-line change here.
• AskData.text is aliased. It is nullable where TextData.text is not, and GraphQL's SameResponseShape rule rejects the entire query over that conflict rather than the one field.

Flag

ai-mingo-remote-tools. With it off, the slash-command list is filtered to the four commands the backend's HubMcpPromptPolicy.REPLACED_LOCAL_COMMANDS allows MCP prompts to replace.

The interceptor awaits the flags rather than reading them optimistically (whenFeatureFlagsResolved()). It rewrites a response the lib caches with staleTime: Infinity, so a guess made before the flags land is not a brief flicker — it is the command catalog the panel keeps for the rest of the session. The filter itself is a pure function, so the policy is testable without mounting a panel.

Display action on cards

Built from the ref's own sourceRepo, falling back to a documentType→table map, and only when the catalog actually has a display action for that source: offering it for a search-only source would run a query instead of showing the row, so the affordance does not render at all on a V2 catalog. The invocation goes through the lib's quoting helper rather than a second escaping rule here.

One note on the mapper

mapMingoMessageToUnified spreads what it does not destructure, so per-message metadata the lib adds later rides through without a change here. That is the same seam that silently dropped sources/refs on the lib side — a mapper that enumerates fields is the shape of that bug, and its test asserts the pass-through rather than the field list.

Before merge

@flamingo-stack/openframe-frontend-core is pinned to 0.0.610-2115.5931.1, the prerelease built from openframe-oss-lib#2115. Exact, not caret — a caret range on a prerelease matches only other prereleases of the same version, which is not what a ^ reads as. Swap it for the plain release once #2115 merges.

Verification

tsc ✓, lint:ci ✓, Prettier ✓, 203 tests ✓ (22 new, covering the history normalizer, the visibility policy, the flag gate and the display-command builder) — all run against the published prerelease, not a local link. npm run test:node is unchanged at 30/1: the registration-attribution failure is pre-existing on main.