Different checks prove different things
Capability Studio saves each check with the exact action and app version. A stronger check can add confidence later, but it does not change what the earlier check proved.
Common check results
- Designed or generated: a person can review the action details, preview, or draft file.
- Code checked: the action definitions and links to working code were inspected.
- Tests passed: focused tests passed in a named setup.
- Build passed: the intended app target compiled successfully.
- Real feature checked: someone tried the installed Shortcuts, Siri, or other experience.
- Seen in production: records from the released version show what happened when it ran.
Be precise before release
A general code scan cannot prove that a file is in the right app target, that the action works when run, or that Siri can find it. Keep unsupported and untested states visible instead of turning them into a green checkmark.