Rendered from GitHub DAILY_BRIEF.md · fetched 2026-05-05T02:05:55.000Z
The freemium framework is functionally complete on the iOS side and the v1.5 feature checklist has been done for days — the app is ready to ship but is being held by three backend deployment steps and one constant that needs a real date. Today's commits were focused squarely on closing that gap: App Store subscription copy is drafted, the entitlements Worker is getting wired up, and FreemiumLaunch.swift exists as the single ship-date control. Walk in knowing the blockers are all mechanical, not architectural — this release is a checklist problem, not an engineering problem.
docs(asc): added 55-char subscription Description plus long reference copy (App Store subscription display copy now fully drafted)docs(asc): documented where subscription display name/description live in App Store Connect (removes ambiguity at submission time)docs(asc): expanded §6 of APP_STORE_CONNECT_FREEMIUM_CHECKLIST.md with App Store description and subscription copydocs(asc): deferred promotional offer (#4 in checklist) until grant cohort nears expiry — reduces submission complexitychore(entitlements): wired D1 database_id into wrangler.toml, aligned migration filename with remote DB — unblocks npm run db:migrate:remotefix(ios): registered FreemiumLaunch.swift in Xcode project (was missing from build target, would have caused compile failure)feat(freemium): aligned pipeline items #71–#79, added entitlements Worker routes, wired PoolViewModel premium gates for Weather Guard and Lightning Proximitypoolos-entitlements backend deploy.da69de0); no further code work needed — blocked on ASC product IDs existing so StoreKit can resolve them.firstLaunchDate; blocked on freemiumLaunchEpoch constant being set to actual ship date before archive.98f8d0d); blocked on five manual steps: create MyPoolOS/poolos-entitlements GitHub repo, add remote, push, add CLOUDFLARE_API_TOKEN secret, run wrangler d1 create poolos-entitlements, paste database_id (done as of today's commit 6934077), npm run db:migrate:remote, set 4 wrangler secrets (ADMIN_TOKEN, APPLE_ID_SALT, FREEMIUM_LAUNCH_EPOCH, APPLE_SHARED_SECRET).PremiumUpgradeView; no outstanding code — waiting on backend /redeem endpoint being live.V1.5 release blockers (Todo):
POST /admin/codes behind Cloudflare Access + ADMIN_TOKEN.com.mypoolos.premium.monthly ($8.99 Tier 9) + com.mypoolos.premium.annual ($89.99 Tier 90), Family Sharing ON, 14-day intro offer, ASN v2 webhook → https://entitlements.mypoolos.app/webhook/apple.Planned / lower priority:
No new App Store updates, website pushes, or customer feedback signals landed in the last 24 hours — today was a heads-down execution day on the freemium plumbing. The App Store listing copy (Marketing/AppStore_listing_v1.5.md) and the Weather Watch landing page rewrite are both complete and waiting on the v1.5 submission trigger. The TFP/Reddit founder post (Marketing/TFP_launch_post_v1.md) is drafted and also holding for submission. The single highest-leverage marketing move this week is completing the poolos-entitlements backend deploy and creating the ASC subscription products — not because those are marketing tasks, but because they are the last mechanical gates standing between the current state and the v1.5 submission that unlocks every queued marketing action simultaneously.
poolos-entitlements GitHub repo creation and wrangler deploy sequence. Five steps documented in the wiki: create MyPoolOS/poolos-entitlements, git remote add + push, add CLOUDFLARE_API_TOKEN secret, npm run db:migrate:remote, set 4 wrangler secrets. database_id is now in wrangler.toml (commit 6934077). This is the single hardest blocker on v1.5 ship.com.mypoolos.premium.monthly ($8.99) and com.mypoolos.premium.annual ($89.99), Family Sharing ON, 14-day intro offer, ASN v2 webhook URL. Required before any StoreKit 2 sandbox testing can happen.freemiumLaunchEpoch in FreemiumLaunch.swift to the actual intended ship date. Currently 1_748_736_000 (placeholder). Decide your target submission date, convert to Unix epoch, commit. This constant gates the existing-user auto-grant for all v1.4 users — it must be correct before archive.docker compose down -v) is due today (2026-05-04 per decommission plan). Confirm you want to run this — it is destructive and the NAS containers are confirmed decommissioned, but flag it as a deliberate act before executing.