Skip to content

31 — Milestone 3 Delivery Plan (Blueprint §9.3)

Cursor-ready execution plan for Milestone 3: storefront widgets, public read API, analytics/billing surfaces, and launch QA readiness.

31 — Milestone 3 Delivery Plan (Blueprint §9.3)

Section titled “31 — Milestone 3 Delivery Plan (Blueprint §9.3)”

Source: 02-Implementation-Blueprint.md§9 Release Plan → Milestone 3 (2 weeks).

Milestone 3 blueprint scope:

  • Theme widget rendering (home + PDP)
  • Widget storefront API
  • Analytics + billing limits
  • App Store readiness and QA

This document is a build spec only. No code changes are implied until a task references this file.

Related: 05, 11, 14, 15, 19, 21, 22, 23, 24.


Ship production-ready storefront delivery and business observability so approved testimonials drive visible merchant value and the app is launch-ready.


  1. Storefront publication layer:

    • Theme extension blocks (home + PDP)
    • Public testimonials read API
    • Placement filtering + fallback logic
  2. Operational intelligence:

    • Analytics page with funnel and media split
    • Billing & usage page with usage meters and overage awareness
    • Dashboard KPI alignment
  3. Launch readiness:

    • end-to-end QA
    • app listing readiness checks
    • compliance and performance sanity gates
  • New core capture workflows (already delivered in milestones 1–2)
  • Advanced AI moderation and transcript enhancements

Milestone 3 assumes:

  • request pipeline is live and stable (29)
  • public submission and moderation flow complete (30)
  • published content controls operational (11)

If any dependency is unstable, delay public widget rollout.


  • Public read API supports:
    • placement=home
    • placement=pdp&product_id=...
  • Two-block extension (recommended):
    • home widget block
    • PDP widget block
  • Shared JS renderer with loading/empty/error states

D2 — Visibility and merchandising correctness

Section titled “D2 — Visibility and merchandising correctness”
  • Only approved + published + ready content appears publicly
  • Placement toggles respected:
    • home
    • PDP
    • collection (if enabled)
  • Featured and sort order applied consistently
  • Analytics page:
    • funnel metrics
    • product coverage
    • media split
  • Billing page:
    • current plan
    • usage vs included
    • overage state
    • upgrade CTA
  • merchant admin smoke tests
  • storefront performance checks
  • compliance checklist pass

  1. Storefront

    • Home widget shows top configured published content.
    • PDP widget shows only product-linked content unless fallback mode applies.
    • Unpublish or visibility toggle updates reflect quickly in API results.
  2. Analytics/Billing

    • KPI values reconcile with source records for sample ranges.
    • Billing counters and overage estimates are deterministic and explainable.
  3. Readiness

    • Security and compliance checks complete for public endpoints.
    • Theme blocks do not break storefront rendering when data is empty.

  1. Home widget with published videos only
  2. PDP widget with product matches
  3. PDP widget with no product matches + each fallback mode
  4. Unpublish flow removes item from widget response
  5. Feature/sort changes reflected in rendering order
  1. Funnel values for date range with known fixture data
  2. Media split with mixed photo/video samples
  3. Billing usage and threshold banners (80%/100%)
  1. API response latency under expected threshold
  2. Widget script loads and renders on mobile themes
  3. No PII leakage in public read payload

  1. Incorrect visibility filtering leaks unintended content

    • Mitigation: single shared predicate helper used by API and admin previews.
  2. Theme integration breaks merchant layout

    • Mitigation: defensive JS and graceful no-op rendering when config/data invalid.
  3. Billing distrust from mismatched counters

    • Mitigation: reconciliation job and metric transparency in UI.
  4. Performance regressions on storefront

    • Mitigation: cap payload size, lazy media behavior, optimized indexes.

7) Suggested implementation order (Cursor)

Section titled “7) Suggested implementation order (Cursor)”
  1. Finalize published content controls and placement fields (11).
  2. Implement/verify public read API contracts (05).
  3. Implement theme extension blocks and renderer.
  4. Build analytics screen and validation fixtures (14, 19).
  5. Build billing & usage screen and usage counter reconciliation (15).
  6. Run launch QA matrix and fix blockers.

  • All milestone 3 acceptance criteria met.
  • Security/compliance tests pass (08).
  • Route map and nav complete (21, 24).
  • Merchant onboarding path tested end-to-end.
  • App listing assets/copy align with implemented behavior.

Milestone 3 is complete when:

  • merchants can reliably publish and display testimonials on storefront home/PDP,
  • key business metrics and usage/billing are visible and trustworthy,
  • app passes internal launch quality and compliance checks.

  • 02-Implementation-Blueprint.md — §9 Milestone 3
  • 05-storefront-widgets-and-read-api.md
  • 11-published-content-screen-7.md
  • 14-analytics-blueprint-screen-11.md
  • 15-billing-and-usage-blueprint-screen-12.md
  • 23-release-plan-and-milestones-blueprint-section-9.md

This folder already includes 05 through 30 plans. This file is 31-....