mlx-bun library API
    Preparing search index...
    • Bounded binary: should THIS chunk update THIS section? Kept schematic on purpose — no concrete example the small model could copy into its answer.

      Framed around the SUBJECT the heading names, NOT a value comparison: the small model otherwise defaults to "no" whenever the note states a different value than the section currently records (a newer value vs the section's older value), which is exactly the correction we must catch. Empirically (e4b, maxTokens 4) this phrasing matches a contradicting same-subject correction 3/3 while still declining off-topic and cross-section notes; the chunk LABEL is deliberately omitted — including it flipped the model back to value-comparison and dropped the match rate.

      Parameters

      Returns string