Release/v0.2.5

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -18,7 +18,7 @@ body:
     attributes:
       label: CLI version
       description: Output of `agora --version`
-      placeholder: "e.g. agora-cli 0.2.2 (commit abc1234, built 2026-05-26)"
+      placeholder: "e.g. agora-cli 0.2.5 (commit abc1234, built 2026-06-05)"
     validations:
       required: true
 

AGENTS.md

@@ -104,7 +104,7 @@ agora
 
 **Design rules — do not break these:**
 - `project` = remote Agora control-plane resource; it never scaffolds local files
-- `quickstart` = local repo clone; requires `git` on the PATH
+- `quickstart` = local repo clone; requires `git` on the PATH; upstream `.git` is removed after clone so demos start without template history
 - `init` = the only command that composes both
 - The `add` namespace is reserved; keep it hidden and return a command-not-found error if invoked
 

CHANGELOG.md

@@ -15,18 +15,26 @@ Earlier entries pre-date this convention and only carry their version's compare
 
 ## [Unreleased]
 
-## [0.2.5] - 2026-06-01
+## [0.2.5] - 2026-06-05
 
-Installer migration improvements.
+Installer migration, quickstart scaffold cleanup, and onboarding doc refresh.
 
 ### Added
 
 - Add `install.sh --replace-npm` to migrate from a global npm-managed `agoraio-cli` install to the standalone installer by running `npm uninstall -g agoraio-cli` before installing the binary.
+- Emit a `clone:strip-git` progress event after removing upstream template git metadata during quickstart scaffolds.
 
 ### Changed
 
+- Remove upstream `.git` metadata after quickstart scaffolds are cloned so demos start without the template repository's history.
 - Improve managed-install errors with explicit uninstall-and-reinstall guidance so users can switch to the standalone installer without relying on side-by-side PATH shadowing.
 - Update website install and troubleshooting docs with npm-to-standalone migration steps and clearer PATH shadowing guidance.
+- Restructure README quick start, command routing tables, env workflows, and documentation index.
+- Document CI and release workflow expectations in CONTRIBUTING.md.
+
+### Fixed
+
+- Bump the pinned Go toolchain to 1.26.4 so release builds include stdlib fixes for GO-2026-5037 and GO-2026-5039.
 
 ## [0.2.4] - 2026-06-01
 

CONTRIBUTING.md

@@ -128,6 +128,22 @@ change; prefer adding a new code and deprecating the old one over a rename.
   that is part of the public contract (JSON shape, exit code, stderr text).
   Use `app_test.go` for isolated helper logic.
 
+## CI and releases
+
+GitHub Actions are configured for:
+
+- push and pull request validation on Linux, macOS, and Windows
+- automated tag-driven releases for `v*` tags
+- cross-platform release artifacts for Linux, macOS, and Windows
+
+Release workflow behavior:
+
+- a pushed tag matching `v*` (for example `v0.2.5`) triggers the release workflow
+- the workflow runs tests, builds release binaries, packages them, and publishes a GitHub release automatically
+- release artifacts include checksums, Cosign signatures, and an SBOM
+
+See [AGENTS.md](AGENTS.md) for the full release pipeline (npm, Homebrew, apt, GitHub Pages).
+
 ## Branching model
 
 - `main` is always releasable. CI must be green before merge.