stage1-probe.ts
@file Which candidate fix actually moves the config stratum?
Overview
@file Which candidate fix actually moves the config stratum?
Four variants over the same golden set, so the Stage 1 build order is chosen
by measurement rather than by the order the design brief listed them in.
naive the committed baseline: 40-line windows
kconfig grammar-aware chunks for .conf files
expand naive chunks, query expanded through a vocabulary alias table
kconfig+expand both
headers naive chunks, each given a deterministic keyword header
The alias table and the overfitting hold-out live in expand.ts, because the
independent-set scorer has to run the same expansion.
depends on chunk-kconfig.ts corpus.ts expand.ts golden.ts headers.ts retrieve.ts
flowchart TD hitAt --> covers
API
Ffunction hybridChunks(): Chunk[]
Naive windows everywhere except .conf, which gets one chunk per symbol.
main · calls buildChunks, chunkKconfig, isKconfig, readLinesUndocumented (5)
mean, main, q, hitAt, pick