An agent asked to add a feature reaches for new machinery, and the review that would have caught it reads like an argument: "couldn't we just use the platform for this?" — met with "I looked, it doesn't do what we need". Nobody can tell from the outside whether anyone looked.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+.
Run the checked-in example
# A case already solved by the standard library: exits 1 and says so.
node bin/minimum-solution-ladder.mjs --worksheet examples/uuid-generation/worksheet.json
# The proposal is already on the lowest verified rung: exits 0.
node bin/minimum-solution-ladder.mjs --worksheet examples/debounce-search/worksheet.json
# A ladder checked only by assertion: exits 2, incomplete, no recommendation.
node bin/minimum-solution-ladder.mjs --worksheet examples/asserted-only/worksheet.json
# The machine-readable report.
node bin/minimum-solution-ladder.mjs --worksheet examples/uuid-generation/worksheet.json --jsonRead the result
The rows below are printed by --help from one frozen table in src/index.mjs, so this document and the tool cannot say different things about an exit code — which they did, until the row for 0 claimed the proposal had been verified while the rule table below correctly documented two rules that pass without verifying it.
Scope
Exceeding a limit is an incomplete result naming the limit — never a silent truncation and never a pass. Limits may also be set in a --config file ({ "schemaVersion": "1", "limits": { ... } }); a flag overrides the file, and an unknown key in either is refused.