ByteAsk CLI v0.2.4

ByteAsk CLI 0.2.4

ByteAsk's best-measured harness configuration is now the default. Nothing to set up: every setting below is on
for new and updated installs, and each one can be changed in ~/.byteask/config.toml.

With ByteAsk Context connected (byteask context connect):

• ByteAsk follows a short set of working rules: reproduce the problem first, make the change complete across the
  related places (Context's find_related_changes and get_symbol list candidates), keep the repository's own
  helpers and names, and check the change with cpp_finish_check before finishing. Your own developer_instructions
  replace them.
• Context's code pack waits up to 2 minutes on large repositories, and a top-level CMakeLists.txt, meson.build or
  configure.ac marks a repository as C/C++.
• cpp_finish_check lists the places Context says may need the same change, right after its verdict.
• Headless runs (byteask exec) offer a smaller tool set; interactive sessions keep every tool.

C/C++ checks:

• cpp_finish_check builds and runs the nearest tests' programs first and names the other tests the change reaches.
• A change that no compiled file reaches is reported as not checked, never as passed.
• When a turn ends with a C/C++ change nobody checked, ByteAsk runs the check once and shows the result.
• C/C++ tools whose program is not installed are not offered.

Builds and long commands:

• ByteAsk's background builds run at idle priority, give way to your builds in the same tree, and stop first under
  memory pressure.
• The environment note states the memory limit and a job count that fits it.
• On a long-running command without a terminal, ByteAsk waits 30 s before the first check and up to 3 minutes
  between checks; every wait ends as soon as the command exits.

Platforms: Linux (x86_64, arm64) and Windows carry everything above. The macOS engine in this release is the 0.2.3 engine; the 0.2.4 macOS engine follows.