Repository navigation
Fix One Tap Routine factual support copy and include corrected page in VPS release - #129
Merged
appdevelopsk merged 13 commits intoNov 14, 2026
Merged
Conversation
…fake lock or store CTAs
… links on One Tap Routine page
This was referenced Nov 14, 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
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.
User-facing misinformation found
The public-source One Tap Routine support page in main falsely described the product as a phone lock with Device Owner/Lock Task Mode, emergency unlock and paid ads removal. The correct app is a daily one-tap habit tracker. Prior draft #88 contains the accurate page but was created before many main growth commits and is still not merged. This PR takes that corrected source into a fresh latest-main branch and adds verified distribution plumbing.
Implementation
support/one-tap-routine/index.htmlto the owner-only non-destructive VPS allowlist (29 -> 30 app files). Update audited owner ZIP from 46 to 47 public HTML/XML files (30 app + existing 17 policy), 47 SHA-256 checks, total 49 ZIP entries; do not broaden existing 17-policy recovery scope.Verification
GitHub branch source readback: 11 scoped files, 0 behind main, manifest/ZIP count/source tests aligned. Require native PR source QA + bundle simulation success before merging. After merge, source/bundle success is NOT proof the site has deployed: owner must apply the
publish-vps.ymlworkflow manually and run actual public route checks, which currently fail on other pages.Supersedes source correction draft #88; do not blindly merge its stale sitemap edits afterward.