Installers now install the release they ship with, not the current main. There is also an uninstaller.
Changes
- Release-pinned installers: every installer (sh and ps1, four agents) defaults to
v5.7.0. SetL_GEVITY_SKILLS_REF=mainfor unreleased work. The validator fails when the pin andpackage.jsondiffer. - Uninstaller:
.install/uninstall.shand.install/uninstall.ps1, one for every agent, with no network needed. They remove only unedited files: first the agent-team files (viainit_workspace.py --uninstall), then the instruction file the lock names, then the locked skills and the lock. Edited files stay and are listed. Without Python 3, or without the remover, while agent-team files exist, they stop before removing anything.curl -fsSL https://raw.githubusercontent.com/l-gevity/l-gevity-skills/main/.install/uninstall.sh | bash - Lock: records the instruction file it wrote, with a
sha256:text digest. init_workspace.py --uninstall [--dry-run].- README: install and uninstall section rewritten, with an example of reading an installer before you run it.
- Test fix: every exit-status check in the PowerShell installer suite read 0 on Windows CI (a script-scoped
$LASTEXITCODE). It now reads the real status.
Verification
npm run validate: passes.npm run validate:mutation: all 170 deliberate violations caught.bash scripts/test-installers.sh: 115 checks pass.scripts/test-installers.ps1: 224 checks pass under pwsh 7 and Windows PowerShell 5.1.- 7 scenarios re-recorded; every expectation met.
- CI green on #52 and #53.
Limits
- Pipe-to-shell stays. Checksums from the same origin would not protect against a compromised repository.
- An install made before v5.7.0 has no
--uninstalland no instruction-file record. Run the installer once first, then uninstall. - Between a version bump merging and its release tag existing, the installers on
mainpoint to a tag that is not there yet.