Skip to main content

Flow Studio Release Smoke Checklist

Use this checklist before publishing a major Flow Studio iteration to Cloudflare Pages. Small copy, styling, and minor scenario-data updates should ship through normal docs builds without creating a new public release snapshot.

Major iteration gate​

A Cloudflare Pages publish must be tied to one of these release markers:

  • a Git tag named flow-studio-vN-name, for example flow-studio-v2-restricted-views
  • a manual docs-portal workflow dispatch with publish_cloudflare=true and major_iteration=vN-name

Do not publish for routine wording, color, or spacing changes unless the user-facing flow, permission model, API surface, notification behavior, training mode, or public demo story materially changed.

Source readiness​

  • The changed behavior is represented in docs-portal/src/flow-studio/scenarios.mjs or the canonical Flow Studio source before UI-only edits.
  • Role visibility still matches the intended viewer type: technical admin, developer, non-technical admin, community moderator, and submitter.
  • Technical-system scenarios that mention private dashboards or credential references are restricted to the technical admin viewer profile.
  • Non-developer viewers see platform behavior and how-to guidance, not API payloads, state changes, audit trails, or private implementation details.
  • Every meaningful screen, action, message, API-adjacent moment, and workflow state has an information link to the appropriate technical or user-facing documentation.
  • Public user documentation and API documentation are updated when the release changes user instructions, connector behavior, moderation behavior, notification copy, or API contracts.
  • No private repository URLs, real phone numbers, credentials, private customer messages, production IDs, or confidential partner details are visible in public documentation or scenarios.
  • The release history entry names the major iteration and the reason it qualifies as a major snapshot.

Automated validation​

Run these from docs-portal before publishing manually:

npm run test:flow-studio
npm run test:flow-studio-access
npm run test:flow-studio-access-enforcement
npm run test:experience-system
npm run test:tenant-emulators
npm run build
npm run build:astro
npm run stage:astro-deploy
npm run test:third-party-services-public-build
npm run test:experience-system-browser
npm run test:experience-system-deploy-artifact
npm run test:flow-studio-browser

The GitHub docs-portal workflow runs the same Flow Studio, experience-system, deploy-artifact, and browser checks before release-tag or manual Cloudflare publishing.

Visual smoke paths​

