v2.195.0

Fixed — docker_apps.rs registry/ollama handlers had no argv-position validation

registry_login/registry_logout passed the admin-supplied registry server
straight into docker login/docker logout with only an emptiness check —
a server starting with - is parsed by docker's own CLI as a flag in that
position, not a registry host. Both now validate with is_valid_image_ref,
the same validator already used a few hundred lines away for change_image's
image field. ollama_pull_model/ollama_delete_model already validated
model-name length and character class but were missing the equivalent
leading-- guard before docker exec ... ollama pull/rm <model>; both now
reject a leading -, matching is_valid_image_ref's existing behavior for
the same threat class. All four are DiD-only (admin-authority endpoints;
safe_command's .args() already rules out shell injection) — named
alongside the (now closed) on_call/escalation_policies tenant-scoping fix
in project_dockpanel_tech_debt_p4's long-standing carry list.

---

Install: curl -sL dockpanel.dev/install.sh | bash

Every release is installed on a throwaway VPS and driven as a user before
it ships. What that means, and what it has found, is written up at
https://docs.dockpanel.dev/testing.html.

Binaries are static musl builds signed with Sigstore; checksums.txt
and the .sig/.pem pairs are attached below.

Full changelog: v2.194.0...v2.195.0