msb-packaging
What ships and how it installs: install.sh --dev versus --package and its --uninstall, get.sh the curl|sh entry point with MSB_MANAGER_BASE_URL, scripts/package.sh with its explicit PAYLOAD list, repr
Files1
View on GitHubSKILL.md.agents/skills/msb-packaging/SKILL.md
GitHubPackaging
Detail carved out of AGENTS.md, which keeps only what has to hold in
every session. Repo-specific throughout; the facts here are verified against
msb 0.7.6 and re-checked on 0.7.7.
install.sh— two modes:--dev(a git checkout; symlinks the commands into it) and--package(copies the tree to~/.local/share/msb-manager/versions/<v>/,currentlink, commands link through it; keeps current + previous). Seeds~/.config/msb/from templates, never overwrites,--uninstallremoves only what it owns. Never reads stdin (it runs undercurl | sh) and has no backticks in its unquoted heredoc (they execute).get.sh— thecurl | shentry point (POSIX sh, modeled on microsandbox's installer): resolves the latest release via the GitHub API, downloads the tarball, verifies its sha256, runs the installer inside it.@@GITHUB_REPO@@is filled in byscripts/package.sh;MSB_MANAGER_BASE_URL(+--version) serves assets from a mirror orfile://for testing.scripts/package.sh— buildsdist/(reproducible tarball, repo-boundget.sh,checksums.sha256) from an explicit PAYLOAD list (keep in step withinstall.sh); fails on symlinks,.envfiles or an unreplaced placeholder; normalizes modes. Does not publish.VERSION— the release version;msbctl --version,msbctl self-update(re-runs the packagedget.sh; a checkout saysgit pull).