docs: plan fork v8.24.0 release

Author: caidaoli

superpowers/docs/plans/2026-07-15-215745-01-plan-release-fork-v8.24.0.md

@@ -0,0 +1,17 @@
+# Release fork/v8.24.0
+
+**Goal:** Publish the current `main` branch as `fork/v8.24.0` and trigger the fork release workflow.
+**Why planning is required:** Pushing the branch and annotated release tag changes remote repository state and triggers GitHub Actions.
+**Acceptance:** Release only from a clean local `main`; preserve the pre-release code anchor `22c4ddf5ad2dadfc2a6be702c2ad72de05bdac39`; confirm `fork/v8.24.0` is absent locally and remotely; push only `main` and `fork/v8.24.0` to `origin`; stop if version calculation, verification, authentication, or push fails; if tag push fails, delete the local tag; if the published release must be withdrawn, delete `refs/tags/fork/v8.24.0` from `origin` and then delete the local tag.
+
+### Outcome 1: Establish the release version and contents
+- Work: Use `github-fork-relase` rules to classify all non-merge commits after `fork/v8.23.1` and commit this release record.
+- Verify: `git rev-list --count --no-merges fork/v8.23.1..HEAD` and `git log fork/v8.23.1..HEAD --no-merges`
+
+### Outcome 2: Create and publish the release tag
+- Work: Create annotated tag `fork/v8.24.0`, then push local `main` and the tag to `origin` without force.
+- Verify: `git ls-remote --heads --tags origin main refs/tags/fork/v8.24.0 refs/tags/fork/v8.24.0^{}`
+
+### Outcome 3: Verify the release trigger
+- Work: Confirm the remote branch and peeled annotated tag resolve to the intended commits, then inspect the GitHub Actions workflow triggered by the push.
+- Verify: `gh run list --limit 10` and remote ref comparison against local `main` and `fork/v8.24.0^{}`