Render gateway upgrade notices at SessionStart; /acp-upgrade skill (0.13.0) - #21
Merged
Conversation
….13.0) The attest response may now carry a notice when this plugin version is behind the gateway registry's latest. Surface it as SessionStart additionalContext so the MODEL sees it and can drive the upgrade — behind a human approval; the canonical installer is step_up-gated at the gateway (gatewaystack-connect#849). Canonical contract lives in lib/attestation.mjs (attestNoticeOutput) with tests. New /acp-upgrade skill walks the agent through the approval-gated installer run, the retry-after-approval, and the restart+re-attest verification. Companion to gatewaystack-connect#849; closes #20.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Companion to davidcrowe/gatewaystack-connect#849 (stale-client upgrade nudge). Closes #20.
bin/govern.mjsSessionStart now reads the/govern/attestresponse: anotice(sent when this version is behind the registry's latest) is emitted ashookSpecificOutput.additionalContext, so the model itself learns an upgrade exists and can run it — the canonical installer is approval-gated at the gateway, so the human click stays the authority.lib/attestation.mjs(attestNoticeOutput) + tests (node --test: all pass)./acp-upgradeskill: exact installer command, expect-the-approval flow, retry after approval, restart + re-attest verification. Explicitly forbids editing governance files directly or working around a deny.Old plugins ignore the extra response field entirely — no behavior change until they upgrade (their reach is the console stale badge and enriched founder alerts on the gateway side).