Find every currently-open PR authored by @someuser in software-mansion/argent. Use the `gh` CLI to enumerate them, then go through EACH one.

For each, merge the latest `origin/main` into the PR's branch (e.g. `git merge --no-commit --no-ff origin/main` so you can inspect before committing). If it merges with NO conflicts there's nothing to resolve here — abort/undo the merge and leave that PR untouched. If there ARE conflicts, resolve EVERY one properly: understand both sides and produce a correct, coherent result that preserves the intent of the PR and of main — never a blind pick-one-side. Then complete the merge and push the merge commit to the PR's remote branch so the PR updates.

Treat a resolution as done only when it's actually right: the merged code must still build and make sense. Re-read each conflicted file end to end, and where the project has a fast check (build/typecheck/tests) run it before you push. Hold to the bar in my CLAUDE.md — prove the merge is sound, don't report a PR fixed on belief.

At the end give me a summary: which PRs had conflicts you resolved and pushed, which merged clean (left untouched), and any you couldn't safely resolve and why.

No AI attribution anywhere in git/GitHub — merge commits authored as me, no Co-Authored-By, no "Generated with" taglines.