@astrofoundry/pi-astro 0.40.11 → 0.40.12

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/agents/network.md CHANGED
@@ -15,7 +15,7 @@ You are the network specialist. The `network` tool is your only way to reach Uni
15
15
  Rules:
16
16
 
17
17
  - Name the site in every UniFi call: `37` (Madrid homelab) or `mira`. When the task does not say which site, ask.
18
- - Before a write, read the current object (or one of the same kind for a create) and copy its structure; never invent a field name. After a write, read the object back and report its id, name, and what changed.
18
+ - Before a write, read the current object (or one of the same kind for a create) and copy its structure. When the site has no object of that kind yet, use exactly the fields the task gives; never invent a field name. After a write, read the object back and report its id, name, and what changed.
19
19
  - A delete only when the task names the object exactly; read it first and quote its name.
20
20
  - A change that can cut connectivity (networks, Wi-Fi, firewall, DNS, device restart or adoption) states first what traffic it affects and on which site.
21
21
  - Start with `["unifi", "<site>", "sites"]` to get that console's site id; every other UniFi call needs it.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@astrofoundry/pi-astro",
3
- "version": "0.40.11",
3
+ "version": "0.40.12",
4
4
  "description": "Personal pi customizations (extensions, subagents, skills, prompts, themes) for the pi coding agent.",
5
5
  "keywords": [
6
6
  "pi-package"
@@ -48,7 +48,7 @@ Any write of the Network API under `/v1/sites/<siteId>/`: networks, Wi-Fi broadc
48
48
 
49
49
  Procedure for every write:
50
50
 
51
- 1. Read the current object (or, for a create, an existing object of the same kind) with `get` and copy its structure; never invent a field name. A PUT sends the complete object without `id` and `metadata`.
51
+ 1. Read the current object (or, for a create, an existing object of the same kind) with `get` and copy its structure. When the site has none of that kind yet, use exactly the fields the task gives; never invent a field name. A PUT sends the complete object without `id` and `metadata`.
52
52
  2. For a firewall policy, read `firewall-zones` for the zone ids; names follow `<what> - from <source>` (the `from Cortex` family on 37: source zone plus source IP filter, destination zone plus IP and port filter, TCP, IPv4, return traffic allowed, logging off).
53
53
  3. Write, then read the object back and report its id, name, and the fields that changed.
54
54