Check these routes on desktop and mobile viewports:

  • Astro experience system catalog under /astro/experience-system/, confirming SEO/AEO, Event Submission, Source Ingest, WhatsApp, FiestaGenius, GLD, Mi Gente, and Flow Studio access-readiness entries are listed.
  • Astro Event Submission product shell, confirming the first-viewport owner-route handoff, redirect-enabled stage, owner route link, deployment evidence link, product canonical route report link, and disabled provider/write/publish actions are visible.
  • Astro Source Ingest product shell, confirming the first-viewport owner-route handoff, redirect-enabled stage, owner route link, deployment evidence link, product canonical route report link, disabled write/publish/operator-approval actions, and lane boundaries are visible.
  • Astro SEO/AEO product shell, confirming the first-viewport owner-route handoff, redirect-enabled stage, owner route link, deployment evidence link, and product canonical route report link are visible while /astro-scaffold remains the preserved scaffold reference.
  • Astro FiestaGenius tenant shell, confirming the first-viewport owner-route handoff, redirect-enabled stage, owner route link, deployment evidence link, tenant canonical route report link, disabled publish/channel/payment/write actions, and public-safe tenant ownership metadata are visible while /astro-scaffold remains the preserved scaffold reference.
  • Astro FiestaGenius public chatbot prototype shell, confirming the first-viewport owner-route handoff, redirect-enabled stage, owner route link, deployment evidence link, tenant canonical route report link, disabled provider/publish/payment/write actions, and public-safe prototype ownership metadata are visible while /astro-scaffold remains the preserved scaffold reference.
  • Astro FiestaGenius dashboard Flow Studio shell, confirming the first-viewport owner-route handoff, redirect-enabled stage, tenant-owned dashboard readiness route link, deployment evidence link, tenant canonical route report link, disabled auth/billing/publish actions, and dashboard launch blockers are visible while /astro-scaffold remains the preserved scaffold reference.
  • Astro WhatsApp Submission Flow Studio shell, confirming the first-viewport owner-route handoff, redirect-enabled stage, dedicated Flow Studio scenario owner route link, deployment evidence link, Flow Studio canonical route report link, disabled provider/moderation/distribution actions, and hidden API payload panel state are visible while /astro-scaffold remains the preserved scaffold reference.
  • Astro WhatsApp Missing Info Flow Studio shell, confirming the first-viewport owner-route handoff, redirect-enabled stage, dedicated Flow Studio scenario owner route link, deployment evidence link, Flow Studio canonical route report link, disabled follow-up/moderation/distribution actions, and hidden API payload panel state are visible while /astro-scaffold remains the preserved scaffold reference.
  • Astro FiestaGenius Submission Flow Studio shell, confirming the first-viewport owner-route handoff, redirect-enabled stage, dedicated Flow Studio scenario owner route link, deployment evidence link, Flow Studio canonical route report link, disabled provider/publish/private-distribution actions, and hidden API payload panel state are visible while /astro-scaffold remains the preserved scaffold reference.
  • Astro FiestaGenius Assistant Q&A Flow Studio shell, confirming the first-viewport owner-route handoff, redirect-enabled stage, dedicated Flow Studio scenario owner route link, deployment evidence link, Flow Studio canonical route report link, disabled assistant-send/escalation/private-info actions, and hidden API payload panel state are visible while /astro-scaffold remains the preserved scaffold reference.
  • Astro FiestaGenius Support Agent Flow Studio shell, confirming the first-viewport owner-route handoff, redirect-enabled stage, dedicated Flow Studio scenario owner route link, deployment evidence link, Flow Studio canonical route report link, disabled support-send/case-mutation/billing/private-data actions, and hidden API payload panel state are visible while /astro-scaffold remains the preserved scaffold reference.
  • Astro FiestaGenius Category Taxonomy Flow Studio shell, confirming the first-viewport owner-route handoff, redirect-enabled stage, dedicated Flow Studio scenario owner route link, deployment evidence link, Flow Studio canonical route report link, disabled taxonomy-write/tenant-config/publish actions, and hidden API payload panel state are visible while /astro-scaffold remains the preserved scaffold reference.
  • Astro FiestaGenius Distribution Review Flow Studio shell, confirming the first-viewport owner-route handoff, redirect-enabled stage, dedicated Flow Studio scenario owner route link, deployment evidence link, Flow Studio canonical route report link, disabled private-channel/owner-approval/provider-send actions, and hidden API payload panel state are visible while /astro-scaffold remains the preserved scaffold reference.
  • Astro FiestaGenius Billing Readiness Flow Studio shell, confirming the first-viewport owner-route handoff, redirect-enabled stage, dedicated Flow Studio scenario owner route link, deployment evidence link, Flow Studio canonical route report link, disabled Stripe-checkout/customer-portal/webhook-subscription actions, and hidden API payload panel state are visible while /astro-scaffold remains the preserved scaffold reference.
  • Astro GLD Event Submission Flow Studio shell, confirming the first-viewport owner-route handoff, redirect-enabled stage, dedicated Flow Studio scenario owner route link, deployment evidence link, Flow Studio canonical route report link, disabled guarded-Supabase-write/connector-publishing/source-queue-ownership actions, and hidden API payload panel state are visible while /astro-scaffold remains the preserved scaffold reference.
  • Astro SEO/AEO Dashboard Flow Studio shell, confirming the first-viewport owner-route handoff, redirect-enabled stage, dedicated Flow Studio scenario owner route link, deployment evidence link, Flow Studio canonical route report link, disabled publish/tenant-write/provider-write actions, and hidden API payload panel state are visible while /astro-scaffold remains the preserved scaffold reference.
  • Astro GLD Ingest and Aggregator Flow Studio shell, confirming the first-viewport owner-route handoff, redirect-enabled stage, dedicated Flow Studio scenario owner route link, deployment evidence link, Flow Studio canonical route report link, disabled source-queue/publish-package actions, submitter-chat ownership exclusion, and hidden API payload panel state are visible while /astro-scaffold remains the preserved scaffold reference.
  • Astro Mi Gente Directory Flow Studio shell, confirming the first-viewport owner-route handoff, redirect-enabled stage, dedicated Flow Studio scenario owner route link, deployment evidence link, Flow Studio canonical route report link, disabled directory-correction/production-publish actions, and hidden API payload panel state are visible while /astro-scaffold remains the preserved scaffold reference.
  • Astro Flow Studio shells for SEO/AEO, WhatsApp missing-info, FiestaGenius submission/Q&A/support/category/distribution/billing, GLD event submission, GLD ingest, Mi Gente directory, and access readiness as non-technical viewers, confirming API payload panels and GitHub source links stay hidden.
  • Astro GLD Flow Studio delivery lane switchboard, confirming submission and source ingest lanes stay separate.
  • Astro Flow Studio Access Readiness shell, confirming public route graduation remains blocked until protected public/restricted route separation exists.
  • Astro scaffold ownership panels, confirming public-safe steward, lane, source-of-truth, and review cadence metadata are visible without private implementation details.
  • Astro route exposure panels, confirming public-safe /astro visibility, preserved /astro-scaffold references, auth source, source-of-truth, access issue, and restricted-route state are visible without private implementation details.
  • Generated /astro/scaffold-reference-retirement-audit.json, confirming redirect-enabled scaffold references are retained until issue #348 records route-by-route retirement decisions.
  • Generated /astro/seo-aeo-scaffold-readiness.json, confirming the SEO/AEO product shell and Flow Studio shell both have product/scenario ownership, public-safe docs refs, disabled actions, read-only live checks, visual baseline coverage, retained /astro-scaffold references, and complete public-scaffold status.
  • Generated /astro/flow-studio-access-enforcement.json, confirming restricted Flow Studio scenarios remain out of public Astro routes and strict protected-host preflight inputs are documented without private account data.
  • WhatsApp Submission as technical admin, moderator, and submitter.
  • GLD Flow Studio Delivery Lanes, confirming the submission and aggregation direct links are visible.
  • GLD Event Submission as submitter on the desktop chat surface and as technical admin on the admin editor surface.
  • GLD Ingest as technical admin on the desktop operator console.
  • GLD Ingest as community moderator and non-technical admin on the mobile operator app surface.
  • Technical System Flow Studio as technical admin, confirming private-dashboard links stay no-secret and step-by-step.
  • Submitter view deep-linked with an admin role; it must downgrade to an allowed lower-permission view.

