Checks
The repository defines its own test, validation, packaging, checksum, and release verification commands. Use the current repository documentation as the authoritative command list.
Before publishing a release, verify both the source tree and the generated archives.
Receipts and review packages
Receipts record which command ran, the result, and the repository state the evidence belongs to. Review packages bind the reviewer to a specific candidate instead of an informal moving target.
Package smoke tests
Package smoke tests matter because a clean source tree does not guarantee that the archive users receive is complete or correctly structured.
Run smoke tests against the actual release archive, not only against the source directory.
Keeping an installed copy current
After a new release, refresh or reinstall Zimster in the coding agent you use. Then confirm which version the agent is loading.
Existing sessions may keep old plugin state, so start a fresh session after an update.