Debug builds: price the split by turning it off The page argued the split is worth having and measured it only as an inline-vs-split object comparison. Turning it off is the clearer demonstration: lame built four ways with the exact flags each level composes gives 1.72x for --debug=full against a normal build, and 11.01x for the same build with -gsplit-dwarf removed. Also records the two results that read backwards: full is the SMALLEST of the three levels, because -O0 emits smaller code than -O2 and past the split the -O choice moves the archive more than the debug info does. Corroborates Documentation/usage.md, which carried ~3x for full until GH-97. Refs #97 Claude-Session: https://claude.ai/code/session_019T1bLfDhuHJpNNhn8CHVLJ
Add the first wiki pages: worked examples, choices, split DWARF Covers what the repository deliberately does not carry: goal-shaped sequences, the reasoning behind a default, and the retention contract that --debug creates. The flag reference stays in Documentation/usage.md, which the every-flag-is-documented gate checks on every push. These pages link to it rather than restating it, so there is no second copy free to drift. Refs #96 Claude-Session: https://claude.ai/code/session_019T1bLfDhuHJpNNhn8CHVLJ