docs(wiki): document coretrace-runtime-analyzer
Six pages, written from README.md, include/runtime_analyzer.hpp and
src/runtime_analyzer.cpp:
- Home: the compile/run/collect flow, and that this is an early prototype
- CLI Reference: every option, the -- boundary between analyzer and compiler
arguments, and batch mode compiling each source separately so test files
that each define main do not collide at link time
- Event Collection: the exact substring each counter matches, and what follows
from that - counters overlap, entry/exit need not match after an abort, and
program output containing a pattern is counted
- Proof Scripts: the full sweep, F4 and F11, and why F11 checks both the
runtime report and the collection counter
- Public API: AnalyzerOptions, AnalyzerResult, CollectionSummary, BatchResult,
and why compile_success and executed are separate from success
- What It Does Not Do: pattern matching rather than a protocol, no per-event
detail, no verdict or report format, and where the mature analysis lives