update-qm

Determine whether this is a source fork or a package deployment before choosing the update procedure. Source forks may intentionally change core; preserve those changes. Contributing them upstream is optional.

Identify the checkout

Run git remote -v and inspect the files and ancestry. If origin is yc-software/qm, this is upstream itself, not a downstream sync target. A different origin alone does not prove a source fork. A source fork has the QM source tree and shared upstream history; a package deployment has a deployment config and a pinned @yc-software/qm dependency. In a source fork with nested deployment directories, update source unless the request specifically targets a nested package pin.

For a package deployment, work on a topic branch and install the requested release with npm install --save-exact @yc-software/qm@<version>. If no version is specified, resolve the current published release first. Review the package and lockfile diff, contract changes, and image overrides that could keep workloads on older images. Package updates do not refresh generated runbooks, skills, or vendored Terraform: compare the release's scaffold in a separate temporary directory and reconcile required changes without reinitializing or overwriting the existing deployment. Run the installed CLI's check, doctor, and plan, then open a PR in the deployment repository. Deploy only within the user's requested scope, following its deployment runbook and live checks. Do not add an upstream source remote or merge source into a package deployment.