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.
0) Goal (one sentence)
Section titled “0) Goal (one sentence)”Ship production-ready storefront delivery and business observability so approved testimonials drive visible merchant value and the app is launch-ready.
1) Scope lock (what is included)
Section titled “1) Scope lock (what is included)”In scope
Section titled “In scope”-
Storefront publication layer:
- Theme extension blocks (home + PDP)
- Public testimonials read API
- Placement filtering + fallback logic
-
Operational intelligence:
- Analytics page with funnel and media split
- Billing & usage page with usage meters and overage awareness
- Dashboard KPI alignment
-
Launch readiness:
- end-to-end QA
- app listing readiness checks
- compliance and performance sanity gates
Out of scope
Section titled “Out of scope”- New core capture workflows (already delivered in milestones 1–2)
- Advanced AI moderation and transcript enhancements
2) Dependencies from Milestones 1–2
Section titled “2) Dependencies from Milestones 1–2”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.
3) Deliverables
Section titled “3) Deliverables”D1 — Storefront API + Theme extension
Section titled “D1 — Storefront API + Theme extension”- Public read API supports:
placement=homeplacement=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 + readycontent appears publicly - Placement toggles respected:
- home
- PDP
- collection (if enabled)
- Featured and sort order applied consistently
D3 — Metrics and billing surfaces
Section titled “D3 — Metrics and billing surfaces”- Analytics page:
- funnel metrics
- product coverage
- media split
- Billing page:
- current plan
- usage vs included
- overage state
- upgrade CTA
D4 — Launch QA readiness
Section titled “D4 — Launch QA readiness”- merchant admin smoke tests
- storefront performance checks
- compliance checklist pass
4) Technical acceptance criteria
Section titled “4) Technical acceptance criteria”-
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.
-
Analytics/Billing
- KPI values reconcile with source records for sample ranges.
- Billing counters and overage estimates are deterministic and explainable.
-
Readiness
- Security and compliance checks complete for public endpoints.
- Theme blocks do not break storefront rendering when data is empty.
5) Test matrix (minimum)
Section titled “5) Test matrix (minimum)”Storefront matrix
Section titled “Storefront matrix”- Home widget with published videos only
- PDP widget with product matches
- PDP widget with no product matches + each fallback mode
- Unpublish flow removes item from widget response
- Feature/sort changes reflected in rendering order
Metrics matrix
Section titled “Metrics matrix”- Funnel values for date range with known fixture data
- Media split with mixed photo/video samples
- Billing usage and threshold banners (80%/100%)
Non-functional
Section titled “Non-functional”- API response latency under expected threshold
- Widget script loads and renders on mobile themes
- No PII leakage in public read payload
6) Risks and mitigations
Section titled “6) Risks and mitigations”-
Incorrect visibility filtering leaks unintended content
- Mitigation: single shared predicate helper used by API and admin previews.
-
Theme integration breaks merchant layout
- Mitigation: defensive JS and graceful no-op rendering when config/data invalid.
-
Billing distrust from mismatched counters
- Mitigation: reconciliation job and metric transparency in UI.
-
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)”- Finalize published content controls and placement fields (
11). - Implement/verify public read API contracts (
05). - Implement theme extension blocks and renderer.
- Build analytics screen and validation fixtures (
14,19). - Build billing & usage screen and usage counter reconciliation (
15). - Run launch QA matrix and fix blockers.
8) Launch readiness checklist
Section titled “8) Launch readiness checklist”- 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.
9) Done definition (Milestone 3)
Section titled “9) Done definition (Milestone 3)”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.
10) References
Section titled “10) References”02-Implementation-Blueprint.md— §9 Milestone 305-storefront-widgets-and-read-api.md11-published-content-screen-7.md14-analytics-blueprint-screen-11.md15-billing-and-usage-blueprint-screen-12.md23-release-plan-and-milestones-blueprint-section-9.md
11) Note on numbering
Section titled “11) Note on numbering”This folder already includes 05 through 30 plans. This file is 31-....