pynchy-opslisted

# Pynchy Ops The live Pynchy host and checkout path are deployment-specific. Public repo instructions must not assume a private hostname or home-directory layout. Set `PYNCHY_HOST` and `PYNCHY_REMOTE_ROOT` from local memory, environment, or the operator before running remote commands. ## Deployment Mode Gate First check whether the authenticated local control-plane socket is available (see Quick Status Check below). Reading local status does not require an SSH profile. Identify the deployment before remote operations or changes. A `pynchy` Kubernetes namespace means the Kubernetes path applies: ```bash PYNCHY_HOST="${PYNCHY_HOST:?set the live host}" ssh "$PYNCHY_HOST" 'sudo k3s kubectl get namespace pynchy' ``` For Kubernetes deployments: - Read [Kubernetes installation and operations](../../../docs/installation/kubernetes.md). - Treat `SCHEDULER__AUTO_DEPLOY=false` as authoritative. A Git pull updates the persistent checkout but does not replace the running image. - Use `sudo k3s kubectl -n pynchy`; do not use `pynchy deploy`, LaunchAgent commands, standalone systemd commands, or direct container deletion. - A successful push to `main` publishes immutable images. The namespace-scoped `pynchy-release-monitor` CronJob preflights and releases them. - Do not manually patch the Deployment or delete a Pod for a normal release. Observe the monitor Job, rollout, exact release annotation, and application status. - The monitor applies the selected release’s `deploy/k3s/app