feat(doctor,shell): ollama host-service suggestion + hub-update hint (0.80.0)
Some checks failed
Security / Security check (push) Failing after 2s

Doctor: when the system AI uses an Ollama endpoint that no declared
host service covers (host:port match, /v1 suffix stripped), the
services panel says so in one sentence with a one-click 'declare as
host service' via the new DeclareService RPC — and states honestly
that it takes effect after a daemon restart (the restart button sits
on the same page). Pure suggestOllamaServiceEndpoint pins every
branch.

Shell: one slim, dismissible banner after connecting when the
release manifest offers a newer hub version; dismissal is persisted
per version so each release hints exactly once (pure
shouldShowUpdateHint + a widget test through the fake hub).
Deliberately manifest-based — Studio and hub versions are
independent counters, so a direct comparison would be wrong;
unreleased dev skew stays with the per-page classified states.
The probe stays inert under the test probe override: its timeout
timer leaked into hub_banner_test (the hermeticity class again).

Signed-off-by: flemming-it <stefan.a.flemming@googlemail.com>
This commit is contained in:
flemming-it 2026-07-23 00:03:42 +02:00
parent 351c5a82bc
commit 14f824b8ef
13 changed files with 703 additions and 135 deletions

View file

@ -6,6 +6,23 @@ lockstep.
## Unreleased
### Added (0.80.0)
- **Ollama joins the host services.** Ollama-backed store entries
now declare `requires_services: [ollama]` hub-side, and the
doctor's services panel notices when the system AI uses an Ollama
endpoint that is not declared as a host service: one plain
sentence plus a one-click "declare as host service" (via the new
DeclareService RPC; states honestly that a daemon restart is
required).
- **The shell says when a hub update exists.** One slim, dismissible
banner after connecting when the release manifest offers a newer
hub version — dismissal is remembered per version, the doctor
page keeps the apply button. (Deliberately manifest-based:
Studio and hub version numbers are independent counters, so a
direct comparison would be wrong; unreleased dev skew stays with
the per-page "needs a newer hub" states.)
### Added (0.79.0)
- **Maintainers in the store.** The detail sheet always answers "who