test/transcripts/f1b/gate-green.txt

1=== F1b gate ===============================================

2repo : /home/daviwil/Projects/Code/sigil/task-f1b-folio-doc-reader @ 7eed7cd8fcd10314fc8500bd33e835217f0353bb

3compiler : sigil 0.19.0 (b99b8f2d)

4sigil-doc : f83d8d86c9ecfd4701f6ef2994f42ff16b590f3a (via dev-redirects, NOT a release)

5sigil-doc dirty : 0 files

6cache : /tmp/f1b/clean019.LJzfDQ

7============================================================

8sigil-doc release: v0.1.3

9--- arm 1: build

10arm 1 OK: bundle built, 139 modules, all three new modules compiled

11--- arm 2: reader suite

12arm 2 OK: 32/32 tests passed, count derived from test/test-folio-doc-reader.sgl

13--- arm 3: refused witnesses by EXACT MEMBERSHIP

arm 3 OK: refused = exactly {milestone note phase project}; 7 admitted; 105 probe checks; comparator proven to see a missing AND an extra member

15--- arm 4: the section-child predicate delegates rather than re-enumerating

arm 4 OK: delegates to block-node?, re-enumerates none of 13 core kinds (detector proven to fire on an expanded copy); descent set DERIVED from sigil-doc = 9 containers, all present in lower-child

17--- arm 5: delegation parity

arm 5 OK: byte-identical canonical datum over 7155B, 19 node kinds exercised; one-byte-shift control differs; denominator = 25 author exports (deliberately excluded: video, example, project-check, term-ref -- each needs external assets, a subprocess-backed verifier, or a glossary this fixture does not declare)

19--- arm 6: no-execution witness

arm 6 OK: 2 detection channels proven able to fire in this run (6 markers, 5 sentinels); folio/doc refused the manuscript and fired neither channel; @code body inert on both paths; argument position pinned as the one channel that still evaluates

21--- arm 7: publication fallback from a read manuscript

arm 7 OK: 61 checks green across plain/HTML/Typst from a PARSED manuscript, and the harness demonstrably goes red on injection

23--- arm 8: probe harnesses go red on injection

24arm 8 OK: both probe harnesses proven able to go red on this run

25--- arm 9: reader-tier passivity

arm 9 OK: 3 reader-tier files inside their allowlist; extractor proven to see a planted violation; allowlist proven to refuse 10 and accept 6

27--- arm 10: reader/inspector layering

arm 10 OK: the reader refuses the duplicate document and the inspector still describes it (2 diagnostics, id status ambiguous) -- the layers disagree in the intended direction

29--- arm 11: suite arithmetic

30arm 11 OK: 351 + 32 = 383 across 22 + 1 = 23 files; test-folio-doc-model 36 and test-folio-doc-inspect 37 both unchanged

F1B_GATE_GREEN arms=11 modules=139 tests=32/32 total=383/383 files=23 profile_checks=105 parity_bytes=7155 parity_kinds=19 publication_checks=61 core_kinds=13

33GATE_EXIT=0