Polish release docs and add CI checks
- Correct stale references and headline-path wording in READMEs and Lean docstrings - Document build steps, comparator requirements, sweep scope, and coverage - Unify Apache headers across Lean and C++ sources - Add a bwrap-free axiom audit for the headline theorems - Add a Gitea workflow running lake build, the axiom audit, C++ tests, and coverage - Match LLVM coverage tool versions to the compiler and recreate stale build dirs
This commit is contained in:
1 parent
73e371fb40
commit
273ad72f0c
34 files changed
+431
-133
No files matched your search
@@ -2132,7 +2132,7 @@ theorem minimal_iff_sound_and_necessaryRange {r : RangeRead} {res : Result}
|
||||
/-- A minimal sound range is contained in every sound range: intersecting it with
|
||||
another sound range stays sound and is a subrange, so minimality forbids the
|
||||
intersection from being proper. This is the least-element half of the
|
||||
least-sound-range conjecture (issue #14), and it is unconditional — no
|
||||
least-sound-range statement, and it is unconditional — no
|
||||
nonemptiness or realizability hypothesis is needed. -/
|
||||
theorem Minimal.subrange_of_sound {r : RangeRead} {res : Result} {cr : ConflictRange}
|
||||
(h : Minimal r res cr) {cr' : ConflictRange} (hs : Sound r res cr') :
|
||||
@@ -2233,7 +2233,7 @@ theorem exists_unique_minimal_of_minimal {r : RangeRead} {res : Result}
|
||||
/-!
|
||||
## The canonical range at offset one
|
||||
|
||||
The first concrete instance of the minimal-range conjecture: when both selectors
|
||||
The first concrete instance of the minimal-range theorem: when both selectors
|
||||
have `offset = 1` and the result is complete (`more = false`), the minimal sound
|
||||
conflict range is the canonical range `[begin.key, end.key)` named directly by
|
||||
the read. At offset one the resolved window `[resolve begin, resolve end)` cuts a
|
||||
|
||||
Reference in new issue
Block a user