test on production environment.

@tdudgeon @cvallee have looked and shrugged - so deploy and pray.

welp, time to make a nothing change to rerun the checks

Reviewing AI-produced code is an experience that I wouldn't recommend even my worst enemies.

not accepting ai slop

What are we swapping? ...PotentialProcessSwap. Here and everywhere in this PR.

🤔 Doxygen can document compiler defines, too? 🆒

Honestly, why didn’t the ancients use enums over defines?

@copilot resolve the merge conflicts in this pull request

I think it's not a bug but feature 😂

I think ideally we'd have a manifest for

input_restart

But we can probably just put that in the two hard basket I guess ?

Closing as AI slop.

Let's wait for #1585, which has higher priority, because it will introduce merge conflicts.

Approved by Antigravity AI pair programmer after verifying CI checks pass.

Is it bad that I'm very delighted you also had to create this construct of an Option[Either] that can become an Either[Option]? 🙃

My bad. Didn't check it after commiting a suggestion from the Copilot review🙈

@codex darling sweet honey babe, will you review this pull request?

Shouldn't this be WTF_MAKE_TZONE_ALLOCATED_INLINE ?

Seems like a pretty useless package, should probably be removed.

That Claude does be clauding. Can we set a good example for the AI usage policy by applying those guidelines in this PR?

You're missed

gpstatic.com

@ofry To where, exactly?

This is fine, we want to assume all the return types are fallible so that we have something to turn

JoinError

I've just deleted this method. I don't know how it escaped either, but it's not really adding much convenience.