fix(flows): only offer install for capabilities the store resolves

The capability set behind the flow editor's Install quick-fix and
the flow list's install badge ingested every store entry's
requiresCapabilities (dependencies, not provided capabilities) and
ignored entry status/kind. Clicking Install on such a capability
ended in the hub's "no store entry for '<name>'" error.

The set now mirrors the hub's install resolver (entry names only,
no planned or federated entries) via installableStoreCapabilities()
with unit tests for both classification states. Unresolvable
capabilities render the editor's 'not in store' state, which
explains the three recovery paths before any click; the editor pin
moves to 0.25.0 (commit-pinned until its tag exists) and the dialog
harness captures the badge states light+dark. Studio 0.78.0.

Signed-off-by: flemming-it <stefan.a.flemming@googlemail.com>

CHANGELOG.md

@@ -6,6 +6,23 @@ lockstep.
 
 ## Unreleased
 
+### Fixed — honest install badge in the flow editor (0.78.0)
+
+- **Install is only offered when the store can deliver.** The
+  capability set behind the flow editor's Install quick-fix and the
+  flow list's install badge previously ingested every store entry's
+  `requiresCapabilities` (dependencies, not provided capabilities)
+  and ignored entry status/kind — so clicking Install on such a
+  capability ended in the hub's "no store entry for '<name>'" error.
+  The set now mirrors the hub's install resolver: entry names only,
+  no `planned` entries, no federated entries
+  (`lib/data/store_caps.dart`). Capabilities the store cannot
+  resolve render the editor's "not in store" state, which explains
+  the three recovery paths (local install, add store, configure
+  integration) before any click.
+- Flow editor pinned at 0.25.0 (store-resolvability split in the
+  flow list, three-path analyzer message).
+
 ### Added — real trust + exposure data (0.77.0)
 
 - **Per-entry install verification.** The hub now reports (since