CODE-065: kv header lexer: unknown keys end the block, `|` scalars, unfenced YAML

Now: OPEN
Sev: LOW
Rep: ///bee
Ask: gritzko
Rev: ///bee#8cb69a0
See: BEE-024
See: TODO-003

Input

Context

index/kv.js:136:9B-152: one non-pair line inside the meta block ends it, so a 4+-char key (Done:, Note:) or a wrapped value drops every registered pair below it (no live instance in 1124 journal tickets today, a latent hazard). :157-167: the YAML lexer keeps desc: | with the literal | as payload though INDEXES.mkd says a multiline scalar is SKIPPED whole, and with no closing fence it scans the whole file, turning body prose into rows. :171-179 readText slices at 1 MB on a BYTE boundary before utf8.Decode and never releases the mmap handle. Found in the 2026-09-18 index review.

Goals

Skip an unknown Word: value line instead of ending the block; skip |/> scalars; bound the unfenced scan to bodyLine; slice on a code point.

WIP

Design decisions

An unfenced --- head takes NO keys: MDFM hands the whole file back as the head, and a page of prose is no preamble.
The cap backs off at most 3 continuation bytes; further back the bytes are malformed and the decoder still says so.

TODOs

[v] repro: Done: line hides Ref: below it
[v] lexer fixes, each with a row test

Blockers and bummers

No handle to release: a read map has no fd and no slot (quickjab io.c:681), so io._munmap there is a silent no-op and the wrapper's death munmaps; 20k reads held flat at 32 VMAs, so that half of the ticket is a non-issue, not a fix.
A WRAPPED value line still ends the block: the Goals name the unknown Word: value line alone.

CODE-065: kv header lexer: unknown keys end the block, | scalars, unfenced YAML