row 273 notes: name the changed T57 item 3 assertion for review (sage-2321)

2026-10-21 20:34:59 -05:00
parent 6273b65e9d
commit 978143bf42
1 changed files with 9 additions and 2 deletions
@@ -57,8 +57,15 @@ Filbert accepted the walk. Sage ruled both findings into this row.
  whenever the run drops the pointer's `--sso`, so it is still the one place that drops it. The plan
  line reads `send: dropped; the run drops --sso, and --send needs it (F39)`, and the steps log gets
  `drop --send; the run drops --sso`. Row 200's sso line now names only the tester as following the
-  pointer. One T57 case pinned the old carry (a legacy `--send` pointer, `--sso`, then a rollback to
-  B). It now expects no `--send`.
+  pointer.
+- Changed existing assertion, for the review to approve by name: T57 item 3 (sage-1389), "the
+  plain case", ends with `assert.deepEqual(pointer(g).console,[...noSend(gbase),...pair(f)])`. It
+  used to expect `'--send'` at the end. The case seeds a legacy `--send` pointer, turns `--sso` on
+  (which carries `--send`), then rolls back to B, whose Console has no `--sso`. A carried `--send`
+  that ends without `--sso` breaks F39 b whatever its source, so the old pin asserted the wrong
+  outcome (Sage accepted this in sage-2321). Row 200's two sso plan strings also lose "--send and"
+  (`ROLLBACK_PLAN` and the round 3 named-instance case), since `--send` no longer follows the pointer
+  on that path.
 - N1: the walk skipped an ok line with no activation. Skipping it could land on an older set that
  isn't the right one, so it now refuses `sso-off-flags` with `an ok line in the log names no
  activation`. The walk reads the log through `mapfile`. That gives no entry for an empty log, so a