docs(wiki): describe the HTTP server's statuses, protocol check and bind policy
proto is now required, unknown parameters are refused, errors carry their HTTP status (400, 403, 500) instead of 200, and the host is bound to its first address. The parallel scheduling example gives proto and uses jobs, which replaces async.
Refs CoreTrace/coretrace#191
docs(wiki): update for sectioned config, exit-code gate, SARIF and server hardening
Brings the wiki back in line with the code since March:
- --tool-config is now --config, and the file is sectioned (analysis, files,
output, runtime, server, stack_analyzer, tools) with the legacy spellings
documented as deprecated
- exit-code gate (--fail-on, codes 0/1/2/3) and its HTTP equivalent result.gate
- merged SARIF 2.1.0 output with cross-tool deduplication and fingerprints
- unified Diagnostic model, ToolOutput sink replacing per-tool IPC, and the
uninterpreted-tool notion
- HTTP: full run_analysis parameter table, new result keys, InvalidInput,
body limit, opt-in CORS, 503 while shutting down
- coretrace-python-analyzer: language routing, bundled Nuitka build, release
archive glibc baseline
- build: PARSER_TYPE/getopt removed, current CMake options, dependency pins
and CI workflows
- shipped defaults (models and bundled tools) and tool path resolution, which
replace the hardcoded cppcheck path
- refreshed limitations: stale entries removed, current ones verified