#!/usr/bin/env sh
# G-12 multi-machine ROUTING validation via SSH-to-self: test-remote points at
# 127.0.0.1, so `--on test-remote` exercises nina's full SSH routing (build ssh
# argv, connect, run remotely, parse output) and `status --all` aggregation.
# CAVEAT: test-remote IS this machine, so this validates the --on plumbing, NOT
# physical isolation (separate generation counts need two real networked VMs).
set -u
N=/root/nina

echo "KILN_MM_BEGIN"

mkdir -p /root/.ssh && chmod 700 /root/.ssh
ssh-keygen -t ed25519 -N '' -f /root/.ssh/id_test </dev/null >/dev/null 2>&1
cat /root/.ssh/id_test.pub >> /root/.ssh/authorized_keys
chmod 600 /root/.ssh/authorized_keys

cat > /root/.nina.conf <<EOF
editor      = vim
generations = 5
confirm     = false
teach       = true
color       = true

[machine]
name    = test-primary
config  = /etc/nixos
local   = true
default = true

[machine]
name    = test-remote
host    = 127.0.0.1
user    = root
ssh_key = /root/.ssh/id_test
EOF

echo "### T-153 nina hello (test-primary local, test-remote ssh)"
$N hello </dev/null; echo "HELLO_RC=$?"

echo "### T-160 nina status --all (both machines in table)"
$N status --all </dev/null; echo "STATUSALL_RC=$?"

echo "### T-164 nina history --on test-remote (via ssh)"
$N history --on test-remote </dev/null; echo "HISTREMOTE_RC=$?"

echo "### T-166 nina service list --on test-remote (via ssh)"
$N service list --on test-remote </dev/null; echo "SVCREMOTE_RC=$?"

echo "### T-165 nina doctor --on test-remote (via ssh)"
$N doctor --on test-remote </dev/null; echo "DOCTORREMOTE_RC=$?"

echo "### T-162 nina apply --on test-remote (ssh -> nixos-rebuild switch on self)"
$N apply --on test-remote </dev/null; echo "APPLYREMOTE_RC=$?"

echo "### T-167 nina status --on ghost-machine (expect error)"
$N status --on ghost-machine </dev/null; echo "GHOST_RC=$?"

echo "KILN_MM_END"