[AUTOMATED] fix(repipe): the arena brief told testers half the CLI did not exist - #439
Merged
Merged
Conversation
…d not exist The tool protocol handed to every tester froze kuna's subcommand list in prose. Four of its five "facts already verified" were false by round 4: it named nine subcommands when there are sixteen, said `decompile --json` exits 2 when it exits 0, said `functions --json` records carry no size when they do, and said there is no `xrefs`, `strings` or `disassemble` subcommand when all three ship. Derive the list from `kuna --help` on the binary the arena actually ships, and replace the per-fact block with things that stay true (no persistence, cold load per invocation, an empty result is not proof) plus a pointer to `kuna docs`. A brief can now only ever be as wrong as the binary in the arena. `kuna --help` writes its usage to stderr with rc=0, so the parser reads both streams. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The problem
Every RE-friction tester gets an
AGENTS.mddescribing the tool it is beingmeasured against. That brief froze kuna's subcommand list in prose, and the
prose rotted. Round 4's arenas, built minutes ago from
main:Against the binary those same arenas ship:
Sixteen, not nine. Three of the subcommands the brief says do not exist do.
Two more of its five "facts already verified" are also false now —
kuna decompile <bin> <fn> --jsonexits 0 and emits JSON rather than exiting 2, andfunctions --jsonrecords carrysizeandobject_location.The fix
kuna --helpat arena-build time, so thebrief can only ever be as wrong as the binary in the arena.
what replaces it is the part that does not change (no server mode, no
persistence, cold load per call, an empty result is not proof of an empty
binary) plus a pointer to
kuna docsand an instruction to checkkuna <subcommand> --helpbefore concluding something is missing.kuna --helpwrites its usage line to stderr with rc=0, so the parser readsboth streams; failing to find the line raises rather than shipping a brief
with a blank list.
The tests
Rebuilt all nine round-4 arenas through the changed path:
workspace build --forceandworkspace checkboth report zero violations on each, and eachbrief now names all sixteen subcommands.
🤖 Generated with Claude Code