@perkos/perkos-a2a 0.12.38 → 0.12.40

package/README.md

@@ -198,9 +198,11 @@ files are created with owner-only permissions.
 It validates config and plugin health, then reads only plugin-owned runtime
 evidence. It never mutates `commands.restart`, sends `SIGUSR1`, waits for an
 OpenClaw gateway drain, launches a second relay/chat client, or scrapes gateway
-status/logs. Clean installs complete through hot reload. Certified upgrades use
-a fenced supervisor rollover while the gateway and its active model/runtime
-remain untouched. Relay, registration, heartbeat, and chat authentication must
+status/logs. Clean installs complete through hot reload. OpenClaw 2026.5 caches
+an already-loaded plugin module, so version upgrades stage the verified package
+and normalized config, then return `ACTION_REQUIRED_REAL_RESTART` immediately;
+the same command resumes after the operator restarts the gateway process or
+container. Relay, registration, heartbeat, and chat authentication must
 remain healthy—with no duplicate plugin or registration messages—for three
 continuous minutes and at least three fresh successful heartbeats. Success or
 failure is emitted as one JSON object; secret values are never printed.
@@ -221,14 +223,15 @@ start identity, boot id, claim time, and transport counts in private health
 evidence so `connect` can distinguish a certified owner from stale files.
 
 For a clean first install, OpenClaw's PID 1 hot reload remains supported without
-a gateway restart. A certified upgrade fences and stops the old supervisor,
-waits for `STOPPED` plus socket/process exit, starts the supervisor CLI from the
-new verified install root, and requires target-version health before opening a
-single relay client. When upgrading a pre-supervisor or otherwise uncertified
-installation, `connect` exits promptly with the machine-readable action
-`ACTION_REQUIRED_REAL_RESTART`; rerunning the same idempotent command after an
-out-of-band service/container restart resumes the migration without replacing
-identity or credentials.
+a gateway restart. A version upgrade keeps a certified entry enabled while it
+stages the new package, records why a real restart is required, and exits
+promptly with the machine-readable action `ACTION_REQUIRED_REAL_RESTART` instead
+of waiting for evidence that a cached VM cannot produce. The same action is used
+for a pre-supervisor or otherwise uncertified installation. Rerunning the exact
+idempotent command after an out-of-band service/container restart resumes the
+migration, verifies the changed PID/start identity and target supervisor, and
+never replaces identity or credentials. Same-version OpenClaw VM reloads remain
+serialized by the single-owner supervisor fence.
 
 On successful verification, `connect` removes the active-attempt file and marks
 the private repair journal `done`. Stale OpenClaw install metadata is reported