test/fixtures/f3a/note.sgd

1#lang folio/doc

2@note["topics/f3a-fixture" title: "F3a transaction fixture" tags: '("f3a")]

4@p{Prose with a deliberate DUPLICATE of the scalar texts below: the words

5'active and 'high and "2026-08-30" appear here verbatim, so a mutation that

6finds FIRST MATCHING TEXT instead of using the recorded span lands in this

7paragraph and corrupts prose. Multi-byte text sits here too -- Ünïcode, naïve,

8café -- so every span after this line has byte offsets ahead of its scalar

9offsets and a byte/scalar conflation cannot stay green.}

11@section["Tasks" id: "tasks"]{

@task["t-alpha" title: "The braced-body target" status: 'active priority: 'high due: "2026-08-30" tags: '("alpha" "target")]{

14@p{The primary mutation target. Braced body, so the journal inserts before the

15closing brace.}

16}

18@task["t-journalled" title: "Already carries a journal entry" status: 'ready priority: 'medium]{

19@p{This task ALREADY has an @code{@@update} child, so a journal postcheck that

20tests mere existence instead of a count increase passes vacuously here.}

22@update["u-prior" timestamp: "2026-08-01" author: "fixture"]{

23@p{A pre-existing journal entry.}

24}

25}

27@task["t-done" title: "Finished, awaiting reopen" status: 'done priority: 'low]{

28@p{The reopen target: done -> ready is the ruled edge.}

29}

31}

33@end note

35@project["projects/f3a-fixture" title: "Named-block container" status: 'active]

37@p{A second root whose body is the named-block spelling, so the journal

38insertion point is the @code{@@end} line rather than a closing brace.}

40@task["t-block" title: "Task inside the named block" status: 'ready priority: 'medium]{

41@p{Body here.}

42}

44@end project