fix: a PERMIT2_TRANSFER_FROM before a permit keeps its amount from standing as the Amount figure (closes #655)

A PERMIT2_TRANSFER_FROM that runs before a PERMIT2_PERMIT of the same
token moves it under whatever allowance the router already had, so it
can move more than the permit's amount. The permit's amount still stood
as the Amount figure, which could then read lower than what leaves the
wallet.

decode() now counts such a transfer, into the router or anywhere else,
among the steps before the permit that took its token, so the permit no
longer stands: the Amount line gives the total the steps take, as with
no permit, and the permit gets its own lines. A transfer after the
permit, or of another token before it, still lets it stand; tests cover
both. README Transaction Decoding states the condition.

Model: opus-5-5

README.md

@@ -3226,36 +3226,41 @@ Currently supported:
   which it does only in the plain shape of Uniswap's own routes: it comes before
   the step that sets the input side, it is the only `PERMIT2_PERMIT` in the
   transaction and there is no `PERMIT2_PERMIT_BATCH`, its spender is the router,
-  the router may not let it fail, no step before it takes its token or a token
-  the decoder does not know, and the decoder reads every step after it in full.
-  Permit2 then lets the router take no more of the token than that amount, so
-  the permit covers every take of it. A later permit or batch may raise what
-  Permit2 lets the router take, and so may a step the decoder does not read in
-  full: a command the decoder does not read (listed at the end of this section),
-  a step whose input it cannot read, in whole or in part, and a step it fails
-  on. Every other `PERMIT2_PERMIT`, before the step that sets the input side or
-  after it, leaves `Token In` and the `Amount` line as they read with no permit:
-  a permit of 5,000 DAI to another address and then a V3 exact-in of 600 USDT
-  read `Swap USDT → USDC` with `Amount 600.0000 USDT`, and so do that exact-in
-  and then a permit of 5,000 DAI to the router. When a permit's amount stands
-  and the step that sets the input side spends a token other than the permit's,
-  or one the decoder does not know, that step's amount gets lines of its own,
-  unless it states no amount and the user pays it none of its input token. Each
-  take the total does not count gives three lines after the `Amount` line (after
-  `Token In` when there is none): one of a token other than `Token In`; one of
-  `Token In` after an amount that is not a quantity (a V4 open delta,
-  `ALREADY_PAID`, which keep their wording on the `Amount` line, or no stated
-  amount, as of a V4 exact-out step); and one whose amount the decoder does not
-  know. When the step that sets the input side states no amount, the user pays
-  it some of its input token, and there is no `Amount` line, that step gets them
-  too whenever another take's lines give a figure, or a `PERMIT2_TRANSFER_FROM`
-  of its token gives one, on the lines below or, into the router, on its
-  `Paid to` line, so that figure cannot read as all that leaves. When it states
-  no amount and the user pays it none of its input token, as when the router
-  pays it, that step takes none of that token from the user's wallet and never
-  gets them, with a permit or without. They come in step order, the step that
-  sets the input side first when it has them: `Moved from the sender`, its
-  amount, worded as the `Amount` line words one, or
+  the router may not let it fail, no step before it takes its token, a
+  `PERMIT2_TRANSFER_FROM` of it included, or a token the decoder does not know,
+  and the decoder reads every step after it in full. Permit2 then lets the
+  router take no more of the token than that amount, so the permit covers every
+  take of it. A step before the permit takes under whatever allowance the router
+  already had, so it may take more than the permit's amount, which would then
+  read lower than what leaves the user's wallet: a `PERMIT2_TRANSFER_FROM` of
+  2,000 USDT into the router, then a permit of 600 USDT to the router and a V3
+  exact-in of 2,000 USDT paid from the router, read `Amount 2000.0000 USDT`. A
+  later permit or batch may raise what Permit2 lets the router take, and so may
+  a step the decoder does not read in full: a command the decoder does not read
+  (listed at the end of this section), a step whose input it cannot read, in
+  whole or in part, and a step it fails on. Every other `PERMIT2_PERMIT`, before
+  the step that sets the input side or after it, leaves `Token In` and the
+  `Amount` line as they read with no permit: a permit of 5,000 DAI to another
+  address and then a V3 exact-in of 600 USDT read `Swap USDT → USDC` with
+  `Amount 600.0000 USDT`, and so do that exact-in and then a permit of 5,000 DAI
+  to the router. When a permit's amount stands and the step that sets the input
+  side spends a token other than the permit's, or one the decoder does not know,
+  that step's amount gets lines of its own, unless it states no amount and the
+  user pays it none of its input token. Each take the total does not count gives
+  three lines after the `Amount` line (after `Token In` when there is none): one
+  of a token other than `Token In`; one of `Token In` after an amount that is
+  not a quantity (a V4 open delta, `ALREADY_PAID`, which keep their wording on
+  the `Amount` line, or no stated amount, as of a V4 exact-out step); and one
+  whose amount the decoder does not know. When the step that sets the input side
+  states no amount, the user pays it some of its input token, and there is no
+  `Amount` line, that step gets them too whenever another take's lines give a
+  figure, or a `PERMIT2_TRANSFER_FROM` of its token gives one, on the lines
+  below or, into the router, on its `Paid to` line, so that figure cannot read
+  as all that leaves. When it states no amount and the user pays it none of its
+  input token, as when the router pays it, that step takes none of that token
+  from the user's wallet and never gets them, with a permit or without. They
+  come in step order, the step that sets the input side first when it has them:
+  `Moved from the sender`, its amount, worded as the `Amount` line words one, or
   `Unknown (could not be decoded)` when the decoder does not know it;
   `Token moved`, giving the token's address as the `Token In` line does; and
   `Moved to`, which reads `The swap step that spends it`. A token the decoder