docs: phase 2 plan, row 273 cases go in stack-release.test.mjs (mos-1247; test-release.sh never calls stack-release.sh)

docs/plans/2026-10-22_sso-phase2-window.md

@@ -20,8 +20,9 @@ Two steps need `scripts/stack-release.sh` flags that don't exist at 02da6a2ae:
 The fix is one small row, approved in mos-1246: `activate --send` and `activate --no-sso`. `--no-sso`
 takes the Console flags from the rollback set of the activation that turned `--sso` on, the way `sso_base`
 already does for a rollback to a copy without `--sso`. It drops `--send`, and its plan line says so. `--send`
-refuses unless the run's Console flags hold `--sso`, given or carried (F39). test-release.sh gets cases for
-both. Darkwing builds it, and a seat other than Sage and Darkwing reviews it. Brief:
+refuses unless the run's Console flags hold `--sso`, given or carried (F39). The cases for both go in
+`packages/cli/tests/stack-release.test.mjs`. F39 named test-release.sh, but that suite tests `release.sh`
+and never calls `stack-release.sh`, so it runs whole and unchanged. Darkwing builds it, and a seat other than Sage and Darkwing reviews it. Brief:
 `docs/plans/2026-10-22_activate-send-nosso.md`. It lands and is re-pinned before the window, on Mos's go,
 run by Jason or Mos. The steps below assume it, and draft 3 names the new copy.