Reissue Invoice

Send an already-numbered document to SdI again (AP-033).

The route for the two ways a transmission ends badly: a scarto (SdI refused the document — it was never issued, so its number is still the right one) and a send the provider never answered. Both keep their number and their XML on purpose, and this re-transmits exactly those bytes; nothing is rebuilt, so a document that validated once cannot become a different one on the second attempt.

Status codes, all decided by the store's own refusals:

• 404 — no invoice of that id for this caller, unknown and somebody else's alike;
• 409 — the invoice is not in a state to re-send: a draft (issue it first) or a document SdI has accepted or is still answering. Two of them because the caller's next step differs, and the row is one they can read anyway, so neither message leaks anything;
• 500 — the stored document cannot be read back. The same server fault GET /xml reports, and for the same reason: those bytes are what would be sent;
• 502 — the transmission failed again. The invoice is back in error and this call can be repeated.

Carries the AP-099 write limiter, like every other mutation here: it makes an outbound call, even though (unlike issuing) it never spends a number.