The build list check - proof, not promises

Every Workshop pack ships build-manifest.json: one row for each screen, feature, table, file store and outside key your app is meant to end up with. It is the only spec for your app.

When your app sends its progress report, we tick off every row. A row your app claims is finished reads built. A row that only appears in your product manual reads written down, but nothing says it works. Anything else reads not there yet.

One shared word is never enough to close a row, and if your app lists something as missing, that beats anything the manual claims.

Press the button and you get a prompt naming the exact rows, with how to prove each one. Paste it into your builder.

The prompt ends by telling your builder to update the manual and send a fresh report, so the next check happens on its own. You do not have to remember.

If the same rows come back missing three times, we stop handing you the same prompt and point you at the Repair Bay instead.

Press Check it now on Build monitor first. Without a report there is nothing to grade.

If the app was not built here, or the build record was lost, the card says so plainly rather than showing an empty tick list.