Solo Cruise

Product

https://solo-cruise.com

Phase 1 closed out at v1.0-phase1; Phase 2A CRM schema deployed and verified. SGP onboarded (Matomo site 2, GA4 configured, Search Console verified, sitemap live). Governance reconciled 2026-09-15: production mapping corrected from VM102 to VM103; VM102 confirmed as Cabins 41 and out of scope. VM103 deployment runbook canonicalised on main (docs/DEPLOYMENT-RUNBOOK-VM103.md). VM103 frontend repaired 2026-09-15: static assets were deployed at wrong level for nested standalone server; clean flat standalone bundle deployed per runbook; legacy solocruise-api.service stopped and disabled. Frontend restored 2026-09-15: design-brief-integration visual system reconciled into main (e7e3cff) preserving VM702 Product API contract, Analytics, sitemap, robots.txt; deployed to VM103 and verified — brown/ink design live with VM702 data. Production baseline locked 2026-09-15: tag solo-cruise-prod-2026-09-15 on 682e96f; governance/PRODUCTION-BASELINE.yaml records approved baseline; deploy/deploy-production-frontend.sh is the only authorised deployment path (guards: main branch, clean tree, HEAD==origin/main, required markers, no HomePageClient, VM702 API contract, build success; writes BUILD-PROVENANCE.json; post-deploy verification); frontend/design-brief-integration marked historical/superseded.

Edit