@astrofoundry/pi-astro 0.40.5 → 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/skills/arcane/SKILL.md +2 -0
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.
|
package/package.json
CHANGED
package/skills/arcane/SKILL.md
CHANGED
|
@@ -49,6 +49,8 @@ Apply updates only when asked, one stack at a time, with `["stack-update", "<sta
|
|
|
49
49
|
- Checks: every service has a container that runs (a one-shot job may have exited 0), found through its Compose project, none still runs an older image than its tag, none is unhealthy or still starting after 5 minutes, and a fresh check finds every updated image current.
|
|
50
50
|
- A failed check after a Compose change reverts the commit, pushes, waits for the sync, and redeploys the previous file. A pull alone cannot be undone; say so when it fails.
|
|
51
51
|
|
|
52
|
+
`stack-update` only moves a stack to what `update-report` offers. Any other image change to one service (a tag switch such as `pr-plugins` to `nightly`, a pin, a digest) goes through the definitions path above: write the Compose file back with only that `image:` line changed, check `git diff` shows that one line, commit, push, and start the stack's sync. On sync, Compose recreates only the services whose configuration or image changed and keeps their volumes (Docker's `docker compose up` reference), so the rest of the stack keeps running. Before the change, record the running image; afterwards, check the service's container, health, and running version. What the tools cannot check (an app's plugin page, a restore into a volume) goes to the owner as a named step, not as a reason to stop.
|
|
53
|
+
|
|
52
54
|
The answer is JSON with `status`: `updated`, `rolled back`, `failed` (with `reason`), or `nothing to do`, plus `services` (`service`, `from`, `to`, `applied`: `pull` or the new reference, `result`: `current`, `behind`, `unchecked`) and `commit`/`revert` when the Compose file changed. Report it in plain words.
|
|
53
55
|
|
|
54
56
|
It refuses `arcane` (next section), stopped stacks (a redeploy would start them), a checkout with local or unpushed changes, and held stacks. Held stacks are listed in `update-holds.json` at the root of the GitOps repository, `{ "<stack>": "<reason>" }`; `update-report` returns them in `holds`, and the daily report shows the reason without a button. Change that file only when the caller asks, through the `git` commands.
|