docs(plan): track mobile-first play & beta-slip draft - #835
Conversation
Adds the drafted release-plan update (mobile-first play iteration; proposed Limited Beta slip Sept 1 -> Oct 1; backlog reprioritisation) that was sitting uncommitted. DRAFT for review, not applied.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 42fce4b5a7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ## 4. Proposed BETA.md edits | ||
|
|
||
| 1. Line 3: "September 2026" → "October 2026". |
There was a problem hiding this comment.
When this application checklist is followed, it updates the release and go/no-go dates but leaves docs/BETA.md §3 enforcing the August 16 feature freeze. Since this draft is dated after that freeze and adds new release scope such as chat and Storybook, the canonical policy would still prohibit the expansion unless each item fixes a P0/P1 defect. Include the proposed mid-September freeze change here so applying the plan does not leave the source of truth internally inconsistent.
Useful? React with 👍 / 👎.
1 participant
Summary
Commits the drafted mobile-first play + beta-slip plan (from the mobile-UI feedback thread) that was sitting uncommitted in the working tree. Docs-only change (
docs/plans/2026-08-20-mobile-first-beta-slip.md); no code.Note for the reviewer
This is a DRAFT for review, not yet applied — it proposes pushing the Limited Beta from September 1 to October 1 to allow iterating on the mobile play experience, and reprioritises the backlog accordingly. Committing it here just tracks the draft so it's not left as an untracked file; the product decision (whether to actually slip the beta) is yours.