[tylerreckart]

Summary

Cuts v1.0.0 through the human release path: project(arbiter VERSION 1.0.0) in CMakeLists.txt, and a changelog section for that version. This is not an Actions → Version bump → major run.

The 1.0.0 notes summarize what landed since 0.13.x: the ONNX installer and $ORIGIN / @loader_path fix, the bge router default and ARBITER_ROUTER, the stability contract, arbiter --version / -V, the ~openai/gpt-sol-latest default, the tool-loop budget and partial sub-agent results, go run confirmation, and the TUI redesign.

Also repairs the 0.13.13 changelog: the repeated ### Fixed block is gone, and the stray - - before the glyph bullet is a single list marker. The #396 tool-loop work, which shipped inside the 0.13.14 tag and was missing from the notes, is recorded under 0.13.14.

## [1.0.0] is already in the changelog, so bump_version.sh will not open a second release commit or a second notes section when this merges.

ASan failed twice in fn+up page up does not kill the session: the input row did not show still-alive within the wait while the frame pump caught up with the page-up burst, and the process was still running. That check now uses the same fallback as the other editor echo test in the file: if the live row does not show the text, submit the line. A deadlock still never echoes it.

What happens on merge

A human merge of this PR starts CI on that main SHA (a GITHUB_TOKEN push would not). When that CI workflow finishes green, version.yml runs because the event was a push to main.

bump_version.sh in auto mode sees CMakeLists 1.0.0 ahead of the latest tag v0.13.14, so the next version is 1.0.0. The changelog heading already exists and the pin is already 1.0.0, so it does not create a chore(release) commit. HEAD is origin/main, so the job tags that SHA v1.0.0 and pushes the tag. It does not open another pull request.

The tag push itself does not start release.yml, because the tag is pushed with GITHUB_TOKEN. The same job then dispatches release.yml with tag=v1.0.0. That workflow requires a successful ci.yml run on the tagged commit, builds arbiter-linux-x86_64.tar.gz and arbiter-macos-arm64.tar.gz (each with a .sha256), and publishes a GitHub Release titled arbiter v1.0.0 with those assets plus install.sh.

Test plan

• Linux, ASan, TSan, and macOS CI are green
• After merge, version.yml tags v1.0.0 on the merge SHA and release.yml publishes the binaries