SOP: Capacitor Mobile Project Lifecycle (playground → app → prod) #117

New issue

Open

opened 2026-03-17 01:50:34 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-17 01:50:34 +00:00

Contributor

Lineage

plan-pal-e-agency → Backlog

Repo

forgejo_admin/claude-custom

User Story

As Betty Sue managing multi-repo projects
I want a documented SOP for the playground → Capacitor app → production lifecycle
So that I never skip gates or parallelize across dependency boundaries

Context

During Phase 7c of mcd-tracker, docker-compose work was created before the playground CSS cleanup was approved. This violates the dependency chain: playground must be approved on phone before Capacitor promotion begins, and Capacitor app must have local dev validation before production deployment.

The SOP should codify:

Input contract — playground repo requirements (single app.css, single app.js, zero inline styles)
Gate 1 — Lucas approves playground on phone
Promotion — mechanical copy: app.css → src/app.css, HTML body → +page.svelte
Gate 2 — docker compose up validates full flow locally
Output contract — 10-point checklist (landing renders, auth works, full flow, hot reload, phone access, build succeeds, Dockerfile works, THEN push to prod)
Gate 3 — production deploy via CI → Harbor → ArgoCD

File Targets

Files to create:

SOP note in pal-e-docs: sop-capacitor-mobile-lifecycle

Acceptance Criteria

SOP note created in pal-e-docs with full lifecycle documented
Input contract section matches Phase 7c playground rules
Output contract section matches Phase 7c verification checklist
Gate dependencies are explicit and non-negotiable

Test Expectations

SOP is queryable via get_note(slug="sop-capacitor-mobile-lifecycle")
Run command: N/A (documentation only)

Constraints

This is a pal-e-docs note, not a code change
Should reference but not duplicate existing SOPs (sop-frontend-experiment, etc.)

Checklist

SOP note created
Linked from sop-index

pal-e-agency — project this affects
mcd-tracker — first project to use this lifecycle
sop-frontend-experiment — related SOP to update

### Lineage `plan-pal-e-agency` → Backlog ### Repo `forgejo_admin/claude-custom` ### User Story As Betty Sue managing multi-repo projects I want a documented SOP for the playground → Capacitor app → production lifecycle So that I never skip gates or parallelize across dependency boundaries ### Context During Phase 7c of mcd-tracker, docker-compose work was created before the playground CSS cleanup was approved. This violates the dependency chain: playground must be approved on phone before Capacitor promotion begins, and Capacitor app must have local dev validation before production deployment. The SOP should codify: 1. **Input contract** — playground repo requirements (single app.css, single app.js, zero inline styles) 2. **Gate 1** — Lucas approves playground on phone 3. **Promotion** — mechanical copy: app.css → src/app.css, HTML body → +page.svelte 4. **Gate 2** — docker compose up validates full flow locally 5. **Output contract** — 10-point checklist (landing renders, auth works, full flow, hot reload, phone access, build succeeds, Dockerfile works, THEN push to prod) 6. **Gate 3** — production deploy via CI → Harbor → ArgoCD ### File Targets Files to create: - SOP note in pal-e-docs: `sop-capacitor-mobile-lifecycle` ### Acceptance Criteria - [ ] SOP note created in pal-e-docs with full lifecycle documented - [ ] Input contract section matches Phase 7c playground rules - [ ] Output contract section matches Phase 7c verification checklist - [ ] Gate dependencies are explicit and non-negotiable ### Test Expectations - [ ] SOP is queryable via `get_note(slug="sop-capacitor-mobile-lifecycle")` - Run command: N/A (documentation only) ### Constraints - This is a pal-e-docs note, not a code change - Should reference but not duplicate existing SOPs (sop-frontend-experiment, etc.) ### Checklist - [ ] SOP note created - [ ] Linked from sop-index ### Related - `pal-e-agency` — project this affects - `mcd-tracker` — first project to use this lifecycle - `sop-frontend-experiment` — related SOP to update