Command Hooks fixes and Build Warnings Log context, deduplication, and filtering

[mkarlesky]

Refs #194.

Summary

Command Hooks

The plugin had no specs at all. This PR fixes three bugs in it and covers it with unit, integration, and system specs.

• Empty hook arguments. :pre_compile_execute, :post_compile_execute, and :pre_runner_generate read argument-hash keys the core never sets, so their tools always received an empty ${1}. Each hook's arguments now come from one table of the keys the core builds:
  • the compile hooks pass the source file as ${1} and the object file as ${2};
  • :pre_runner_generate passes the test file, as documented.
• Tool lists. A hook configured with a list of tools failed validation. The validator walked the list by index through the configuration walker, which can't index lists. This has been broken since 1.1.0.
• Logging default. Hook validation added :logging to the project configuration instead of to the hook's own tool.
• System spec. A real test:all runs every test-build hook with a recording script, checking each hook's documented argument. A clobber afterward runs no build hook, which pins Comand hooks run after every command (including module:create, clobber, clean) #194.

Build Warnings Log

• Context. WarningCollector groups GCC and Clang diagnostics with the lines that explain them: the function or include context before a warning, and the source line, caret, and any note after it. Output in other formats is collected a line at a time, and compiler summary lines are left out.
• Deduplication. Each distinct warning is logged once per build context. A header warning's identity leaves out its include chain, so it is logged once rather than once per including file.
• New settings. :patterns and :excludes take regular expressions. :patterns replaces the default match of any line mentioning "warning", and :excludes drops warnings already accepted. An invalid entry stops the build, naming its setting.

Docs

• command-hooks.md:
  • corrects the hook names and fixes the broken example YAML;
  • documents each hook's arguments;
  • notes that build hooks don't fire for non-build commands, and that a failing tool stops the build.
• report-build-warnings-log.md: rewritten for context, deduplication, :patterns, and :excludes.
• Changelog: 💪 Fixed entries for Command Hooks, and a 🌟 Added entry for the warnings log.

Testing

• Unit specs: command_hooks_spec.rb is new, warning_collector_spec.rb is new, and report_build_warnings_log_spec.rb is extended.
• Integration specs: Command Hooks runs with real tool validation and execution. Build Warnings Log runs on real gcc output with real log writing.
• System spec: spec/system/command_hooks_spec.rb. With the old compile-hook key restored, it fails and shows the empty ${1}.
• Results:
  • rake specs:units: 4587 examples, 0 failures.
  • rake specs:integration: 436 examples, 0 failures.
  • Lint and the strict docs build are clean.

🤖 Generated with Claude Code