kernel-Complex.sumRange_mul_eq_diag_add_corner
- Kind
- kernel-term
- Status
- checked
Supports: `Complex.sumRange_mul_eq_diag_add_corner` is admitted with exactly the type in formal.statement. It composes `Complex.sumRange_mul_double[f,g,n,n]` -- which turns a product of partial sums into the RECTANGLE sum over {(i,j) : i<n, j<n} -- with `Complex.sumRange_rect_eq_diag_add_corner`, via Equiv.trans. The rectangle decomposition is itself the Equiv-port of Nat.sumRange_rect_eq_diag_add_corner, same induction structure. THE PORT IS NOT MECHANICAL: Complex.Equiv has no free single-sided congruence, so every rewrite under `add` needs an explicit add_congr paired with Equiv.refl on the untouched side, where over Nat it is just Eq and a rewrite chain.
test "$(scripts/cargo-serialized.sh test -p axeyum-lean-kernel --lib complex::complex_tests::the_rectangle_decomposition_is_stated_exactly -- --exact 2>&1 | grep -Ec 'test result: ok\. 1 passed; 0 failed')" -ge 1 Evidence notes
A footprint check cannot carry this claim: the theorem with the CORNER TERM DROPPED is precisely the refuted naive identity, and it would have an identically empty footprint. Mutation-verified by the establishing lane: a single-character mutation of the pinned constant took the suite from 10 passed to 9 passed / 1 failed, naming this test and no other; the file was then restored and hash-verified against the committed blob, and the suite returned to 10 passed. The command is anchored on the exact `1 passed; 0 failed` count so an unmatched filter -- which prints `running 0 tests ... ok` and exits 0 -- cannot read as success. Note that complex_tests.rs OVERFLOWS the default 2 MiB stack and aborts with SIGABRT; the suite runs bodies on a 64 MiB thread via its own on_a_deep_stack helper, so a SIGABRT here is an environment fact and not a proof failure.