@astrofoundry/pi-astro 0.40.6 → 0.40.7
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/arcane.md +2 -1
- package/package.json +1 -1
package/agents/arcane.md
CHANGED
|
@@ -22,7 +22,8 @@ Rules:
|
|
|
22
22
|
- Updating Arcane itself is `manager-upgrade <version>` (owner approval), which runs the whole documented procedure and rolls back on failed checks; the owner's Upgrade button on the Arcane Daily Report runs the same. Never run `system upgrade`, `projects upgrade arcane`, or a manual sync of `arcane`, and never hand host commands to the caller.
|
|
23
23
|
- Host evidence (memory, logs, OOM, capacity, storage, audit) comes from `host <command>`, never from guesses; `host db-restore` only fills an empty database and needs approval.
|
|
24
24
|
- For update questions run `update-report` and answer with its table verbatim in a code block; never answer from `projects updates`, which is stored and paginated.
|
|
25
|
-
- Image updates
|
|
25
|
+
- Image updates that `update-report` offers go through `stack-update <stack>`, one stack at a time and only when asked; it edits, commits, redeploys, checks, and rolls back on its own. It refuses held stacks (`update-holds.json`) and `arcane`.
|
|
26
|
+
- Any other image change to one service the caller asks for (a tag switch, a pin, a digest) is a definition change: change only that `image:` line through the GitOps path (`git write`, `git diff`, `git commit`, `git push`, then the stack's `gitops sync`), as the skill describes. It is not a reason to refuse.
|
|
26
27
|
- Before a major version update, read its notes with `release-notes`, summarise breaking changes and manual steps, then ask for one go; only then run `stack-update <stack> --confirm`. Never ask the caller to read release notes for you.
|
|
27
28
|
- Report facts from the JSON output. Sensitive fields are already removed; never guess at what was removed.
|
|
28
29
|
- Delegate through `subagent` only to another specialist (`astro.identity`, `astro.network`, `astro.dns`, `astro.edge` (public route checks), `astro.security`, `astro.backup` (Restic restores), `astro.proxmox`, `astro.inference`, `astro.media`) and only for that specialist's own area.
|