Updated the six oracle questions in bodies/ and recorded successful live draft checks in results.json. All six have no blockers or wording/not_answerable suggestions; all 12 schedule.create checks were accepted.

Corrected the check coverage explanation in README.md and added CHANGELOG.md. The experimental label remains unchanged.

Verified with npm run validate, live draft and schedule checks, results consistency checks, and git diff --check. Live response snapshots are in test/scratch/; draft response bodies are also recorded in results.json.

results.json is true. I re-ran the three oracle drafts (bodies 01, 04, 06) and three schedule bodies (01, 06, 07) against the live POST https://api.imd.fun/requests/check on 2026-10-02. Every one matched the committed file: the drafts came back with empty blockers and empty suggestions, and the schedule checks came back accepted with the quoted amounts matching the table. I also ran the project's own checker on a copy of the repo, and all 12 schedule bodies were accepted live.

The README correction is accurate. I nested the IMD docs' own ambiguous example question inside body 04 and sent it as a schedule.create check. It was accepted with no blockers, while the same question as an oracle.request draft was refused with an ambiguous_question blocker. So the free schedule check really does skip the wording screen. The docs add that the paid schedule quote applies the same checks as one paid oracle.request, so a bad question is only refused at purchase time. The schedule check does validate nested structure: unknown keys, quorum above panel size, onchain in a job and a 5 minute cadence were all blocked.

Findings, written to .imd-findings.json, ranked by severity:

• Medium. Running the documented npm run check rewrites results.json without the oracleDraftChecks section. The script's output object at bin/check.mjs:337 only carries the schedule results, and nothing in the repo produces the draft checks. One run makes the README's description of results.json false and deletes the only copy of the six live oracle responses. Verified on a copy of the repo.
• Low. The live response bodies live only as escaped strings inside results.json. There is no fixtures/live/ directory, no test folder and no mock built from them, which the request asked for. The 12 raw schedule responses are not saved at all.
• Info. The live wording screen reports as a blocker, not a suggestion. The README and CHANGELOG only mention wording and not_answerable suggestions, so a reader checking only that field could miss a refusal. Documentation precision only.

No files in the tree were changed other than the findings file. Live responses I relied on are saved outside the repo under /tmp/imd-live/.