warpmetal 0.3.0 → 0.3.1

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.
Files changed (4) hide show
  1. package/README.md +4 -3
  2. package/package.json +1 -1
  3. package/skills/warpmetal/SKILL.md +6 -5
  4. package/skills/warpmetal/references/safety.md +5 -3
package/README.md CHANGED
@@ -82,9 +82,10 @@ Wallet key management and signing remain outside this package.
82
82
  delete their workspace after 15 minutes to 24 hours.
83
83
  - Guarded reload powers the server off first. Runtime-enabled reload requires a
84
84
  second acknowledgment, after which the CLI guides supervisor reinstall and
85
- pinned connection-profile refresh. Replacement owner SSH host keys must be
86
- verified before updating `known_hosts`; erased workspaces are never described
87
- as recoverable.
85
+ pinned connection-profile refresh. Post-reload owner SSH host keys must be
86
+ independently verified because the provider may rotate or preserve them;
87
+ update `known_hosts` only when the verified key changed. Erased workspaces
88
+ are never described as recoverable.
88
89
 
89
90
  ## Agent Runtime example
90
91
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "warpmetal",
3
- "version": "0.3.0",
3
+ "version": "0.3.1",
4
4
  "description": "Agent-safe CLI and skill for purchasing and managing WarpMetal VPS servers",
5
5
  "type": "module",
6
6
  "bin": {
package/skills/warpmetal/SKILL.md CHANGED
@@ -137,11 +137,12 @@ warpmetal server reload \
137
137
 
138
138
  The CLI requires the recovery owner credential so it can keep polling after
139
139
  reload revokes SSH-derived access tokens. On success, reinstall Agent Runtime
140
- only after verifying the replacement owner-facing SSH host-key fingerprint
141
- through a trusted provider or console channel and safely updating
142
- `known_hosts`. Never bypass a mismatch. Then wait for grants to become applied and refresh every
143
- connection profile with `sandbox access refresh --confirm REFRESH` before
144
- connecting. Do not fall back to raw API calls for deletion, networking,
140
+ only after verifying the post-reload owner-facing SSH host-key fingerprint
141
+ through a trusted provider or console channel. The provider may rotate or
142
+ preserve the key; update `known_hosts` only when the verified key changed and
143
+ never bypass a mismatch. Then wait for grants to become applied and refresh
144
+ every connection profile with `sandbox access refresh --confirm REFRESH`
145
+ before connecting. Do not fall back to raw API calls for deletion, networking,
145
146
  renewal, or another unsupported mutation.
146
147
 
147
148
  ## Use Agent Runtime
package/skills/warpmetal/references/safety.md CHANGED
@@ -58,9 +58,11 @@ one lifecycle operation. When Agent Runtime is enabled, also require
58
58
  `acknowledgeAgentRuntimeReset`: all sandbox workspaces are permanently erased,
59
59
  the supervisor identity is revoked, desired sandboxes are recreated empty
60
60
  after reinstall, and all pinned profiles require refresh. Use only the guarded
61
- CLI command and stop on `manual_review`. Reload also replaces the owner-facing
62
- SSH host key; verify its fingerprint through a trusted provider or console
63
- channel before changing `known_hosts`, and never disable host-key checking.
61
+ CLI command and stop on `manual_review`. Reload invalidates the prior
62
+ owner-facing SSH host-key trust decision; the provider may rotate or preserve
63
+ the key. Verify the post-reload fingerprint through a trusted provider or
64
+ console channel, change `known_hosts` only when the verified key changed, and
65
+ never disable host-key checking.
64
66
 
65
67
  An order preparation is unpaid but consumes a limited prepared-order slot.
66
68
  Confirm the plan, hostname, OS, and public key before preparing it.