Xean 4.2.0

xean 4.2.0 lets Explorer read notebook entries on demand through the read_notes tool. It starts with a summary index and can request detailed summaries or complete texts. Coordinator uses a compact index, retaining full text for notes without summaries.

Explorer may apply a verified result from a summary that contains the necessary statement, hypotheses, conventions, and limitations. Correctness verification checks summary fidelity against full text. Source and correctness trust, verification timing, and joint reconstruction of candidates and generated dependencies retain their existing requirements.

The note-access experiment at 96aa0d5 ran two campaigns on each First Proof Batch 3 problem with gpt-6-astra/max. At the release checkpoint, 18 of 20 campaigns had passed independent review. Both P08 campaigns were still running. Across 16 pairs with independent PASS results for both the experiment and 4.1.0 controls, recorded solver cost fell from $254.19 to $166.10, including Coordinator cost falling from $81.29 to $7.77. Packet preparation, independent review, and unknown failed-response usage are excluded. Prepared summaries and note access changed together, so this comparison does not isolate their effects. Seven pairs finished faster, and median paired elapsed time increased by 4.5%.

The final summary-reading policy at ad4541a has narrower live evidence: a gpt-6-luna/high Explorer used a sufficient verified summary without fetching the proof, and a correctness verifier rejected a summary that omitted a necessary hypothesis. The full-campaign comparison predates that final prompt change.

Version 4 remains deliberately narrow: reasoning over prepared notes and checking the resulting arguments. Literature discovery and paper preparation require an external workflow. Optional Codex citation search remains available during source verification. Internal acceptance and independent model review remain separate from formal certification.

Requires Bun 1.4.2 or later on macOS or Linux. Download xean-4.2.0.tgz and verify it with SHA256SUMS. Use fresh campaign databases and preserve earlier campaigns with their recorded runtimes. The README and FAQ describe setup, note preparation, verification modes, and limitations. Pinned Pi dependencies are unchanged. Release and packaged checks each pass 114 tests and 1,109 assertions.