Files
igny8/docs/plans/LAUNCH-VERIFICATION-CHECKLIST.md
IGNY8 VPS (Salman) 6c69ca3feb Version 1.8.1
2026-01-18 15:18:25 +00:00

8.4 KiB

IGNY8 v1.8.1 Launch Verification Checklist

Version: 1.8.1
Created: January 17, 2026
Updated: January 18, 2026
Purpose: Final end-to-end verification before production launch


Quick Status

Section Items Status
1. User Journey 12
2. Content Paths 8
3. Settings Verification 10
4. Analytics & Billing 7
5. Documentation 6
6. Design Standards 5
7. Future Update Rules 4

1. USER JOURNEY VERIFICATION

1.1 - Registration & Onboarding

# Test Expected Pass
1 Visit /register Form renders, validation works [ ]
2 Submit registration Account created, redirects to wizard [ ]
3 Onboarding wizard Step 1 Welcome screen, "Get Started" works [ ]
4 Onboarding wizard Step 2 Add site with industry/sectors [ ]
5 Onboarding wizard Step 3 WordPress integration (can skip) [ ]
6 Onboarding wizard Step 4 Add initial keywords (can skip) [ ]
7 Onboarding wizard Step 5 Completion summary, go to dashboard [ ]

1.2 - Authentication Flows

# Test Expected Pass
8 Login with email/password JWT issued, redirects to dashboard [ ]
9 Forgot password flow Reset email sent, link works [ ]
10 Change password (in-app) Password updated, session valid [ ]
11 Logout Session cleared, redirect to login [ ]
12 Token refresh Automatic refresh before expiry [ ]

2. CONTENT PIPELINE PATHS

2.1 - Manual Pipeline (Full Path)

Stage Action Verify Pass
1 Add keywords manually Keywords appear in list, status: pending [ ]
2 Run clustering Clusters created, keywords linked [ ]
3 Generate ideas from cluster Ideas created with title/brief [ ]
4 Convert ideas to tasks Tasks appear in Writer Queue [ ]
5 Generate content Full article with HTML + meta [ ]
6 Generate image Featured image attached to content [ ]
7 Review content Editor works, preview renders [ ]
8 Publish to WordPress Content appears on WP site [ ]

2.2 - Automated Pipeline

# Test Expected Pass
1 Configure automation (Site Settings > Automation) Settings save, schedule displays [ ]
2 Run automation manually (Run Now) All enabled stages execute in order [ ]
3 Pause automation mid-run Run pauses after current item [ ]
4 Resume paused automation Continues from saved stage [ ]
5 Skip stage configuration Skipped stages show 0 processed [ ]
6 Per-run limits respected Stages stop at configured limit [ ]

2.3 - Publishing Paths

# Test Expected Pass
1 Manual publish (single) Content published immediately [ ]
2 Schedule for future Content scheduled, shows in calendar [ ]
3 Bulk schedule Multiple items scheduled with stagger [ ]
4 Auto-approval flow Review → Approved automatically [ ]
5 Auto-publish flow Scheduled → Published at time [ ]
6 Unschedule content Content removed from schedule [ ]

3. SETTINGS VERIFICATION

3.1 - Site Settings Tabs

Tab Settings to Verify Pass
General Site name, URL, industry, sectors, description [ ]
Automation Schedule, stages, batch sizes, per-run limits [ ]
Integrations WordPress connection status, sync settings [ ]

3.2 - Automation Settings (Unified)

Setting Verify Pass
Enable/disable toggle Saves and reflects in next run [ ]
Frequency (hourly/daily/weekly) Next run calculates correctly [ ]
Scheduled days Only selected days show in schedule [ ]
Time slots Run starts within selected window [ ]
Stage enable/disable Disabled stages skipped [ ]
Batch sizes Correct items per batch [ ]
Per-run limits Stage stops at limit [ ]
Testing model selection Uses correct model (is_testing) [ ]

