chore(release): prepare public source release

2026-07-18 15:33:01 +08:00
commit 34d6a57f38
510 changed files with 163501 additions and 0 deletions
@@ -0,0 +1,46 @@
+# Mercury Toolbox v0.1.0
+
+Mercury Toolbox v0.1.0 is the first hosted release for the Gitea-backed repository. It packages the current PowerShell-first Rust toolbox, ships the renamed `mhash` hashing command, carries the generated Codex skill and AI prompt assets, and aligns the portable install path with the current package bundle.
+
+## Highlights
+
+- `mhash:` the former `digest` command surface is now published under the permanent `mhash` name across binaries, docs, scripts, packaged assets, and installed skills.
+- `Guided triage:` the generated AI prompt, skill catalog, and PE tooling guidance are bundled into the portable package so the hosted release matches the current local install surface.
+- `Portable packaging:` the release archive includes install and uninstall scripts, `SHA256SUMS.txt`, `mercury-toolbox-package.json`, and the packaged command catalog for offline inspection.
+- `Gitea automation:` this release adds native `.gitea/workflows` CI and tag-driven release publishing for the hosted repo.
+
+## Breaking Changes
+
+- `digest -> mhash`
+- Any automation or muscle memory that still invokes `digest` should switch to `mhash`.
+
+## Install Or Upgrade
+
+Fresh install from source checkout:
+
+```powershell
+pwsh -NoProfile -File .\scripts\install-toolbox.ps1
+```
+
+Portable package install from the release assets:
+
+```powershell
+pwsh -NoProfile -File .\MercuryToolbox-x86_64-pc-windows-msvc-ReleaseFast\scripts\install-package-toolbox.ps1
+```
+
+## Verification
+
+- Release gate: `just jade`
+- Package build: `just package`
+- Release publish: `pwsh -NoProfile -File .\scripts\publish-gitea-release.ps1 -Tag v0.1.0 -NotesPath .\docs\releases\v0.1.0.md`
+
+## Assets
+
+- `MercuryToolbox-x86_64-pc-windows-msvc-ReleaseFast.zip`
+- `SHA256SUMS.txt`
+- `mercury-toolbox-package.json`
+
+## Notes For Upgraders
+
+- Open a new PowerShell after install so the updated PATH picks up the current toolbox binaries.
+- Codex skill installs are refreshed by the package installer; a new Codex session is the cleanest way to pick up the latest packaged skill copy.