test/transcripts/f3a/sabotage-red.txt

# F3a sabotage transcript (post-review-fix) -- provenance: folio 5a53dbd, sigil 0.19.2, sigil-doc f63e98a via dev-redirects, 2026-08-25

3SAB-F3A LEG S1: remove the revision comparison

4 PREDICT RED: sab-revcheck (a stale write publishes)

5 PREDICT GREEN: sab-uncontended

6SAB-F3A LEG S1: RED AS PREDICTED

7SAB-F3A LEG S2: remove rebase precondition 2 (old value unchanged)

8 PREDICT RED: sab-precond2 (a conflicting rebase publishes)

9 PREDICT GREEN: sab-uncontended, sab-rebase-report

10SAB-F3A LEG S2: RED AS PREDICTED

11SAB-F3A LEG S3: land the edit at the FIRST MATCHING TEXT, not the span

12 PREDICT RED: sab-span, sab-uncontended, sab-rebase-report (the

13 fixture's prose duplicates catch all three via the

14 postcheck: the value never lands in the task)

15 PREDICT GREEN: sab-journal, sab-revcheck, sab-precond2, sab-postcheck-defends

16SAB-F3A LEG S3: RED AS PREDICTED

17SAB-F3A LEG S4a: serializer drops due's closing quote -- the POSTCHECK

18 must refuse and nothing may publish (this leg proves the reparse

19 DEFENDS; S4b then proves the defense is load-bearing)

20 PREDICT RED: sab-span, sab-rebase-report (their due edits refuse)

21 PREDICT GREEN: sab-postcheck-defends (refusal + unchanged bytes is

22 that arm's plant-mode acceptance), sab-uncontended

23SAB-F3A LEG S4a: RED AS PREDICTED

24SAB-F3A LEG S4b: S4a's serializer defect PLUS the verify verdict ignored

25 -- skip post-write reparse: the corrupt note PUBLISHES

26 PREDICT RED: sab-postcheck-defends (published corruption), sab-span

27 PREDICT GREEN: sab-uncontended (nothing corrupt to catch on priority)

28SAB-F3A LEG S4b: RED AS PREDICTED

29SAB-F3A LEG S5: the coordinator publishes WITHOUT taking the lock

30 PREDICT RED: gate-f3a arm 3 -- some round yields two OKs (a lost

31 update), which is what the lock exists to prevent

32SAB-F3A LEG S5: RED AS PREDICTED (5 round(s) with a lost update)

33SAB-F3A LEG S6: the status transition no longer writes its @update

34 PREDICT RED: sab-journal (the count-increase postcheck REFUSES the

35 unjournalled write, so the transition cannot publish)

36 PREDICT GREEN: sab-uncontended

37SAB-F3A LEG S6: RED AS PREDICTED

38SAB-F3A LEG S7: acquisition degrades to a SHARED lock (excludes nothing

39 it cooperates with, still conflicts with an exclusive prober)

40 PREDICT RED: sab-coord-init via the SECOND-ACQUISITION direction of

41 the exclusion probe -- the raw-flock direction alone

42 cannot see this plant, which is why 1b exists

43SAB-F3A LEG S7: RED AS PREDICTED

44SAB-F3A LEG S8: a successful rebase stops reporting itself

45 PREDICT RED: sab-rebase-report (precondition 5: a silent rebase is a

46 defect even when byte-correct)

47 PREDICT GREEN: sab-uncontended

48SAB-F3A LEG S8: RED AS PREDICTED

49SAB-F3A LEG SA: assertion layer -- flip sab-revcheck's expected reason

50 PREDICT RED: sab-revcheck (the driver's own assertions are live)

51SAB-F3A LEG SA: RED AS PREDICTED

52SAB-F3A: restoring and re-running the FULL gate as the restore proof

53SAB-F3A: restored gate GREEN

54---

55F3A_SABOTAGE legs=10 red=10 setup_failed=0

56SAB_RC=0