lawzava Upgrading Megapowers
Use the current marketplace channel reference. Before any write, inventory visible registrations: enabled state and version, exposed scope, marketplace name and source, pin or ref, local edits, duplicates, caches, and active sessions. Read the stable release and changelog without writes. Stop on ambiguous provenance, managed-source edits, or conflicting installations.
Preserve enabled state, source or channel, scope, pin, and local edits. A floating Git marketplace follows its latest stable release; a pinned or local checkout changes only when explicitly approved. Keep one installation channel per harness and exclude unrelated cleanup. If already current, report a verified no-op.
Resolve the stable release tag to its exact commit and the observed marketplace
source's tracked head: its release branch when the registration carries that
ref, otherwise its default branch. A floating refresh may proceed only when the
release commit and marketplace head match. Otherwise stop before any write;
never install unreleased branch state as a stable upgrade. A registration that
tracks the default branch is a channel defect: report it and propose
re-registering at release as a separately approved write.
After refreshing but before registration, resolve the snapshot commit and require it to match the approved commit. Otherwise stop with the installed plugin untouched.
Request one exact approval covering target harnesses, enabled state, source, scope, pins, current and target versions, writes, restart or cache effects, and verification. Apply only that approved channel. If a write fails, stop, read back state, and report applied, failed, and not attempted steps.
For a floating marketplace, use the channel reference so the refreshed snapshot becomes the registered cache. Substitute the observed marketplace name and scope; never rename either.
For an approved pinned checkout, update only its exact path and ref, then use the existing marketplace registration; never switch its source silently.
Verify registration output and marketplace-source inventory: enabled state and version, source, exposed scope, returned install path, and cached byte parity against the target ref. Report partial application precisely. Restart before expecting new guidance. Never delete a stale or superseded cache while an active session may use it; removal needs separate approval, exact directories, and proof that sessions restarted. Registration itself may prune a superseded cache: when any session may still use it, snapshot that cache before registering and restore it if pruning occurs. Do not invoke a model or provider session without explicit authorization; otherwise stop at registration and cache proof.