Skip to content

Fix One Tap Routine factual support copy and include corrected page in VPS release - #129

Merged
appdevelopsk merged 13 commits into
mainfrom
fix/one-tap-habit-page-verified-release-20261114
Nov 14, 2026
Merged

appdevelopsk merged 13 commits into
mainfrom
fix/one-tap-habit-page-verified-release-20261114

Conversation

@appdevelopsk

Copy link
Copy Markdown
Owner

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

  • Replace outdated phone-lock SEO, OG, FAQ and premium promises with habit-tracker content, local-data backup privacy disclosure and truthful unverified-store-link status.
  • Add 3 native Node regression tests to guard against reintroduction of false features, fake store CTAs or unverified premium claims.
  • Publish it: add the fixed support/one-tap-routine/index.html to 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.
  • Extend actual public HTTP smoke with One Tap Routine title, product copy, privacy link and strict forbidden old phone-lock SEO checks; source/smoke regression covers this page.
  • Include source + test in PR and main QA triggers. Update the existing sitemap lastmod date to 2026-11-14.
  • Preserve 5 press locales, 2 AI debate guides, source-only ZIP safety, manual owner consent for VPS publish and no unverified Play listing.

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.yml workflow 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.

@appdevelopsk
appdevelopsk merged commit 713f375 into main Nov 14, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant