feat(repipe): standing brief — be an interface, not an oracle

[mahaloz]

The corpus is deliberately hostile — 171 of its 250 challenges carry at least one obfuscation class, 57 are code-virtualised. Hostile binaries are exactly where a decompiler's automatic answer is wrong, so the interesting question this loop asks is not "why did kuna guess wrong" but "why could the agent not tell it the right answer?"

That is now a standing instruction to both halves of the loop.

Testers file a missing interface whenever they catch themselves thinking "kuna should have known this" — because the useful form of that complaint is almost always "kuna should have let me say so". Define a function boundary, override a jump table, declare a blob as data with a type, steer structuring, fix a prototype, make a rename persist. They check kuna catalog --json first: an option that already exists is a discoverability problem, not a missing interface, and that is worth reporting too. The prompt now names the challenge's own obfuscation classes, because "this one is virtualised and string-encrypted" changes which interface is worth asking for.

Builders expose before they invent. kuna-console registers ~37 intervention-shaped commands — map function, override jumptable, force goto, force datatype, parse line, retype, structure blocks … — and none is reachable from the kuna binary. Three very different jobs hide behind "add an interface":

1. it already works in the console and is merely unexposed → wiring, the common case, verifiable in one decomp_dbg invocation before any code is written;
2. it answers engine integration not yet ported (global add, dump, callgraph build confirmed) → real engine work, [PROPOSAL] route, not a half-port;
3. there is no decision point at all → that is a phases.toml option, not a subcommand, because a new judgement call ships behind a named flag.

Two rules keep the result usable by the thing it is for:

• A durable assertion beats a one-shot flag. The model is assert(phase, anchor, type, value, strength), consulted on every re-run. An agent that renames forty functions and loses them on the next invocation has gained nothing.
• Machine-readable in, machine-readable out. Assertions as a file or repeatable flags; JSON beside the human form.

smoke.sh 71/71, make check-spec OK. No Rust touched.

🤖 Generated with Claude Code