3.3 - Account Settings

Setting Page Verify Pass
Organization name Account tab Saves and displays [ ]
Profile info Profile tab Name, timezone save [ ]
Password change Profile tab Requires old password [ ]
Team members Team tab Can invite, list shows [ ]

4. ANALYTICS & BILLING

4.1 - Credits System

Test Expected Pass
Header displays balance Shows full number (12,000 not 12k) [ ]
Clustering consumes credits Balance decreases correctly [ ]
Idea generation consumes credits Balance decreases correctly [ ]
Content generation consumes credits Token-based calculation correct [ ]
Image generation by tier Basic=5, Quality=15, Premium=25 [ ]
Zero credits blocks AI Shows "insufficient credits" error [ ]
Transaction logged Appears in credit history [ ]

4.2 - Billing & Payments

Test Expected Pass
Current plan displays Shows correct plan name + price [ ]
Upgrade flow works Stripe/PayPal checkout opens [ ]
Payment history shows Past invoices listed [ ]
Subscription renewal date Calculated correctly [ ]
Credits reset date Matches billing cycle [ ]

5. DOCUMENTATION CHECK

5.1 - Core Documentation

Document Status Verified
docs/INDEX.md - v1.8.0 Updated [ ]
CHANGELOG.md - v1.8.0 Updated [ ]
10-MODULES/AUTOMATION.md Reflects unified settings [ ]
10-MODULES/PUBLISHER.md Reflects unified settings [ ]
20-API/ENDPOINTS.md unified-settings endpoint added [ ]
30-FRONTEND/PAGES.md Removed pages documented [ ]

5.2 - Help Content

Help Section Accurate Pass
Getting Started Matches current wizard flow [ ]
Pipeline flow 7-stage + publish accurate [ ]
Settings descriptions Matches current UI [ ]
FAQ answers Still accurate [ ]

6. DESIGN STANDARDS COMPLIANCE

6.1 - UI Consistency Check

Area Standard Verified
Module colors Planner=green, Writer=yellow, Automation=blue, Publisher=purple [ ]
Buttons Using <Button> component everywhere [ ]
Forms Using <InputField>, <SelectDropdown> [ ]
Cards Using <Card> with consistent padding [ ]
Loading states Global loader, no per-page spinners [ ]

6.2 - Layout Standards

Rule Verified
Global padding from AppLayout only (no page-level padding) [ ]
Consistent header height and spacing [ ]
Sidebar navigation states (active, hover) correct [ ]
Responsive breakpoints working (mobile, tablet, desktop) [ ]

7. FUTURE UPDATE RULES

7.1 - Version Numbering

MAJOR.MINOR.PATCH

MAJOR (X.0.0): Breaking changes, major features
MINOR (x.X.0): New features, significant improvements
PATCH (x.x.X): Bug fixes, minor improvements

7.2 - Update Checklist (For Every Release)

[ ] Update CHANGELOG.md with version entry
[ ] Update docs/INDEX.md version number
[ ] Update relevant module docs if changed
[ ] Update API docs if endpoints changed
[ ] Run ESLint and fix violations
[ ] Run TypeScript strict check
[ ] Test affected user flows manually

7.3 - Code Standards (Enforce)

Rule Enforcement
Use design system components ESLint rule
No inline styles (use Tailwind) ESLint rule
TypeScript strict mode tsconfig
No console.log in production ESLint rule
API responses typed TypeScript

7.4 - Documentation Rules

Document Update When
CHANGELOG.md Every release
Module docs Module changes
API ENDPOINTS.md Endpoint added/changed/removed
PAGES.md Route added/changed/removed
Help content User-facing feature changes

SIGN-OFF

Pre-Launch Approval

Role Name Date Signature
Developer
QA
Owner

Notes

Use this space for any issues found during verification:





Document Owner: IGNY8 Team
Next Review: After each major version release