Files
msd-core/docs/features/installer-migrations.md
Jakub Zych a9a7a328e6 refactor: hard-fork GSD -> MSD (Make Software Done)
Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD
across contents and paths, upstream package/repo coordinates -> @golem15/msd-core
and golem15com/msd-core. Deep links into upstream history, sibling upstream
packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is.

Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line,
package/plugin identity, regenerated lockfile, install-tree fixtures, derived
registries and benchmark baseline; migration checksum baseline re-locked
(MSD keeps its own install state, so no install had applied the old sums);
sort-order and regex-escaped expectations in tests adjusted.
2026-10-06 01:47:40 +02:00

929 B

id, title, group
id title group
134 Installer Migrations v1.42.1 Features

Purpose: Make runtime config cleanup explicit, auditable, and rollback-aware during installs and updates.

Capabilities:

  • First-time baseline migration records managed files.
  • Legacy stale-file cleanup uses ownership evidence before deleting or rewriting.
  • User-owned artifacts are preserved.
  • Ambiguous MSD-looking files block with a clear report instead of being silently overwritten.
  • Migration plans support dry-run reporting and rollback protection.

Requirements:

  • REQ-INSTALL-MIGRATION-01: Migration records MUST include metadata, install scope, and ownership evidence.
  • REQ-INSTALL-MIGRATION-02: Destructive actions MUST fail closed when ownership is ambiguous.
  • REQ-INSTALL-MIGRATION-03: Install failures MUST restore the pre-install state when rollback data exists.

Reference: Installer Migrations