Skip to content

P0: verify appdevelopsk.com growth changes live and GA4 before acquisition rollout #51

Open

Description

@appdevelopsk

Why this remains open

2026-11-05 public read-only check of https://appdevelopsk.com/ confirms the previously merged count-neutral hero and featured order Debate Me → Tappitsu Battle → FutureMe are live. However, the just-merged related-app links from PR #50 have not yet been confirmed on public /support/debate-me/ (the checked copy lacked the new section at the time of the read). A successful GitHub merge does not prove full live propagation, browser functionality, or any install increase.

Already in main

Operator verification — no GitHub Actions

  • Open the three public pages in a fresh private browser: /support/debate-me/, /support/tappitsu-battle/, /support/future-me/. Verify a visible, usable two-link related-app section with no self-links, mobile layout and keyboard navigation.
  • Confirm each new destination resolves successfully. Check English, Japanese, Arabic RTL and at least one other locale; then audit all 17 translation headings. No invented store availability.
  • Check browser devtools console and GA4 DebugView for one related_app_click per click with only source_app, target_app, placement; one existing download_click per real Play click with app_slug and placement. Confirm that outbound store clicks are not counted as installed users.
  • Confirm homepage title, catalog descriptions, JSON-LD and live sitemap entries reflect current source. Google search cache may be older than live HTML.
  • Confirm how appdevelopsk.com is deployed and preserve deploy logs/commit SHA and rollback plan. If live pages lag main, do an authorized manual site publish; do not assume GitHub merge is a deploy.
  • Compare GA4 7-day new users, landing-to-store click rate, store first-time acquisitions and matured D1/D7 by actual release date/country. Separate prior overall new-user trend from causal attribution.
  • Verify authentic app-store screenshots, localized listings and real release version before new ASO tests. User handles App Store Connect/Play Console and mobile signing.

No GitHub Actions, no store publication, paid placement or fabricated campaign results. Close only after public/browser analytics evidence is attached.

