I fixed both items. npm test passes (19 of 19), and the change is limited to the example, the type declarations, one test, one new fixture, and the README and CHANGELOG.

1. Safety: examples/viem-signer.mjs

• The example now calls pay(quote.order, signer, { execute }), where execute is true only when process.env.IMD_EXECUTE === "1". Otherwise it does the SDK's existing dry run: no signature, no payment.
• When IMD_EXECUTE=1 is set, it prints WARNING: IMD_EXECUTE=1 is set. Signing and submitting a real IMD payment for order <id>. before paying.
• The README signer section now says the example is a dry run by default and only pays with IMD_EXECUTE=1.
• I checked this with a throwaway copy of the example that used a fake client in place of the real one. With no variable set, it passed { execute: false }. With IMD_EXECUTE=true, it also passed { execute: false }, because only 1 counts. With IMD_EXECUTE=1, it printed the warning and then passed { execute: true }. I did not run the real example against the live API, so no payment was made.

2. Types: CheckResult in src/index.d.ts (and dist/, rebuilt by npm test)

• I confirmed the gap against the live API: POST https://api.imd.fun/requests/check for a 7-run schedule.create returns action, blockers, suggestions, unitAmount, runs, amount and terms, and no kind, plan, facts or judged.
• kind, plan, facts and judged are now optional. I added optional unitAmount: string, runs: number, amount: string and terms: string. Here terms is a plain string, unlike Quote.terms, which is an object.
• The live response (captured 2026-10-02) is saved as test/fixtures/live/check-schedule-create.json. The drift test now checks that it has every required CheckResult field plus the four new ones, that runs is 7, and that amount equals unitAmount × 7 (0.5 IMD × 7 = 3.5 IMD).
• With the old declaration, the drift test fails with check schedule.create fixture has required kind. With the new one it passes.
• The saved response contains an ambiguous_question blocker for my test question. That does not affect the fields checked here.
• I also re-ran the live job.open check: it still returns kind, plan, facts and judged, so the existing check.json fixture still matches.

Unchanged: payment, retry and cap logic, src/index.js, the CLI, and the existing tests. The "experimental" warning stays in the README, CHANGELOG and CLI. No client method returns any, and the existing test that rejects Promise<any> still passes. The CHANGELOG has a new entry listing both items and what changed.

Not run: the TypeScript compiler, which isn't installed here (the project has no TypeScript dependency). Slither and Aderyn don't apply, since no Solidity changed.

Noticed but left alone: in test/live-schema-drift.test.mjs, the pattern meant to mark field?: as optional actually looks for a backslash, not a ?. Optional fields are still excluded because they don't match the pattern at all, so the result is correct, just not for the reason the code suggests.

The changes are not committed.

Audit complete. The work is correct on both items. I found one low-severity test-coverage gap and no defects in the implementation. Findings are written to .imd-findings.json; no other file in the tree changed.

What I verified

• Example dry run against a mock. I ran examples/viem-signer.mjs unmodified from a sandbox outside the repo, with viem installed and every call to api.imd.fun redirected to a local mock that logged each request. With no IMD_EXECUTE set, the mock saw only the free quote and the free challenge POST. No request carried a payment signature header, no spend ledger and no saved authorization file were created, and the output was the dry-run object. With IMD_EXECUTE=1 the warning printed before the signed submit, and the ledger and authorization file appeared. With IMD_EXECUTE=true the run stayed a dry run, which matches the spec's wording of exactly 1.
• Schedule check types against the live API. The free POST to /requests/check today with a schedule.create input and runs 7 returned exactly the keys action, blockers, suggestions, unitAmount, runs, amount and terms, with no kind, plan, facts or judged. That matches the saved fixture and the optional fields in the declaration. A job.open check returned the old shape with kind, plan, facts and judged. The declarations type-check under strict TypeScript against a consumer that reads the new optional fields.
• Regressions and labels. All 19 Node tests and 3 Foundry tests pass. dist/ is byte-identical to src/. The experimental label remains in README, CHANGELOG and the site. The CHANGELOG entry lists both items. Reverting kind to required makes the drift test fail as intended.

Finding (low, test coverage)

• The drift test checks that the fixture has unitAmount, runs, amount and terms using a literal list, but never reads those names from the declaration. Deleting all four optional fields from CheckResult in src/index.d.ts leaves the drift test passing 2 of 2. The implementation itself is correct, so this only weakens the guarantee the test claims to give.

Observation, not a defect

• The dry-run example still creates a real order on the live API through the free quote and challenge calls. That is the documented pre-existing flow and involves no payment, and the README says so.