Every runner printed whatever came back and exited 0, and fell back to a
second raw HTTP call when the SDK import failed. Now each recipe carries
expect.json, the answers a careful reader gives on its own input: a list of
acceptable options for a choice, of level indices for a score, true or false
for a noul. run.py and run.ts send request.json through the SDK, print every
answer, and exit 1 when a checked one is wrong. A question with no obvious
answer on its input is printed and not checked.
Recipes 09 and 11 had no input with an obvious answer, so each state gains
the one fact that decides it. The recipe READMEs describe what each recipe
asks instead of capabilities it never exercised, and copy the request and
checked answers from the two JSON files.
Co-authored-by: Hanzo Dev <[email protected]>
zeekayandHanzo Dev