Files
stack/docs/plans/2026-10-22_activate-send-nosso.md
jason.woltje f0d0b31e9b docs: briefs for the activate --send/--no-sso row, FED R3 and the 193b1 split; phase 2 plan F39 fixes
- docs/plans/2026-10-22_activate-send-nosso.md: the row Mos approved in mos-1246. Darkwing builds,
  Filbert reviews. --no-sso drops --send, --send refuses without --sso (F39), test-release.sh cases.
- docs/plans/2026-10-22_federation-r3.md: FED R3, the broker user principal, on 193b1a's candidate.
  Owner Morgana, reviewer Dewey. Its parents R1 and row 196 have landed, and the filing was owed.
- human-users-build.md: 193b1 split into 193b1a (message filter, chained on 196) and 193b1b (viewer
  verbs and board refusals, after FED R3 and R4). Mutant 3 moves to 193b2 (sage-2288, morgana-0063).
- sso-phase2-window.md draft 2: the tool gap paragraph names the approved row, and rollback step 1
  drops "--send follows the pointer", since --no-sso drops --send (mos-1246 items 2 and 3).
2026-10-21 19:42:01 -05:00

3.9 KiB

Row: stack-release.sh activate --send and --no-sso, for the Q175 phase 2 window

Sage, 2026-10-22, for Mos's go mos-1246 (re sage-2285). Gitea #385, Vikunja #412. The window plan is docs/plans/2026-10-22_sso-phase2-window.md (draft 2, 92be0db02).

Brief: activate --send and --no-sso

Owner Darkwing. Reviewer Filbert (not Sage or Darkwing, mos-1246 item 1). Gate owner Sage. Base: origin/refactor at this brief's commit. It lands and is re-pinned before the phase 2 window. That re-pin is Q173 work on Mos's go, run by Jason or Mos. If the target copy's schema differs from 3j and needs --migrate, it waits for Jason.

Why: at 02da6a2ae, scripts/stack-release.sh activate has --no-send but no --send, and nothing turns --sso off. Without --sso, sso_base carries it from the pointer, and check_target refuses the pointer's copy as already-active. So the window can't turn send on with --sso (mos-1195), and its same-copy rollback (mos-1245 R1) can't run.

Send and forward auth (mos-1246 F39): send went off on 10-20 (mos-0972) because, under forward auth, any same-uid process can send as Jason through 127.0.0.1:7332. So send goes only with --sso.

What to build, in scripts/stack-release.sh only:

  1. activate --send puts --send into RUN_CONSOLE where webui-service.sh renders it. It refuses unless the run's Console flags hold --sso, given or carried. With --no-send it is a usage error. The plan's send line reads send: on; --send was given, or send: carried when the pointer already holds it. check_target lets --send name the pointer's copy when the pointer holds no --send.
  2. activate --no-sso is allowed only when the pointer's Console flags hold --sso. Otherwise it refuses with a named reason. It takes the Console flags from the rollback set of the activation that turned --sso on (that set's show-$CONSOLE_UNIT.txt, checked against its SHA256SUMS), the way sso_base already does for a rollback to a copy without --sso. It drops --send, and its plan line says so (F39 a). The tester follows the pointer. A set it can't read, or a set whose Console already ran with --sso, refuses before anything stops. check_target lets --no-sso name the pointer's copy. With --sso, --send, a proof pair or --no-proof, it is a usage error. The plan prints sso: off; Console flags from <set>/<file> and lists every flag it restores.
  3. Both flags are refused under --units external, like the other unit-render flags (row 232).
  4. The usage text and the header comment name both flags. No other behavior changes.

Tests, whole files on Sage's slot: packages/cli/tests/stack-release.test.mjs, packages/cli/tests/stack-release-external.test.mjs for item 3, and scripts/test-release.sh.

  • T1: --sso --send on a pointer without send. The plan shows send: on, and the unit and the pointer gain --send.
  • T2: --send without --sso, given or carried, refuses (F39 b). --send --no-send is a usage error. --send on the same copy when the pointer already has send refuses as already-active.
  • T3: from an --sso --send pointer, --no-sso on the same copy returns the unit and the pointer to the pre---sso flags byte for byte, with no --send (F39 a and c). The tester stays as the pointer had it.
  • T4: --no-sso refusals, each before any unit stops: a pointer without --sso; a tampered set (SHA256SUMS mismatch); a set whose Console ran with --sso; --no-sso combined with --sso, --send or a proof flag.
  • T5: --units external refuses both flags.

Mutants, each killed: drop the SHA256SUMS check in the --no-sso path; let --no-sso run with no --sso in the pointer; let --no-sso keep --send; let --send run without --sso; let --send and --no-send combine.

Gate: Filbert approves the manifest. The two touched test files run whole plus test-release.sh, and the mutants are killed. No live activation in this row. The window uses it.