feat(connections): Harmoniqs Cloud is connectable where Pasqal is

[Rchari1]

The reports

1. "where is our harmoniqs cloud, where can I put an API key in"
2. "I literally tried to switch to piccolissimo and it did not ask me for an API key"
3. "it's not a prompt that should ask, it should be integrated in like how pasqal is connected"

Why both happened

Both trace to amicode#200, and neither was a broken wire.

statusTabConnections() filtered company-compute out of the Connections tab and connectionTitle() renamed it "Solver API key", moving the whole connect flow inside the solver capsule's collapsed card. The reasoning was sound in isolation — one credential for one service, not a second product. The effect was not: Pasqal Cloud rendered as a connectable service in the place that lists clouds, and ours did not. So people went looking for Harmoniqs Cloud exactly where Pasqal is, and found nothing.

Report 2 has a different cause and is not a bug: with a valid key on file hpClickAction("connected") returns "activate", so clicking HP switches immediately instead of re-asking. Correct — but the status dot lived inside the collapsed card, so the row had no way to say "you're already connected," and a successful switch was indistinguishable from a no-op. (Verified live: the server reported company-compute → state: "connected", identity raghav-internal.)

Changes

• statusTabConnections() no longer filters. Harmoniqs Cloud renders as a card beside Pasqal Cloud, using the base-url-token form (Service URL + API key) the tab already supported for non-Pasqal ids — so this un-hides a working flow rather than building a new one. Kept as a function so there's still one obvious place to filter a genuinely internal connection later.
• connectionTitle() → "Harmoniqs Cloud". In a list whose other entry is "Pasqal Cloud", "Solver API key" read as a settings field rather than our service — and Harmoniqs Cloud is the name every downstream refusal already uses (amico-run's local-launch refusal, the hpc gate).
• The solver row states its connection state — CONNECTED / CHECK KEY / ADD KEY. Text rather than a bare dot: Kate's idiom is that the dot accompanies words, words survive colour-blindness and a screenshot, and it says what a click will do.
• HP row tooltips name Harmoniqs Cloud, and the connected one states the consequence: every solve on this solver runs there.

Not changed

The wire id stays company-compute — renaming it would break the credential route, the status cache, and CONNECTION_IDS for no user-visible gain. Both entry points (tab and capsule) write the same credential, so connecting in either shows up in both.

Testing

ui: 57 pass. turbo typecheck: 23/23. Strings verified present in the built darwin-arm64 binary, which is vendored and serving the running dev host.

The two filter tests that pinned #200's removal are rewritten to pin the opposite, with the regression spelled out — including that a compute-only list must still render a card rather than hit the empty state.

Reviewer note

This reverses a deliberate #200 decision (Kate's, on presentation grounds). Worth a look from her: the disagreement is only about where the credential is entered, not about the one-credential model, and the capsule affordance is untouched.