What's Fixed
This release focuses on making workflow expectations behave the way you may expect, especially when you intentionally check for non‑2xx responses. Steps that specify expect.status or expect.statuscode no longer auto‑fail on 4xx/5xx. Instead, they pass or fail based on the expectation itself. Resterm also preserve the original error message when a request fails without a response, so workflow summaries are clearer and less generic.
I also tightened validation for workflow expectations at parse time. Empty expect.status /expect.statuscode values or non‑numeric expect.statuscode values, are now flagged immediately and the invalid expectation is dropped rather than silently masking status failures. There's a small runtime guard as well to keep the error message explicit if an empty status expectation "sneaks" in.
Highlights:
- Expected 4xx/5xx outcomes are now allowed when explicitly declared in workflow steps.
- Parse‑time validation prevents empty/invalid expectations from weakening workflow checks.
- Error messaging for request failures is preserved and more consistent.