Why there's a check before you publish

Most build failures aren't surprises: a setting nobody filled in, a missing file, a dependency that was never pinned.

The build runs for minutes, fails, and leaves a long log with one line that matters.

Before you publish, "Is it ready?" reads the project and lists what's missing in plain sentences. You can fix it, or hand the list to your AI.

It can't promise a build will pass. Some problems only appear when the code compiles, and those still show up after publishing. That's also why the check is optional: skip it whenever you like.