@astrofoundry/pi-astro 0.40.36 → 0.40.37
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
package/skills/proxmox/SKILL.md
CHANGED
|
@@ -5,7 +5,7 @@ description: How the proxmox specialist operates Proxmox VE on Pulsar (37) and S
|
|
|
5
5
|
|
|
6
6
|
# Proxmox specialist
|
|
7
7
|
|
|
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` (
|
|
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` (stopped and retired on 2026-11-01; the operator deletes it after 2026-12-01; never start 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
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
|
|
package/skills/security/SKILL.md
CHANGED
|
@@ -5,7 +5,7 @@ description: How the security specialist reads Wazuh, CrowdSec, and the remote l
|
|
|
5
5
|
|
|
6
6
|
# Security specialist
|
|
7
7
|
|
|
8
|
-
VM 106 (`10.0.90.10`, VLAN 90) runs the Wazuh manager (container `observability-wazuh-manager-1`, agents `identity`, `arcane`, `dmz`, `CORTEX`, `NEXUS`, `
|
|
8
|
+
VM 106 (`10.0.90.10`, VLAN 90) runs the Wazuh manager (container `observability-wazuh-manager-1`, agents `identity`, `arcane`, `dmz`, `CORTEX`, `NEXUS`, `frontdoor-1337`, `tailscale`, and since 2026-11-01 `pulsar`, `synapse`, `technitium2`, `radius`, `backup`, `space-x`, `technitium3`, `tailscale-mira`), CrowdSec with its local API for the front-door bouncer, and rsyslog, which archives remote logs under `/var/log/remote/<host>/<program>.log` (14 days). The Discord bridge on Cortex reads Wazuh through this tool every two minutes and posts urgent alerts at once (level 11 or higher, and rules 100011, 100012, 100020, 100021; a deployment-file change that a GitOps commit or our own operation explains is not urgent), with Investigate and Acknowledge buttons for the owners; everything else goes into the Security Daily Report (06:00) and, on Mondays, the Security Weekly Report. The VM itself no longer posts to Discord. Two local CrowdSec scenarios matter: `37pla/pomerium-http-probing` (repeated Pomerium denials) and `37pla/frontdoor-sni-scanning` (rejected SNI at the VPS; bans escalate 4h, 24h, 7d, 30d, 90d). The home WAN address is whitelisted every five minutes; a scan test in August 2026 once banned it.
|
|
9
9
|
|
|
10
10
|
The `security` tool is read-only. Every call is a fixed command on the guest; `["--help"]` lists them.
|
|
11
11
|
|
|
@@ -54,7 +54,9 @@ The `security` tool is read-only. Every call is a fixed command on the guest; `[
|
|
|
54
54
|
| `arcane` | VM 100, Docker host | `astro.arcane` for containers |
|
|
55
55
|
| `identity` | VM 103, ZITADEL | `astro.identity` |
|
|
56
56
|
| `dmz` | VM 104, Pomerium and nginx | `astro.identity` |
|
|
57
|
-
| `
|
|
57
|
+
| `pulsar`, `space-x` | Proxmox hosts at 37 and Mira | `astro.proxmox` |
|
|
58
|
+
| `synapse`, `technitium2`, `technitium3` | the three DNS nodes | `astro.dns` (`technitium host <node>`) |
|
|
59
|
+
| `radius`, `backup`, `tailscale-mira` | LXC 108, LXC 102, SPACE-X LXC 105 | `astro.network` (RADIUS), `astro.backup`, none for the Mira router |
|
|
58
60
|
| `NEXUS` | Mac Studio | `astro.inference` |
|
|
59
61
|
| `CORTEX`, `tailscale` | Mac mini, LXC 105 | none; the operator |
|
|
60
62
|
|
|
@@ -113,7 +113,7 @@ ${Object.entries(HOST_COMMANDS)
|
|
|
113
113
|
.map(([name, c]) => ` ${name.padEnd(35)} ${c.help}`)
|
|
114
114
|
.join("\n")}
|
|
115
115
|
|
|
116
|
-
Not available: create, clone, destroy, disk changes, host
|
|
116
|
+
Not available: create, clone, destroy, disk changes, host configuration. Those are operator tasks.`;
|
|
117
117
|
|
|
118
118
|
interface PveEnvelope {
|
|
119
119
|
data?: unknown;
|