plans: row 200 follow-up N1 brief (#1744, Launchpad, Webby): the sso-config hint carries --instance NAME

This commit is contained in:
2026-10-20 19:12:34 -05:00
parent 9e10858160
commit 76134dfde1
@@ -37,3 +37,21 @@ a hand-edited pointer is not an option.
Webby approves the manifest. The cli suite and every `scripts/test-*.sh` are green on Sage's gate, and the
mutants are killed (one per refusal, and one that keeps `--auth-header` in the written flags).
## Brief: row 200 follow-up N1, the sso-config hint names the instance
Sage, 2026-10-21, from Webby's round 3 note N1 on row 200 (comment 29772). Gitea #1744. Owner Launchpad,
reviewer Webby, gate owner Sage. Size XS. Builds on row 200's landing 9e1085816.
`scripts/stack-release.sh` builds the sso-config refusal's first-step hint as `activate $TO without --sso
first, then write console.sso, then run activate $TO --sso`. For a named instance (row 190), both commands
need `--instance NAME`, and the hint leaves it out. An operator who copies them acts on the default instance.
- When the run names an instance, both commands in the hint carry `--instance NAME`. The default instance's
hint is unchanged.
- A test runs the sso-config refusal for a named instance and asserts both commands carry `--instance NAME`.
The existing default-instance case keeps its exact text.
- One mutant drops the flag from the hint, and it must die.
Gate: Webby approves the manifest. `packages/cli/tests/stack-release.test.mjs` passes whole, and the cli suite
and every `scripts/test-*.sh` are green on Sage's gate.