[nichinichisou0609]

Summary

• Bound compilation under laws, the regime census and the per-part bounds of a conversion run under the request's deadline. A compilation that would start after it is skipped; the search keeps its other bounds, so the result stays sound.
• Exact LUCK refinement starts a unit that runs to its end (an order's residue law, a power-twin comparison) only when the time left covers the longest such unit seen so far in the request. A refinement the deadline cuts short certifies nothing.
• The regime preparation, the post-search refinement and the bound over what a stop leaves unexplored are recorded as their own phases (regimeCompile, refine, bound), so the phases account for the request's elapsed time. docs/telemetry.en.md lists them.

Tests

• an_expired_deadline_reports_no_proof_and_starts_no_refinement
• a_tiny_deadline_returns_within_a_bounded_multiple_and_never_claims_a_proof
• cargo test -p ournotes-search

🤖 Generated with Claude Code