feat(deploy): host-native and Docker deployment for Ouroboros Desktop

[keXXpert]

Host-native and Docker deployment for Ouroboros Desktop

Summary

This pull request adds two complementary deployment layouts for running Ouroboros Desktop in headless environments on Linux (Ubuntu-first):

1. deploy/docker/ — containerized VPS profile: Docker Compose, env templates, systemd unit on the host, backup/restore, update with rollback, and diagnostics.
2. deploy/host/ — bare-metal profile: install and operate the app directly on the machine with parallel scripts, systemd integration, and the same operational surface (update, backup/restore, doctor).

The goal is a reproducible operator story: one entrypoint per profile, consistent metadata and ref tracking, and less ad-hoc glue on servers.

Why

Source and generic Docker instructions exist, but production-style VPS and “install on the host” flows benefit from a single scripted surface (install, update, rollback, backup, diagnose) aligned with how operators actually run services.

What’s included

Docker (VPS) profile — deploy/docker/

• install.sh — staged/resumable installer, interactive and non-interactive modes, one-line curl | bash style bootstrap.
• docker-compose.vps.yml, ouroboros-headless.service — compose stack plus host systemd integration.
• update.sh, backup.sh, restore.sh, doctor.sh, enable-browser-tools.sh, systemd-healthcheck.sh.
• common.sh — env helpers, security-oriented checks (bind mounts, secrets, file layout), compose wrappers, health wait, deploy metadata.
• README.md, .env.example — operator documentation and a safe template for required variables.

Host-native profile — deploy/host/

• Same operational ideas as Docker profile: install.sh, update.sh, backup.sh, restore.sh, doctor.sh, enable-browser-tools.sh, common.sh, systemd unit (ouroboros.service), health check helper.
• README.md, .env.example for host-specific paths and conventions.

Repository hygiene

• .gitignore — keep real .env files and secrets out of git while continuing to track deploy/**/.env.example as documentation; ignore local .deploy/ metadata used at runtime.

Notes for maintainers

• Scope is deployment and operations only; no changes to core agent or application logic in this branch.
• Linux/Ubuntu-first assumptions are intentional for both profiles.

Validation

• Local checks: bash -n on deploy shell scripts where applicable; review of compose and systemd units.
• (No new GitHub Actions workflow in this PR; CI for deploy/docker/** can be proposed separately if desired.)

---

Хостовый и Docker-деплой для Ouroboros Desktop

Кратко

Два варианта деплоя для headless сценариев: deploy/docker/ (VPS в контейнерах) и deploy/host/ (установка прямо на машине), с единообразными скриптами эксплуатации и документацией.

Зачем

Упростить воспроизводимую эксплуатацию: установка, обновление, откат, бэкап и диагностика через согласованный набор скриптов, а не разрозненные шаги.

Что внутри

См. английскую секцию выше: структура зеркальная для docker и host профилей (install/update/backup/restore/doctor, systemd, common.sh, README и .env.example).

Комментарий

Только поверхность деплоя; правки .gitignore — чтобы не коммитить секреты и при этом оставить в репозитории примеры deploy/**/.env.example.

[keXXpert]

Добавил второй вариант деплоя (bare-metal), сквошнул все коммиты, убрал лишние правки в github actions, Dockerfile и Readme