For each path, confirm:

  • the scenario and surface selector docks directly below the main header while scrolling
  • changing the viewer closes the profile menu
  • lower-permission users cannot select higher-permission role views
  • non-technical users get public how-to documentation links
  • technical admin and developer profiles can see API and implementation documentation links
  • the technical-system credential dashboard scenario is not available to developer, non-technical admin, moderator, or submitter profiles
  • the technical-system credential dashboard scenario is not exposed as a public Astro scaffold route
  • Flow Studio Access Readiness records protected-host-verified while remaining a public-safe readiness shell
  • the Flow Studio access-enforcement manifest records the technical credential dashboard as restricted and the private dashboard host as protected
  • the GLD desktop submitter/admin intake is a chatbot-style event intake, not a generic console card
  • the visible response messages and moderator/operator panels match the scenario state

Cloudflare publish checks​

  • The GitHub repository has the required Cloudflare deployment secrets configured.
  • The GitHub repository has the selected public Flow Studio URL configured for release builds.
  • The release workflow is started from a flow-studio-v* tag or manual dispatch with a major iteration name.
  • The staged Astro scaffold catalog returns HTTP 200 under /astro/experience-system/.
  • The staged Astro scaffold product, tenant, Flow Studio, and prototype links are all prefixed under /astro/.
  • Any owner-route-live canonical target, deployment evidence, and route report links remain public-safe read-only URLs.
  • Existing Docusaurus prototype routes still return HTTP 200 and are not overwritten by Astro transition routes.
  • The Cloudflare Pages preview URL and production URL both return HTTP 200.
  • A hydrated browser smoke check confirms the updated WhatsApp and GLD Flow Studio text is visible on the public site.
  • A browser smoke check confirms non-technical Astro-backed Flow Studio viewers cannot see source edit links or API payload panels.

Release record​

After publication, record:

  • major iteration id
  • GitHub commit SHA
  • Cloudflare Pages preview URL
  • production URL
  • /astro/experience-system/ catalog URL
  • validation commands or workflow run link
  • any known limitations or blocked follow-up issues