Repository navigation
P1: publish Dotchi quick-games discovery source and verify real Play click funnel #29
Description
2026-10-30 source completed (do not reimplement)
- PR #28 merged into
mainatf22b768a3e7920fade714b43e949cc36f515224a. - PR CI success and post-merge source CI success.
- New source: Dotchi in the Quick games catalog filter and
/guides/quick-games/card, Play referrer/UTM andguide_store_click, 5-entry ItemList JSON-LD, sitemap lastmod; read-only live smoke gate.
Verified release gap
- Read-only main-push live smoke FAILED at 2026-10-30 06:34 UTC with
FAIL quick-games guide missing Dotchi CTA. Public VPS is not yet updated. This is expected after source-only merge but blocks any claims about real users.
Operator-owned publish (no ChatGPT deploy executed)
- In Actions: publish to VPS, choose main,
mode=dry-run, inspect proposed transfers of the targeted acquisition pages and policy pages. - If safe and authorized, run main,
mode=apply. The workflow uses a restricted self-hosted runner; it runs both app-discovery and policy sync without deleting files. Do not repeat apply if already current. - Inspect apply run's
本番の検証(apply 時のみ), or runbash scripts/check_app_discovery_live.shread-only. Verify bothdata-app="twotaku"on/guides/quick-games/andtwotakuin the public/appsQuick games filter. - After public confirmation, Google Search Console URL Inspection for canonical
https://appdevelopsk.com/guides/quick-games/if appropriate, and compare GA4guide_store_click(guide=quick-games, app=twotaku) over subsequent 7/28 day windows. The GSC request is optional; indexing is not guaranteed. - Compare actual Play listing acquisition separately, by reporting period. No inference from clicked UTM links alone.
Acceptance
- Production HTTP source reflects new guide/catalog and read-only smoke is green.
- Publication date / main SHA / successful apply run recorded.
- Future GA4 click and mature Play acquisitions measured after that date; report
unknownrather than 0 for missing data. - Any user-owned confirmation saved in handoff TXT; close only after public verification.
Preexisting site drift issue #21 was closed correctly after previous source matching production. This new content intentionally creates a new, distinct deployment gate.
Activity
appdevelopsk commentedon Oct 30, 2026
2026-10-30 22:58 JST — Additional source improvement integrated; publish once
mainSHA19e4123115c87e007c79e8b2c440043d199ba91eafter green PR CI, green post-merge CI.FAIL homepage missing published Dotchi feature. Earlier run 41014895153 failedFAIL quick-games guide missing Dotchi CTA. The scheduled policy/support sync giving 0 stale does not cover these latest growth gates.mainpublish with publish-vps.ymlmode=dry-runfirst and thenmode=applyif safe; no duplicate work or separate deployments per PR. Validate all homepage, guide, catalog, policy pages via the workflow's本番の検証(apply 時のみ)and rerunLive App Acquisition Pages Smokeif desired.appdevelopsk commentedon Oct 30, 2026
2026-10-30 23:26 JST: publish to VPS (main 19e4123, mode=apply) を実行・成功 https://github.com/appdevelopsk/appdevelopsk.github.io/actions/runs/41071430060
転送: apps.html / index.html / sitemap.xml / guides/quick-games/index.html (削除なし)。本番の検証ステップ PASS。
HTTP 確認: / に Dotchi あり(Face Battle カード無し・JS のタグライン辞書に名称が1件残るのみ)、/guides/quick-games/ に Dotchi + Play リンク2、/apps に Dotchi + Play リンク1。
Live App Acquisition Pages Smoke の手動 dispatch は GitHub API が HTTP 500 を返したため未実行(翌朝 09:40 JST の cron で再確認)。
https://claude.ai/code/session_01J5anYPwn44oC1yu4pesMiJ
appdevelopsk commentedon Oct 30, 2026
2026-10-31 00:27 JST: RELEASE VERIFIED / issue closure evidence. Operator-owned dry-run Actions run 41071042588 followed by real apply run 41071430060, deploying source SHA
19e4123tolocal:/var/www/html. Apply logs showPASS: catalog, guides, priority search landings, store CTAs, icon crawl policy and sitemap current (HTTP 200)andChecked 17 public policy pages; failures: 0. The current read-only live checks cover new quick-games Dotchi CTA, Quick games catalog filter, and homepage replacement. The publication gate is complete. Tracking and post-release acquisition/retention uplift are separate future measurements; no claimed download uplift. Closing issue to avoid repeating this VPS step.