chore(agentic-toolkit): add bump-version release skill

.agentic-toolkit.yaml

@@ -1,2 +1,4 @@
 extends:
-  - github.com/wardnet/agentic-stacks/wardnet.yaml@main
+  - github.com/wardnet/agentic-stacks/wardnet.yaml@main
+skills:
+  - ./.agents/skills/bump-version

.agents/skills/bump-version/SKILL.md

@@ -0,0 +1,117 @@
+---
+name: bump-version
+description: |
+  Use this skill when the user asks to cut/release/bump a new inforge
+  version (e.g. "cut a new version", "release with the recent fixes",
+  "tag a release"). Covers picking the semver bump, tagging the release
+  (which fires .github/workflows/release.yml → goreleaser), moving the
+  floating major-alias tag (vN), and verifying the published release.
+---
+
+# Cut an inforge release
+
+Releases are **tag-driven**: pushing an annotated `vX.Y.Z` tag to a commit
+on `main` triggers `.github/workflows/release.yml` (build & test →
+goreleaser), which publishes the GitHub release with the four
+statically-linked binaries, the two `pulumi-resource-*` plugins,
+`checksums.txt`, and `install.sh`.
+
+Two tags move per release and **both are mandatory**:
+
+1. the immutable `vX.Y.Z` release tag (the workflow trigger), and
+2. the floating `vN` major-alias tag (e.g. `v2`), force-moved to the same
+   commit. Consumers pin `uses: wardnet/inforge@v2`, so the alias **must**
+   track the latest release of that major. This is convention, not
+   optional — a release where `v2` still points at the previous commit is
+   an incomplete release.
+
+## 0. Preconditions
+
+- The fixes to release are **already merged to `main`** and `main`'s CI is
+  green. This skill does not merge PRs (see the repo CLAUDE.md rule). If the
+  fix is still on a PR, stop and get it merged first.
+- You are in the `gt` bare-repo layout; `gh`/`git` authenticate as the user
+  in the root `.envrc` (`gh auth token --user <username>`). Read that user
+  before any `gh`/push command.
+- `git fetch origin --tags` so local tags and `origin/main` are current.
+
+## 1. Pick the version
+
+Find the current latest and what has landed since it:
+
+```bash
+gh release list --repo wardnet/inforge --limit 5
+git log --oneline "$(gh release view --repo wardnet/inforge --json tagName -q .tagName)"..origin/main
+```
+
+Choose the bump by the **highest-impact change to the shipped binaries**
+since the last release (SemVer):
+
+- **patch** (`vX.Y.Z+1`) — bug fixes only; no new user-facing behaviour.
+- **minor** (`vX.Y+1.0`) — backward-compatible features / new flags / new
+  resource types.
+- **major** (`vX+1.0.0`) — breaking changes (descriptor `SupportedVersion`
+  bump, renamed/removed CLI surface, stack-config changes). A new major also
+  means a **new floating alias** (`vN+1`) and updating consumers that pin the
+  old one — call this out explicitly.
+
+Config-only changes (e.g. a `dependabot.yml` edit) do **not** by themselves
+warrant a release; only cut one when the binaries changed.
+
+Let `$VER` be the new version (e.g. `v2.3.1`) and `$MAJOR` its alias (`v2`).
+Let `$SHA` be the `origin/main` commit to release.
+
+## 2. Tag the release and push
+
+Annotated tag (matches existing release tags), at the exact `main` commit:
+
+```bash
+git tag -a "$VER" "$SHA" -m "$VER
+
+<one bullet per change being shipped, e.g. fix(...) (#NNN)>"
+git push origin "$VER"
+```
+
+The push fires `release.yml`. Nothing else triggers it — only tags matching
+`v*.*.*`.
+
+## 3. Move the floating major alias
+
+The `vN` tag is **lightweight and hand-maintained** (not a workflow
+trigger). Re-point it and force-push:
+
+```bash
+git tag -f "$MAJOR" "$SHA"
+git push origin "$MAJOR" --force
+```
+
+The force-push of a shared tag may need explicit approval — that is
+expected; this step is required, so request it if blocked. Do not skip it.
+
+## 4. Verify
+
+```bash
+gh run watch "$(gh run list --repo wardnet/inforge --workflow release.yml \
+  --limit 1 --json databaseId -q '.[0].databaseId')" \
+  --repo wardnet/inforge --exit-status
+gh release view "$VER" --repo wardnet/inforge \
+  --json tagName,isDraft,isPrerelease,assets \
+  -q '{tag:.tagName, draft:.isDraft, prerelease:.isPrerelease, assets:[.assets[].name]}'
+git ls-remote origin "refs/tags/$MAJOR"   # must equal $SHA
+```
+
+Confirm: workflow **success**; the release is **not draft / not prerelease**
+and shows as **Latest** in `gh release list` (goreleaser sets no
+`prerelease`/`make_latest: false`, so the highest semver is auto-Latest);
+assets include all four binaries × `linux_{amd64,arm64}` + `darwin_arm64`,
+both `pulumi-resource-*` plugins, `checksums.txt`, and `install.sh`; and the
+`$MAJOR` remote tag now points at `$SHA`.
+
+## How consumers pick it up
+
+`action.yml` defaults `version: latest` and installs from
+`releases/latest/download/install.sh`, so any repo using
+`uses: wardnet/inforge@<major>` with no `version:` pin gets the new release
+on its next CI run as soon as it is marked Latest. The `vN` alias keeps the
+**action.yml code** consumers resolve current — which is why step 3 is not
+optional even though delivery flows through `releases/latest`.