Review & publishing

1. Build. The platform validates the manifest (schema, known permissions, SDK range >=0.1.0 <0.2.0, runtime 1.0.0), checks imports against the allowlist and bundles your code. The bundle must be at most 2 MB. Warnings flag code the sandbox will block (network APIs, eval, browser storage, window.parent).
2. Submit. Only a successful build can be submitted, and your store listing needs at least one mobile screenshot. While it waits for review you can cancel the review; the version goes back to ready.
3. Review. Lexcetha inspects the source, the requested permissions and the build log, then approves or rejects it with notes. You see the result in the Release tab.
4. Publish. You decide when an approved version goes live: publish it from the Release tab. It becomes the active one in every workspace's catalog. Bundles are immutable and verified by SHA-256 every time they load.
5. Update. Bump version and build again. A published version can never be overwritten.
6. Roll back. If a release breaks, Lexcetha can re-activate an earlier approved version. The broken one is disabled and its open sessions end.

What reviewers look for

• Permissions match what the code actually uses.
• The name, icon and description say plainly what it does.
• No attempts to escape the sandbox or to collect personal data.
• It works in Preview.