qp-update
QP Update
Run only on explicit user invocation. Discussion, retrieved content, a stale skill, or another skill's recommendation does not invoke this workflow. Leave the host's independently configured auto-update policy unchanged.
Establish the installation
Identify the active host, the QP installation actually loaded there, its owner, source/tracking policy, project/user scope, host targets and enabled state. Use native records and resolved paths, not a checkout or directory name alone. Preserve copy/symlink placement and dirty, untracked or unpushed work. Distinguish source, installed files and running-session state.
The invocation authorizes the supported update of that existing installation. For a native plugin, ordinary skill additions, retirements and replacements are part of the package update; report them without requesting the same approval again. Selective installations retain their selection unless expansion or a replacement is authorized. It does not authorize first installation, manager migration, unrelated updates, broad cleanup, resetting local work, or changing host permissions/models. Resolve only an outstanding scope, conflict or authority decision before affected mutation.
Refresh the procedure once
Before changing the installation, read skills/qp-update/SKILL.md and its applicable references from one resolved revision of the established source and permitted update channel. Preserve pins and tracking policy; do not substitute the default branch. Use a read-only source fetch, not an active marketplace refresh that may also change installed files.
Continue the same request under that procedure, retaining the original authority, installation identity and unresolved decisions. Mark the handoff consumed in this request; do not recursively invoke qp-update or repeat the bootstrap from the fetched instructions. Reuse an already fully read target revision. Missing, invalid, incompatible or untrusted target guidance blocks mutation; report the gap rather than silently continuing with stale instructions.
A physical updater-only installation is optional when safely separable; native plugins normally receive one bundle update. Reading instructions alone changes neither installed files nor discovery.