The report was written in the order the pipeline runs, so a user reading one had to
reach line 380 before meeting the first evaluative statement, and the warnings were
last. Every run was 314 to 407 lines whether it succeeded or failed, about 200 of
them fixed prose. The anisotropy section printed 21 keys and announced DETECTED
(strong) on 54% of all runs - "strong" is the statistical confidence, which a reader
takes as the severity - and reported a censored fit, which is survival-analysis
vocabulary for good news.
Assemble the report into a document and render from it, rather than streaming it out
as the pipeline goes. That is what allows a verdict to sit above the evidence it was
drawn from: SUMMARY carries VERDICT, one sentence of plain text, the warnings and
ten facts, and it is composed after the sections that produce them. A clean run is
188 lines, a failed one 93, and the verdict is on line 25 in both.
Warnings now carry a closed pathology vocabulary alongside their free text, so a
consumer can switch on the code and a reader still gets the sentence.
Everything removed from the default report is still written under --developer, which
also carries the internals worth having when diagnosing the program rather than the
crystal: the gate keys behind the anisotropy verdict, the operator and candidate
tables, the sweep and spindle internals, and the essays.
Nine statements the report made that were not true are fixed here as well. Among
them: --mode scale printed a detector tilt of exactly zero on tilted data, which is
worse than printing nothing because nothing about it looks wrong; every --mode scale
run carried a "No image indexed" warning, because a key that is absent and a key
measured to be zero were the same value; and a fitted resolution was asserted past
the point where the run's own table shows CC1/2 at zero.
REPORT_VERSION is 8.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EFEJG6WBQv8th4UJFNe53N
leonarski_fandClaude Opus 5
d6ccdbdb61
