@astrofoundry/pi-astro 0.40.28 → 0.40.29

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@astrofoundry/pi-astro",
3
- "version": "0.40.28",
3
+ "version": "0.40.29",
4
4
  "description": "Personal pi customizations (extensions, subagents, skills, prompts, themes) for the pi coding agent.",
5
5
  "keywords": [
6
6
  "pi-package"
@@ -43,6 +43,10 @@ Restore tests on record: `kuma` 2026-08-15 (`PRAGMA integrity_check` ok), `supab
43
43
 
44
44
  A service's backup is confirmed when `arcane-backup-status` shows `Result=success` for last night's run, `restic-snapshots <tag>` lists a snapshot from that run, and `restic-ls <snapshot>` shows the files the method above names. The method already makes the copy consistent: do not ask for a WAL check, and a restore test is extra, not a condition. Layer 1 also holds the whole Arcane VM (vmid 100) from 02:30.
45
45
 
46
+ ## Mira guests
47
+
48
+ SPACE-X (Mira) writes its own vzdump archives to TESLA (`tesla-backup`, `BACKUP/space-x/dump`), and Pulsar's `mira-backup-pull.timer` copies them to the UNAS (`BACKUP/space-x/dump`) at 05:00 without mirroring Mira's deletions. This tool does not read SPACE-X; the proxmox specialist's `space-x tasks` shows the runs, and Kuma monitors `space-x-backup` and `mira-backup-pull` carry the heartbeats.
49
+
46
50
  ## Reading the output
47
51
 
48
52
  - `*-status`: `Result=success`, `ExecMainStatus=0`, and the `ExecMainExitTimestamp` of the last run; the timer line shows the next run.
@@ -7,7 +7,7 @@ description: How the proxmox specialist operates Proxmox VE on Pulsar (37) and S
7
7
 
8
8
  Pulsar (`10.0.10.37`, Proxmox VE 9 on Debian 13, node name `pulsar`) runs every guest: VM 100 `arcane` (Docker platform), LXC 101 `hermes` (being retired by the operator; no specialist operates it), LXC 102 `backup` (GCS pusher), VM 103 `identity` (Zitadel), VM 104 `dmz` (Pomerium), LXC 105 `tailscale`, VM 106 `observability`, LXC 107 `technitium2`, LXC 108 `radius`. Storage `local-lvm` holds the disks, `unas-backup` the vzdump archives. The `proxmox` tool talks to the API with a token whose role allows audit everywhere and, on guests, power, snapshots, and CPU/memory/option/network settings; nothing else. `["--help"]` lists the commands.
9
9
 
10
- SPACE-X (`10.1.10.37`, Proxmox VE 9 at Mira, node name `space-x`) runs LXC 100 `technitium3` (DNS cluster node) and LXC 105 `tailscale` (Mira's subnet router). Put `space-x` before any command to run it there, for example `["space-x", "guests"]`; without it every command runs on Pulsar. SPACE-X has the same restricted user `spc-proxmox@pve!cortex` with its own token, and the same forced-command key as Pulsar. SPACE-X has no backup storage yet.
10
+ SPACE-X (`10.1.10.37`, Proxmox VE 9 at Mira, node name `space-x`) runs LXC 100 `technitium3` (DNS cluster node) and LXC 105 `tailscale` (Mira's subnet router). Put `space-x` before any command to run it there, for example `["space-x", "guests"]`; without it every command runs on Pulsar. SPACE-X has the same restricted user `spc-proxmox@pve!cortex` with its own token, and the same forced-command key as Pulsar. SPACE-X backs up every guest nightly at 02:30 (Dubai time) to storage `tesla-backup` on Mira's Synology TESLA; Pulsar's `mira-backup-pull` copies the archives to 37 at 05:00. `["space-x", "tasks"]` shows the vzdump runs.
11
11
 
12
12
  ## API commands
13
13