docs: update mobile app release messaging#98843
Merged
Merged
Conversation
openclaw-barnacle
Bot
added
docs
Contributor
|
ClawSweeper status: review started. I am starting a fresh review of this pull request: docs: update mobile app release messaging This is item 1/1 in the current shard. Shard 0/1. This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking. Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted. |
joshavant
force-pushed
the
docs/mobile-apps-official-release-messaging
branch
from
July 2, 2026 02:10
0fc4076 to
2dec98a
Compare
vincentkoc
added a commit
that referenced
this pull request
Jul 2, 2026
* origin/main: docs: update mobile app release messaging (#98843)
gitchrisqueen
added a commit
to gitchrisqueen/openclaw
that referenced
this pull request
Jul 2, 2026
The maturity summary fixture reads the live taxonomy.yaml and qa/maturity-scores.yaml, which were updated on main by openclaw#98843 after this assertion was written, shifting the aggregate score from 67% to 68%. Sync the hardcoded expectation to the current generated value so the tooling shard passes. No production behavior change.
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 2, 2026
This was referenced Jul 2, 2026
chenyangjun-xy
pushed a commit
to chenyangjun-xy/openclaw
that referenced
this pull request
Jul 3, 2026
This was referenced Jul 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Problem This Solves
Resolves a problem where the iOS and Android apps were still described in docs, release metadata, showcase copy, and maturity projections with pre-release language after their public release.
Why This Change Was Made
The mobile app messaging now treats iOS and Android as regular released apps across the app READMEs, release/versioning docs, fastlane metadata, gateway configuration docs, showcase docs, and maturity taxonomy. The old TestFlight showcase image was removed instead of reusing a misleading asset that did not show an app workflow.
User Impact
Users and reviewers now see the mobile apps presented as official public apps for App Store and Google Play distribution. The maturity pages and score source data also classify the iOS and Android app surfaces as M4 Stable instead of preserving stale pre-release positioning.
Evidence
pnpm docs:listpnpm maturity:checkpnpm docs:check-mdxpnpm docs:check-links(checked_internal_links=5624,broken_links=0)git diff --checkrgoverapps,docs,taxonomy.yaml,qa/maturity-scores.yaml, andsrc/config/schema.help.tsfound no matches..agents/skills/autoreview/scripts/autoreview --mode localpassed with no accepted/actionable findings.