Public-apps and UI-apps working docs (docs.md, RELEASE-CHECKLIST.md, QA-TESTCASES.md)

[piyushsarin-sib]

Summary

Collects the working docs for the two pre-GA features — public app distribution (BEX-405) and UI apps (BEX-290) — on a branch off main, so they are tracked independently of the feature branch they were written on. Each is removed from features_set_public_cli in a companion commit.

Three files, three jobs:

docs.md — the open-questions log

• Part 1 — release copy for the two features, written as changeset text and held until GA rather than published now. A public CHANGELOG naming a command the published build eliminates would send readers to an unknown command.
• Part 2 — everything still open or undecided: unresolved wire contracts, follow-ups deliberately not done, and items awaiting confirmation against the platform.

RELEASE-CHECKLIST.md — the GA runbook

The ordered, mechanical steps for the day each feature ships: ## Before public-apps GA and ## Before UI-apps GA. Both sections are durable and stay until their feature ships; each carries its own final step saying when it may go. The feature branch's ## Per-branch verification section did not come with them — that is branch scratch and stays there.

The split against docs.md is what to do on the day versus what is still unknown. An item moves from docs.md to here when it turns into a release step.

QA-TESTCASES.md — the pre-GA manual test plan

Suite 2 (public create), TC-5.13–5.16 (upload under review states), suite 6 (status), suite 7 (withdraw), TC-10.2/10.3 (the build-time gate as it shows up in --help), suite 12 (UI apps / action links) and TC-13.4 (submit) — plus the results recorded for each in the 2026-08-13 sweep. The private-app half of the plan stays on the feature branch.

Every case here needs a preview build (PREVIEW=1 yarn link:dev); the preamble says so and explains why no account or env var substitutes for it.

Notes

• Suite and case numbers are unchanged, so they are sparse on both sides. Renumbering would break every reference to a case in commit messages, PRs and docs.md; each file's preamble says to read a gap as "that case lives on the other side".
• Two claims in suite 12's preamble were corrected rather than carried over verbatim, both contradicted by evidence already in the same file: it said nothing on the platform stores the ui_app snapshot (TC-12.5(a)'s own result shows create persists it), and it described BEX-361 as unshipped.
• Merge-order note: main has none of these three files, and features_set_public_cli carries its own reduced RELEASE-CHECKLIST.md and QA-TESTCASES.md. Whichever branch merges second will hit an add/add conflict on those two paths — resolve by keeping both sides' content under its own file, not by picking one.
• Docs only — no source, test or build changes, so no changeset.
• None of the three is in package.json files:, so none ships in the npm tarball.
• Content reviewed against the public-repo rules in CLAUDE.md: no keys, credentials, internal hostnames, account identifiers, or Jira ticket content — tickets are referenced by key only.

🤖 Generated with Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud