Skip to content

Harden Likeable billing and production readiness#2

Open
vyakymenko wants to merge 36 commits into
mainfrom
feature/likeable-billing-production-deploy
Open

Harden Likeable billing and production readiness#2
vyakymenko wants to merge 36 commits into
mainfrom
feature/likeable-billing-production-deploy

Conversation

@vyakymenko

@vyakymenko vyakymenko commented May 27, 2026

Copy link
Copy Markdown
Contributor

What changed

  • Scoped Likeable billing to build-hour packs and extra playground slots only.
  • Disabled production-project purchases before Stripe is called; legacy production metadata is recorded safely but no grant/start/notice is created.
  • Disabled custom-domain endpoints with explicit 410 handoff to Fibe.
  • Made playground idle sleep configurable via playground_idle_stop_hours and removed legacy production exemptions from idle-stop behavior.
  • Removed production/custom-domain controls from the builder and admin UI, and hid legacy production/domain fields from project/admin diagnostics JSON.
  • Removed dead production-start and custom-domain routing helpers so shared environments do not need to manage those paths.
  • Updated Admin readiness/billing health, live config, preflight, README, and Help copy to position Likeable as experiments/development; production hosting, always-on runtime, custom domains, and DNS work belong in Fibe.
  • Kept server guardrails for old routes/products so stale clients or old Stripe metadata fail closed instead of reviving the removed workflows.

Why

The production/custom-domain flow adds too much operational complexity for a shared Likeable environment. The safer product boundary is: Likeable sells experimentation capacity, then users move serious production/custom-domain work to Fibe.

Validation

Latest local validation on head 9e1d8b4:

  • npm run lint
  • npm run build
  • docker run --rm -v "$PWD":/src -v /tmp/likeable-go-mod:/go/pkg/mod -v /tmp/likeable-go-build:/root/.cache/go-build -w /src golang:1.26.1-bookworm go test ./...
  • bin/deploy-preflight
  • git diff --check

GitHub CI:

  • Deploy preflight passed on commit 9e1d8b478ad8a0326df7bd52e3cc9ea32e8947c5.

Browser/UI notes:

  • Earlier browser smoke confirmed the builder no longer showed Make production or custom-domain actions, and Help showed the Fibe handoff copy.
  • After the final internals cleanup, in-app Browser could not create an active pane (No active Codex browser pane available), so final verification relies on TypeScript, Go tests, deploy preflight, and the explicit diagnostics JSON hidden-field test.

Deploy notes

Deployed to Fibe playground likeable-vyakymenko / id 92 on branch feature/likeable-billing-production-deploy.

Current running image:

  • playgrounds/likeable/app:9e1d8b4-b527
  • public URL: https://likeable.vyakymenko.com

Live validation after rollout:

  • playground status is running; redis and app are running.
  • /healthz returns 200 with redis/sqlite ok.
  • / and /admin/billing return 200.
  • bin/live-readiness with LIKEABLE_ALLOW_BLOCKERS=1 shows billing health clear: no billing issues, hour packs 1/10/100, project slots enabled.
  • Live checkout smoke creates Stripe Checkout Sessions for hour_pack and project_quota; production_project returns 410 before Stripe checkout. No payment was completed.

Known live readiness blockers are environment setup, not Likeable billing code:

  • google_oauth: missing Google client id/secret.
  • smtp_delivery: missing SMTP host/from email warning.

@vyakymenko vyakymenko changed the title [codex] Harden Likeable billing and production readiness Harden Likeable billing and production readiness May 28, 2026
@vyakymenko vyakymenko marked this pull request as ready for review May 28, 2026 18:44
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