Activity

  1. appdevelopsk commented on Nov 5, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-05 update: source-side acquisition PR #55 was merged (catalog detail links and click attribution). Release verification script PR #56 was merged at fc32f07. To validate on a Mac without GitHub Actions:

    python3 -m unittest discover -s scripts -p 'test_growth_live.py' -v
    python3 scripts/check_growth_live.py > /tmp/appdevelopsk-growth-live.json

    This performs a read-only HTTP check of homepage, 92-card catalog, 3 priority support pages, robots and sitemap. Nonzero exit is a deployment/release gate failure, not evidence of traffic decline. Tests were added but not executed in this connector session. After live source passes, separately verify JavaScript and GA4 DebugView in browser, Play Console acquisition, store listings and mobile/RTL layout. Do not close until evidence of production publication and event delivery is attached.

  2. appdevelopsk commented on Nov 5, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-05 additional completion: catalog app-detail links merged via #55 (549863f), smoke runner and six offline fixtures merged via #56 (fc32f07), and stale-live-catalog regression merged via #57 (0db1190). The Python suite now contains seven test functions, but has not been executed in this environment.

    Public search retrieval today still returned old catalog copy ('92 free apps on Google Play') and no related-app section on one or more individual support pages; caching/deployment status requires verification. Run the source QA and live smoke locally:

    python3 -m unittest discover -s scripts -p 'test_growth_live.py' -v
    python3 scripts/check_growth_live.py > /tmp/growth-live.json

    Then check live browser/GA4 DebugView separately, keeping this issue open until evidence is attached.

  3. appdevelopsk commented on Nov 5, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-05 21:19 JST follow-up: merged PR #58 (90ae436ab747044b3ea538c0e4e4521448e8cbb8) strengthening the read-only live smoke: now checks catalog has 92 distinct Google Play Android package IDs, and verifies exact package-ID parity/count/order against JSON-LD ItemList. Added two more offline regression cases, for nine test definitions. Source inspection of current /apps found 92 unique package IDs and expected UTM/referrer parameters. The regex/JSON-LD matching logic was exercised on synthetic good/duplicate fixtures; complete Python 9-test suite was not executed, nor was public HTTP smoke confirmed. Web retrieval today still produced a version of /apps with no new detailed-app section, and a version of the Tappitsu support page without its new hero CTA, so production cache/version verification remains a P0 blocking gate. No GitHub Actions or store submissions. Run python3 -m unittest discover -s scripts -p 'test_growth_live.py' -v and python3 scripts/check_growth_live.py, then verify the browser UI and GA4 DebugView, saving release SHA/country/time/window evidence.

  4. appdevelopsk commented on Nov 5, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-05 21:19 JST verification correction: The nine offline Python tests from merged PR #58 were executed successfully (9/9) in the ChatGPT local Python environment (not GitHub Actions). Both local file hashes match the exact blobs fetched from GitHub main: scripts/check_growth_live.py = 3515d64efa1c716fd29cd6bff8c5190d9b0b4ae4, scripts/test_growth_live.py = df41efc8b34760de1a0e0a4ad9f4da89567d2229. Tests cover baseline, missing page, missing related link, disallowed icon crawl, stale homepage/copy, duplicate Android package ID, schema mismatch, count mismatch. Actual public HTTP smoke could not be executed in this environment due to DNS/network resolution failure. Browser execution, deployment provenance, GA4 DebugView and Play Console measurements remain open. No GitHub Actions run.

  5. appdevelopsk commented on Nov 5, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-05 JST, acquisition closure evidence:

    • PR test(growth): validate all catalog Play packages and JSON-LD consistency #58 confirmed merged; exact Github blob hashes match the local smoke/test files: 3515d64efa1c716fd29cd6bff8c5190d9b0b4ae4 and df41efc8b34760de1a0e0a4ad9f4da89567d2229. 9/9 offline Python tests passed. Does not establish live deployment.
    • Public read-only retrieval: homepage count-neutral and featured priority order visible. Catalog page shows count-neutral heading, but the new detail spotlight from feat(growth): link catalog visitors to detailed app pages with measurable clicks #55 was absent in retrieved content. Support and robots fetch could not be inspected via this retrieval. This is incomplete evidence, not proof of a failed deployment.
    • app-infra PR #200 merged as 2918ca2f731373135be5c8c595014a0e95322215 to reject nonfinite acquisition data and invalid retention cohorts. 13 locally reconstructed equivalent cases passed, but full exact GitHub source suite was not rerun.
    • Latest snapshot 2026-11-05 07:14 JST (2026-10-29..11-04): Debate Me 112 new/162 active, Tappitsu Battle 75/78, FutureMe 41/47, Twotaku 20/23. GA4 app-level measurements are not verified unique Play installs.
    • Open gates: run live smoke, browser desktop/mobile/RTL, actual GA4 DebugView for outbound and related clicks, Play Console first-time installers and exact version/date. No GitHub Actions.
  6. appdevelopsk commented on Nov 5, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-06 JST acquisition update: PR #59 merged (0990352), extending related-app referral web flow from three to five apps: Debate Me, Tappitsu Battle, FutureMe, Dotchi (repo slug twotaku), Instant Judge.

    Code/source QA: 5/5 pages have 17 localized related-app headings, exactly two distinct non-self internal links, GA4 related_app_click/download_click hooks and both hero/detail CTA positions. /apps now has five detail spotlight links and still has exactly 92 catalog cards. Live smoke scripts expanded to five app pages and now contain 11 test methods; no Python test run claimed for this new commit. Sitemap retains 319 entries and updated lastmod for modified /apps, /support/twotaku/ and /support/instant-judge/.

    Read-only public retrieval on 2026-11-06: /apps returned a result crawled today showing updated count-neutral description, but did not show the already merged app-detail spotlight; /support/instant-judge/ result was crawled last week and lacks related-app section; /support/twotaku/ fetch was inaccessible. This is incomplete/mixed-age crawler evidence, not a reliable deploy-status verdict. Execute the repository's read-only Python HTTP smoke against live and verify browser JS + GA4 DebugView before closing.

    Outstanding: authenticated deployment/commit-to-live confirmation, responsive/RTL/browser checks, Play Console first-time installer and conversion evidence, and ASO/short-video publishing. No GitHub Actions used.

  7. appdevelopsk commented on Nov 5, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-06: merged acquisition validation PR #60 at cdb54d0.

    Fixed a live smoke false-negative: previously the presence of data-related-app / data-detail-app alone could pass even when href led to an invalid page. The checker now validates actual destination URL equals /support/{slug}/ and five distinct catalog-detail links. Added two corrupted-URL regression cases, bringing the suite from 11 to 13 tests. Source regex checked on actual 5 catalog links and Twotaku related links; the exact new Python unittest suite was NOT executed.

    2026-11-06 read-only public retrieval: homepage showed the corrected priority feature order and count-neutral messaging; /apps result did not expose the new five-app detail spotlight. Instant Judge result was crawled the prior week; Twotaku and robots.txt could not be fetched by this retrieval. Mixed-age and failed fetch results are INSUFFICIENT to say a deploy failed; verify with authenticated publish evidence or run the included HTTP smoke on a networked machine.

    Owner release gates remain open: exact main test run, HTTP smoke against live, mobile/RTL and browser devtools validation, GA4 DebugView (one related_app_click/download_click per real click), Play Console actual store visitors/first-time installers, ASO screenshot tests, creative publishing. Do NOT use GitHub Actions.

  8. appdevelopsk commented on Nov 5, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-06: PR #61 merged into main as f5bc398. The live smoke previously required exactly 92 store cards. It now requires at least 92 as a non-regression baseline, enforces unique Play package IDs and an exact match with JSON-LD ItemList. This permits genuine 93+ app releases while rejecting partial catalog/schema updates.

    Test proof: Python unittest executed locally on the exact PR file contents (Git blob hashes 36c32dd9491cd90a10e6962f81672a72acaa1b73 and 69b448fceb9e029e5cf7d39c2785ae47535c7867), 15 passed / 0 failures. GitHub Actions not used.

    Public read-only retrieval 2026-11-06: homepage shows corrected featured app order, catalog response is missing the 5-app detail spotlight, Instant Judge response lacks related app section; Twotaku and robots.txt could not be fetched by that source. These retrieval differences are not sufficient to determine the exact publish SHA, because source timestamps/crawling and deployment may differ.

    Next owner gate: deployment commit SHA/URL verification and read-only live smoke on network-enabled Mac, then browser mobile/RTL, GA4 DebugView and Play Console first-time install conversion. No store publishing or SNS automation was attempted.

  9. appdevelopsk commented on Nov 6, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-06 SEO release update: PR #62 merged to main at 478705a.

    Added factual SoftwareApplication JSON-LD to /support/instant-judge/ based on existing Android Play package com.instantjudge.instant_judge; no invented downloads or ratings.

    Extended source/HTTP smoke for all five priority support pages: canonical URL must exactly match the public page, disallow unintended noindex, and require parseable relevant JSON-LD referencing Android. Verified canonical and structured-data conditions in the five GitHub HTML source files. 18/18 offline Python tests executed successfully on exact Git blob hashes ca1be0c04410d756417f8e988e0c0dea99de58a8 and fac63f2a7733620f1541bb68d5ec8e3c6714c28b.

    Public status remains OPEN: external search result for /apps on 2026-11-06 still showed no catalog spotlight in parsed response, and support/robots could not be fetched reliably. This does not prove nondeployment; record actual deployment commit hash, run authenticated network live smoke and browser tests before closing.

    No GitHub Actions, no store-listing edits, no site deploy claimed and no installation lift claimed.

  10. appdevelopsk commented on Nov 6, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-06 latest acquisition analytics fix: PR #63 merged at 3611409.

    Found inaccurate GA4 semantics in homepage source: clicking an app card emitted app_view, although no app-detail page view had yet been confirmed. Changed to app_detail_click with app_slug and placement=homepage_card. GA4 page_view remains separate; this is a deliberate change in the event time series (historical app_view events were actually clicks).

    Live smoke now asserts homepage click event is properly named; two regression cases added. Exact GitHub blob SHA verified in local container, Python 20/20 tests PASS, 0 failures: checker 4c5b6db510bd54025a1628a3b418796e6dd314dc; tests a28fb4b215817adbf8aff968058c1c24b1b2fef5. GitHub Actions not used.

    Live source verification remains BLOCKED/UNVERIFIED: public crawler fetched /apps today without the five-app spotlight, and Instant Judge today without related-app section. Crawled result is not the same as an authenticated deployment SHA or full live browser. Need deployment settings/logs, read-only HTTP smoke on networked Mac, JS event validation in GA4 DebugView, Play Console first-time-installer and store CVR.

  11. appdevelopsk commented on Nov 6, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-06 growth release blocker and fix: PR #64 merged as 0361f7d.

    All seven entry pages (/, /apps, and /support/ for debate-me, tappitsu-battle, future-me, twotaku, instant-judge) now contain identical <meta name="sk-growth-release" content="growth-20261106-wave2"> in GitHub main. Source read-only smoke now requires that exact marker in each page, so it fails if some pages still serve the old/cached release. This marker is a version label, not a Git SHA.

    Local unittest run 22/22 passed. Blob hashes identical to GitHub PR source: checker d55acbe1435ba0aa9549da1a218952a9913c33af and tests fa71b51c97ac651ed12bdd46c787b6d77939587c. Repaired catalog expansion fixture to preserve new metadata.

    Independent live smoke against appdevelopsk.com attempted from container; failed due to DNS/network restrictions, not application response. Public read-only crawler responses of /apps and Instant Judge still did not show prior new sections; these are not authoritative verification of latest deployment.

    Owner release gate: publish main code, inspect page source for growth-20261106-wave2 on all 7 URLs, execute python3 scripts/check_growth_live.py from connected Mac, verify 22 offline tests + actual browser clicks and GA4 DebugView, then compare Play first-time installers. Keep issue open until publication and behavior evidenced; no GitHub Actions.

  12. appdevelopsk commented on Nov 6, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-06 11:22 JST growth QA update: PR #65 was squash merged into main at e069944.

    The read-only growth smoke now rejects mismatched Play Store package IDs across hero CTA, details CTA and structured data on each of the five priority app landing pages. Checked all five current GitHub HTML pages (5/5 package IDs agree). Three new regression methods bring the test count to 25.

    Proof: Python unittest 25/25 PASSED on local code with exact matching GitHub branch blob SHA: scripts/check_growth_live.py = 24822797f8e5719be84114214bba063f707d48f7, scripts/test_growth_live.py = 267fba433d987508772859518be9510a57d99496. GitHub Actions were NOT used.

    Public fetch via web on 2026-11-06 still exposed older catalog content without the five detailed-app links and an older Instant Judge page without related apps. This indicates a source-versus-public-content discrepancy in fetched results, but does not prove deployment failure (cache/crawl timing possible). robots.txt could not be fetched from this source. Open gate: authenticated deployment commit/version verification on all seven pages and live HTTP smoke, responsive browser checks, GA4 DebugView outbound-click actual delivery, Google Play Console install conversions and ASO tests.

    Note: growth release meta value is a manual milestone marker, not a cryptographic content hash; source/content tests remain necessary to validate specific fixes.

  13. appdevelopsk commented on Nov 6, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-06 JST: PR #66 merged as 1a205b8. Added a real zero-result recovery control to /apps: clears search, resets category to All apps, restores all cards, focuses search, and tracks only non-PII catalog_search_reset. Preserved 92 store cards/5 spotlight links.

    Locally ran 27/27 Python unittest cases successfully on exact GitHub branch blob contents: checker a82647843fab435be068cf0ad0d8f1ffedae9abb, tests 99de2cb819f621b1af72efc6ca8de286adfb634e. No GitHub Actions.

    Today's public read-only web fetch of https://appdevelopsk.com/apps still returned the older 'No matches. Try another word or choose All apps' empty state, and did not expose the already merged five-app spotlight. This does not certify deployment failure, because index/cache refresh and publication timestamps are unknown. twotaku support and robots could not be fetched by web source.

    NEXT REQUIRED: deploy latest main through owner-controlled publishing and run Python HTTP smoke, compare all seven <meta name=sk-growth-release> markers, then verify dynamic reset behavior in browser and GA4 DebugView. Measure actual Play Console store listing views and first-time installers; site-to-Play clicks are NOT installs. Keep this issue open until production evidence attached.

  14. appdevelopsk commented on Nov 6, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-06: PR #67 merged at 6e6079b.

    Catalog search previously searched only visible app-card text, so searches for internal/former slugs such as twotaku (public app name Dotchi) could miss existing apps. Now the search corpus also includes image-derived stable slug and its hyphen-separated alias, without sending raw search terms to analytics. Preserved 92 Play cards, five app detail links, categories, and privacy-safe existing measurement.

    Python regression: 29/29 PASSED locally on exact GitHub branch blob hashes check_growth_live.py 48f3e2539b781534064f54d10a548562c072445a and test_growth_live.py 3eedecc5c2c3e0919a6c6c92c77fbea05a52c081. No GitHub Actions.

    Read-only public retrieval of https://appdevelopsk.com/apps on 2026-11-06 still showed older catalog HTML in its parsed response: no five-app detail spotlight or empty-state reset, despite both in latest main. Direct support/twotaku and robots were inaccessible to the retrieval. Treat live as UNVERIFIED, not proven failed deployment. Run smoke against user-controlled live origin from a network-enabled Mac, inspect deployment configuration/caches, GA4 DebugView and Play Console actual installs. Closing this issue requires production evidence.

  15. appdevelopsk commented on Nov 6, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-06 19:33 JST: PR #68 merged as 57a9aa8.

    Corrected misleading GA4 catalog_search_used analytics: previously triggered immediately on the first typed character, giving unfinished query/result counts. The app catalog still filters instantly on keystrokes, but now emits search_used only on Enter or blur, once per normalized query, without transmitting raw user search strings. Explicit empty-search reset clears the reporting guard. Note a measurement-definition break: pre/post-release event totals are not directly comparable.

    Proof: 32/32 local Python unittest cases passed against exact GitHub main blob contents: scripts/check_growth_live.py=71a9d2926f2378926b645466c95d5d0b63317bed; scripts/test_growth_live.py=89205a7df44b38d03c9a3883b10fcf5720fb5b01. Three negative regression cases added. Existing 92 catalog store links and 5 app-detail links preserved. GitHub Actions unused.

    Latest public web retrieval of /apps (2026-11-06) still showed older empty-state and no five-app detail spotlight, while repo main has updated code. May reflect deployment lag/caching/tool retrieval, not an authenticated deploy verdict. Actual live source/JS/DebugView/Play Console conversions remain owner verification gates; do not mark published or claim acquisition lift.

  16. 31 remaining items

  17. appdevelopsk commented on Nov 13, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-13 22:35 JST — owner-deliverable release ZIP produced and verified, not deployed.

    • Merged PR #123, main f15e07fec4bd864b034787e6f7aea8c19be908c7.
    • GitHub's public hosted runner successfully executed workflow #43436368141: existing press/preflight + real temp rsync staging + 5 ZIP safety tests and archive creation all green. 14-day Actions artifact appsite-vps-source-f15e07fec4bd864b034787e6f7aea8c19be908c7 (artifact ID 14044061372).
    • The resulting nested ZIP was downloaded into the chat and independently inspected: 44 exact public site documents (27 app/discovery + 17 policy), 5 press routes, SHA256SUMS.txt, DEPLOY_README.txt, 46 ZIP entries total. All 44 SHA256 content digests verified; ZIP CRC passed. No repo-private files or remote commands in payload.
    • Existing authorized publish to VPS owner-only main → dry-run → mode=apply workflow remains preferred. Portable archive is the offline alternative if the special self-hosted appsite-deploy runner is unavailable. Owner can extract, verify SHA256SUMS.txt (macOS: shasum -a 256 -c SHA256SUMS.txt) and carefully rsync only extracted site/ contents to verified /var/www/html/, with no --delete.
    • On actual public VPS, last directly verified state remained 5/5 press URLs HTTP 404 and the five-language catalog absent. This ZIP is NOT a successful deploy and does not cure the 404 until uploaded to the VPS; rerun live smoke afterwards.
    • No VPS host, DNS, SNS, store, indexing or paid campaigns were modified by this turn.

    The issue remains open until live HTTP proof. Source archive downloadable from the action artifact under the linked run. User-facing direct file also available in this conversation.

  18. appdevelopsk commented on Nov 13, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-13 — GSC real-search acquisition baseline and release verification

    Connected Search Console property sc-domain:appdevelopsk.com, finalized 2026-11-08..10 (3 days, no prior-period comparison):

    Landing page Impressions Clicks Avg position
    /support/debate-me/ 97 0 6.43
    /support/face-reaction-battle/ 20 2 6.3
    /support/brain-burst/ 17 0 7.82
    /support/key-clash/ 8 0 6.63

    For the query debate me alone: 78 impressions, 0 clicks, average position 6.05. These samples predate the November 13 source-main snippet edits documented in README; do not rewrite the same snippets or attribute changes to them. The source support page already has first-party canonical, SoftwareApplication schema and Google Play hero/details CTAs.

    Verification blocker: public-domain retrieval from this session was unavailable (web fetch cache misses and DNS restrictions in independent runtime). This is not evidence of a website outage or stale production. HYPD GA4 account list reports connected properties but no selected property; GA4 first-time active users and actual store acquisitions remain unverified.

    Action gates already provided in repository: node --test scripts/test_support_serp_snippets_20261113.cjs; python3 -m unittest discover -s scripts -p 'test_support_serp_live.py' -v; python3 scripts/check_support_serp_live.py > support-serp-live.json; confirm serving host SHA, store CTR and real Play Console first-time installers before closure. After publishing, compare like-for-like 7/28-day qualified organic clicks and activated users; do not treat impressions, downloads clicks or bots as active users.

  19. appdevelopsk commented on Nov 13, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-13 follow-up — source smoke/source regression gate is now native-CI validated, but publication remains owner-controlled.

    • Merged PR #124, main 963705fa53e0d6b24dd3c52c7f5dd91ca4bf390c. Added six offline unit tests to check 57 literal required public smoke conditions against 15 checked-in HTML/XML sources and assert the one forbidden stale homepage marker is absent. Dynamic $slug/$code cases remain covered by separate press/rsync tests. Updated QA source/path filters to include the TaleTime page and parity test.
    • PR CI #43438073335 passed. Main CI #43438187417 passed.
    • Re-verified the owner ZIP created in #123, artifact run #43436368141: 44 source files, all 44 SHA-256 checksums match, ZIP CRC passes, and five localized press HTML pages are included. This archive is only a release input, not evidence of production deployment.
    • Live 5 press pages were HTTP 404 in previous authoritative live diagnostics; there is no subsequent successful VPS deploy or current live smoke in the appsite repo. Do not claim the 404s are resolved. Need the owner to start publish-vps.yml on main, review mode=dry-run, authorize mode=apply (self-hosted appsite-deploy runner) or manually transfer reviewed ZIP contents to the owned VPS. Then run actual HTTP smoke; only close once all five 200 and current catalog and FAQ are verified.

    No automated VPS apply, external advertising, social publication or indexing submission performed.

  20. appdevelopsk commented on Nov 14, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-14 JST — fresh independent production replay confirms the release is still blocked. Re-ran read-only live acquisition smoke #43429400764 as attempt 2. Downloaded the newly generated artifact 14089653160 and inspected its JSON: five press locales /press/, /press/es/, /press/pt-br/, /press/ja/, /press/id/ each HTTP 404; catalog /apps HTTP 200 lacks catalog-language selector; only 4/12 source/public URLs byte-identical. Public BrainBurst FAQ still exhibits old restore/subscription/offline language (current web crawler), so main fixes not deployed. No owner VPS apply observed in Actions.

    New source monitoring fix merged: PR #125 squash 65b77389. Previously push-path filter ignored press/**, homepage, sitemap and robots; now all acquisition-critical changes trigger immediate public live smoke. Two new offline read-only path/permission tests passed PR CI #43538495741, and main CI #43538554263 success. The resulting main live smoke #43538554459 correctly remains failure; this is a public delivery failure, not a false CI PASS. The source-only owner ZIP #123 remains valid: comparison from bundle-source commit to latest main changes only workflow/test files, not the 44 published HTML/XML files.

    Owner action: publish-vps.yml -> select main -> review dry-run -> explicitly approve mode=apply on registered appsite-deploy runner; alternatively upload the verified release ZIP's site/ contents to the confirmed VPS web root. Re-run live smoke and HTTP 200, canonical/lang/GA4 event checks; do not close this issue until verified. No VPS transfer, SNS post or store release was performed by this chat.

  21. appdevelopsk commented on Nov 14, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-14 — New bilingual Debate Me organic-entry guide merged, production still unverified

    PR #126 was merged into main at commit 0e272a2fb25d48af151d117b3e56975fc087b509. The source now includes:

    • /guides/ai-debate-practice/ (EN) and /guides/ai-debate-practice/ja/ (JA), reciprocal hreflang/canonical and Article schema.
    • In-context entry links from /guides/ai-tools/ and /support/debate-me/ and matching sitemap entries.
    • Source tests node --test tests/ai-debate-practice-guide.test.mjs (4 pass in isolated exact-file sandbox) and GitHub readback checks.

    Not done: actual appdevelopsk.com deployment, hosting mapping, live HTTP/canonical checks, GA4 DebugView, Google Play conversion and first-time installs, Android retention. Do not announce the guides as published until host SHA/source is checked (this repo README explicitly warns main != deployed). Recommended checks: node --test tests/ai-debate-practice-guide.test.mjs, python3 scripts/diagnose_growth_deploy.py --root . --output growth-deploy-diagnosis.json, run an authorized manual host publish only after verified checkout and compare HTML/sitemap on new URL and JA counterpart. Monitor real qualified organic clicks and Play Console first-time acquisitions after actual deployment, not GitHub-merge date.

    Metricool reports no connected social networks, so no social post was scheduled; authorization through https://app.metricool.com/brands/connections?blogId=7709450 remains external.

  22. appdevelopsk commented on Nov 14, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-14 11:05 JST — release bundle and sitemap parity gap corrected, public VPS still not published.

    Merged PR #127 as f5e963f227373b42830b57edd1b1ff44e55ab764. Discovered that recently published bilingual AI debate practice guide source pages /guides/ai-debate-practice/ (en) and /guides/ai-debate-practice/ja/ (ja) appeared in sitemap.xml and internal links but were not in the previous 27-file manual VPS allowlist or 44-file ZIP, so a subsequent owner deploy would have left two new organic landings at HTTP 404.

    Fix includes both locales in manual publish_app_discovery.sh allowlist, 46-file source-only ZIP (29 app discovery + 17 privacy policy), strict read-only public smoke on both guide languages/canonical/Android UTM CTA, and general regression: every sitemap-indexed /guides URL must map to an actual source file in the VPS publisher manifest. This is in addition to five international press routes.

    Native PR source QA #43543653999 success, PR source bundle #43543654003 success; after merge main QA #43543703317 and main owner ZIP #43543703178 success. Downloaded artifact ID 14093280790, extracted and verified 46/46 SHA-256 matches, ZIP CRC, 5 press pages, 2 AI guides, 17 policy files, owner-only README.

    External production remains stale. Main live smoke #43543703269 failed; previous Nov14 HTTP diagnostics proved all 5 press pages HTTP 404 and locale catalog absent. The separate Pages sync #43539163983 published GitHub Pages but still found stale support/brain-burst/ and support/debate-me/ on the VPS. GitHub Pages success is not a VPS release.

    Owner action still needed: publish-vps.yml manual main dry-run → explicitly approved mode=apply on owned appsite-deploy runner, or manually transfer verified ZIP site/ contents. Afterward rerun live smoke and verify 5 press + 2 debate guides HTTP 200, catalog selector, current BrainBurst/ Debate Me SEO. Do not claim user/revenue gains until measured. No production update was initiated from this chat.

  23. appdevelopsk commented on Nov 14, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-14 11:xx JST — verified re-inventory after PR #128 merged as 3c846d94b7187476cbfccf7fa25a58228c814aef. Native main source QA #43545015596 SUCCESS. Read-only public smoke #43545015433 FAILS as expected. Downloaded machine-readable artifact appsite-live-route-inventory-43545015433 (artifact id 14093418595) and inspected its JSON:

    • Public 5-language press /press/, /press/es/, /press/pt-br/, /press/ja/, /press/id/: all HTTP 404.
    • /apps HTTP 200 but does not contain expected 5-language catalog selector; /apps.html 200 and aliases body-match.
    • Full source/public byte compare 4/15 identical. Misses include new /guides/ai-debate-practice/ and /guides/ai-debate-practice/ja/ (HTTPError), /support/brain-burst/ and /support/debate-me/ (HTTP 200 but stale), homepage and catalog (200 but differs), plus 5 press 404.
    • PR CI: monitor deployed BrainBurst and bilingual debate guides; activate source diagnostics tests #128 adds those 3 newly important pages to independent release diagnostics and ACTIVATES previously dormant diagnostics tests in CI. PR + main CI green. It changes only monitoring/QA code, does not deploy.

    There is a valid 46-file source release ZIP from artifact run #43543703178 of source commit f5e963f2 (both bilingual debate guides and 5 press locales included). Latest main 3c846d94 changes only diagnosis/tests; the publishable HTML/XML set remains the same. Explicit owner approval is still required: publish to VPS workflow, main + inspect dry-run + mode=apply; or manually upload checksum-verified ZIP's site/ contents to confirmed web root without --delete. Then rerun live smoke, confirm all press & debate guide HTTP 200 and BrainBurst/Debate Me/catalog current. Do not close issue on source CI alone.

  24. appdevelopsk commented on Nov 14, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-14 addition to public release gates: PR #130 merged 0f65580968732a55d59023265cf489d79b77c530, adding safe EN/JA Quick Games alternatives from KeyClash support and classifying the existing single Play click event. The initial proposal to add KeyClash to 5/4-card Quick Games lists was reverted because its Android Google Play listing could not be verified and a third-party AppBrain page reports removal June 17, 2026. Owner Play Console check is tracked in issue #131; do not assert permanent delisting or resume store promotion until official listing and regional availability confirmed. Public deployment, signed-out link behavior, GA4 click attribution, and actual Play first-time acquisitions remain unverified. GSC 2026-11-09–11: KeyClash support 6 impressions/0 clicks; tiny sample.

  25. appdevelopsk commented on Nov 14, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-14 JST — ACTUAL completed truthful content / release work, not a VPS publication:

    • Merged PR #129 as main 713f3752471ec81e0a09aea25ab39428a202edcc, correcting One Tap Routine support page's false phone-lock/Device Owner/emergency unlock/premium claims to truthful habit tracking/FAQ. Reused verified correction from older PR Correct One Tap Routine support SEO and FAQ (remove inherited lock-app copy) #88; closed that draft as superseded to prevent duplicate/stale merging.
    • Added the corrected support page to reviewed owner-only app-discovery rsync manifest (30 app growth pages), source/smoke QA, privacy link and canonical checks, 3 native Node regression cases, updated sitemap freshness.
    • PR native QA and bundle test both success QA #43548775258 / ZIP #43548775261. Main source QA + ZIP build successful QA #43548944664 / ZIP #43548944627. Downloaded owner release artifact ID 14094963778, extracted the ZIP and independently validated 47/47 SHA256 checks, archive CRC, 5 press locales, both AI debate guides and existing 17 policy pages. No owner deployment attempted.
    • Main has moved further to 0f655809... after PR Fix One Tap Routine factual support copy and include corrected page in VPS release #129; commit comparison changes KeyClash support and test files only, leaving the 47-file reviewed release manifest and contents unchanged. This owner ZIP is thus still byte-correct for its explicit approved allowlist, NOT a full backup of every repository file.
    • Independent live smoke #43548944624 remains FAIL as expected. Prior 15-route diagnosis had 5 multilingual press HTTP404, 2 AI debate guide HTTP errors, stale One Tap/BrainBurst/DebateMe/catalog. Need owner on publish-vps.yml to review main dry-run, authorize mode=apply to correct VPS root, rerun live smoke and verify current One Tap truthful copy. GitHub Pages dynamic workflow success is NOT VPS publish proof.
    • Separate source fact-risk: latest support/key-clash/index.html contains a large multilingual FEAT_T object with unrelated plant encyclopedia labels like '144 Plant Species', 'Medicinal Properties', 'Herb Guide'. It must be corrected and product facts/store availability verified before including KeyClash in the curated VPS release manifest; do not blindly publish all sitemap-listed pages or claim its game listing is confirmed.
      This issue should remain open until public HTTP 200/source parity is demonstrated.
  26. appdevelopsk commented on Nov 14, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-14 follow-up: cross-site production content proof merged in appdevelopsk/growth-ops PR #24 (c7176e95527e85e0418b15855f8b14b89b53e197), including a read-only marker for the KeyClash safe Play-availability caveat from merged PR #130. The live /support/key-clash/ page could not be retrieved conclusively by web inspection; do not mark deployed based on GitHub main. Check actual Google Play Console package com.keyclash.key_clash and regional status per issue #131 before promoting new direct-download CTAs. This is not proof the app is permanently delisted. Source-only marketing edits are not real installs; measure Play first-time acquisitions and valid engaged sessions after live verification.

  27. appdevelopsk commented on Nov 15, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-15 new evidence for appdevelopsk.com: GSC finalized 10/15–11/11: 1,476 impressions and 17 clicks (CTR approx 1.15%); /support/debate-me/ 303 impressions/0 clicks vs /support/face-reaction-battle/ 188 impressions/8 clicks. GA4 11/14: 4 sessions, MAU 135, no tracked action events. Clarity previous 24h: 1 classified session and 1 bot, too little for conclusions. Most actionable: check exact query intent, visible store link and launch readiness on the real public support page; compare store outbound first-time installs after live SHA verifies source deployment. Cross-portfolio report in app-infra Draft PR #277; not a live site change or verified uplift.

  28. appdevelopsk commented on Nov 15, 2026

    @appdevelopsk
    OwnerAuthor

    Confirmed connected GSC 3-day finalized 2026-11-10–12: /support/debate-me/ had 82 impressions, 0 clicks, average position ~7.06; query debate me 63 impressions, 0 clicks, position ~6.76. Source support/debate-me/index.html ALREADY has optimized title Debate Me – Practice Debating with AI on Android | SK APPS, product description, and Play download URL. README shows 2026-11-13 snippet fixes awaiting production deployment verification. Do not make another speculative title update. First execute source-vs-live snippet/deploy checks documented in README, verify actual prod host ref/SHA, then GSC rendered snippet/query-to-page intent and store referral events.

  29. appdevelopsk commented on Nov 15, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-15 app acquisition source experiment

    Draft PR #133 adds localized opt-in sharing to Debate Me, FutureMe and Tappitsu Battle support pages. Shared URLs include utm_source=reader_share, utm_medium=referral, utm_campaign=app_support_share and a known public app slug only. share_tap means an attempt, not completion or an installation. Tested source script parser/URL builder/17 locale labels/deploy inclusion with 11 isolated checks; full repo tests/browser QA pending.

    VPS deployment critical: the script scripts/app-share.js was explicitly added to the existing exact file manifest and the safe offline release bundle. Running a release from old source without this asset would produce a non-functional button. Before owner-authorized manual publish: node --test tests/app-support-share.test.mjs, python3 -m unittest scripts.test_site_release_bundle scripts.test_publish_app_discovery_staging -v, python3 scripts/preflight_app_discovery.py, dry-run bash scripts/publish_app_discovery.sh --dry-run. After actual deploy, verify https://appdevelopsk.com/scripts/app-share.js 200 and share UX on the three URLs, then verify real inbound GA4 sessions and Play store acquisitions as separate datasets. This is draft source code, not a live launch.

  30. appdevelopsk commented on Nov 15, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-15 share/referral feature integrated, VPS still owner-only

    PR #133 MERGED: 8621d492e2861badbd68ee3e18a06b8572b60be8. Its head passed Public App Discovery and SEO QA and Prepare app site owner-only VPS release ZIP on GitHub Actions. The prior CI failures were stale assertions for BrainBurst/Debate Me titles and Debate Me UTM and an outdated ZIP entry count; corrected against the actual source (no SEO-content rollback).

    No VPS deploy yet. Publish through the authorized owner-managed release gate, not by treating CI artifact creation as publication. Verify /scripts/app-share.js HTTP 200 plus three actual /support/... pages, native share + clipboard, 17-locale behavior and GA4 share_tap vs true inbound reader_share sessions and Play acquisitions. The release bundle contains exactly 48 reviewed site documents/assets + SHA256SUMS + deployment instructions. Do not publish without source SHA/parity checks.

  31. appdevelopsk commented on Nov 15, 2026

    @appdevelopsk
    OwnerAuthor

    New production proof merged 2026-11-15

    PR #135 merged as a083291d334b8dee82089d70145cfe82db6fc6ca, after BOTH relevant CI workflows succeeded on final head 3b1fb7f67e698fde1158b895373b914856ddee93. Public smoke now fetches /scripts/app-share.js and fails if missing/no real JS native sharing or clipboard support, and checks three exact support-page script tags including Tappitsu Battle. Static source parity tests were fixed to current Debate Me title/description and new JS/HTML mapping. Owner-only --apply was not executed. After authorized VPS publish, run bash scripts/check_app_discovery_live.sh and browser QA (en/ja/ar, native share, clipboard denied, URL exactly clean); measure actual inbound UTM visits and Play acquisitions separately from share taps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions