Agent Trainer Sprint — GestaltView

Sprint Progress 0 / 5 complete

Revenue Pipeline Flow

📦

Package Gen

Onboarding fields

💳

Payment

Stripe processing

🔑

Key Issued

Auto-generated

⌨️

Key Entry

Client enters key

⬇️

Download

Deliverable asset

🐛 Active Bugs

DEF-02 · BUG-01 LINKED

Persistent Email Prompt During Bundle Viewing

Bug Critical Path · Resolve First

The "Please enter via email" prompt reappears during bundle viewing even after the field was previously filled and data confirmed saved. The buyer email captured on the onboarding screen is not being passed forward to the Generate Package step — the downstream component reads from a local or uninitialized state rather than from the persisted session/context, meaning the save writes to one location and the prompt reads from another.

Root Cause

Confirmed state handoff failure. The email is being written to one data source during onboarding but the bundle view component is reading from a different, uninitialized source — likely a missing or misplaced React Context Provider boundary across route transitions, or a Firestore listener initializing lazily after the prompt check already fires.

Reproduction

1. Enter buyer email on onboarding screen → 2. Save confirmed → 3. Navigate to bundle/Generate Package view → 4. "Please enter via email" prompt reappears despite prior save.

Identify where the email is written on onboarding (local component state, context, Firestore doc) and confirm the package builder reads from the exact same source

If email is stored in React context or Redux store, verify the Provider wraps both onboarding and builder routes — a missing or misplaced Provider boundary will silently drop the value between route transitions

If reading from Firestore, confirm the document listener is active before the builder component mounts — not initialized lazily after the prompt check runs

Add a null/empty guard on the email field that defers the prompt check until after the async read resolves, so a slow fetch does not falsely trigger the modal

Once state handoff is confirmed stable, remove the prompt entirely from the bundle view context — it should never surface there

DEF-01

Selection Highlight Instability in Package Builder

Bug Pre-Revenue Blocker

Selected items in the package builder render with partial highlights, intermittent flashes, and positional "jumping" rather than snapping to a stable, solid selected state. Creates visible unreliability that undermines user trust before reaching checkout.

Root Cause Hypothesis

Selection state is likely being set and then immediately re-evaluated on the same render cycle — causing the highlight to paint, unpaint, then repaint before settling. Classic symptom of: (1) a redundant setState call inside a render-triggered useEffect with the selection array as a dependency, (2) a race condition between local UI state and a syncing async state where a Firestore listener or Redux store update arrives late and overwrites the local optimistic update, or (3) CSS transition conflicts on the .selected class being toggled faster than the transition duration allows.

Reproduction

Open the package builder → select any item → observe highlight behavior on initial click. Look for partial paint, flash, or positional jump before the selected state settles.

Audit the selection handler for any setState calls inside useEffect with the selection array as a dependency — these will loop

Confirm optimistic UI selection is applied before any async write, not after the write resolves

If using CSS transitions on .selected, ensure the class is not being toggled off and back on within the same event cycle

Check for duplicate event listeners — onClick firing twice due to bubbling on a wrapper + child both bound

BUG-01

Package Generator Re-Asks for Buyer Email

Bug Critical Path

The "Generate Package" step prompts for buyer email even though it was captured on the previous onboarding screen. Data handoff between onboarding and generation is broken — state is not persisting across steps.

Root Cause

Missing data handoff between the onboarding screen and the "generate package" action. The buyer email and company name filled earlier are not being passed forward to the generation step.

Reproduction

1. Enter buyer email + company name on onboarding screen → 2. Proceed to "Generate Package" → 3. System re-prompts for buyer email. First-run toggle exhibited intermittent behavior but the reproducible path expects re-entry. The UI repeatedly asks for an email using the prompt: "Please enter via email." This prompt appears even after fixes were applied and after data is saving. Flickering unsettled bundle selections. It commonly surfaces when viewing bundles.

Trace state from onboarding form submission through to generation handler. Impact & required fix. Visual instability (flashing/partial highlights) can confuse users and imply unreliable state. The persistent email prompt blocks expected flow despite saves; needs removal or correct validation.

Confirm onboarding fields are stored in context/state before navigation. Business Name and Email Fields empty when saves are made or progresses to next section

Remove redundant email prompt from generation step

End-to-end test: onboarding → generate → verify no re-prompt

Action Items

AT-01

Define Package Scope & Value Proposition

Todo

Design the content, structure, and deliverables for a larger custom package. The small sample used during testing isn't sufficient for client validation — a proper package needs clear, tangible value.

Session Note

"You want to make sure there's value proposition for what they're getting."

Scope Questions to Resolve

What files, agents, and configs does the client receive? What customization is bespoke vs. templated? How is value communicated at the point of purchase?

AT-02

Split Admin vs. Client Agent Trainer Environments

Todo

The Admin Dashboard Agent Trainer must be strictly separated from the client-facing bespoke trainer. Access controls need to prevent clients from seeing or interacting with the admin trainer at any point.

Session Note

"That's not something they should be seeing or having access to."

Identify all shared routes/components between admin and client trainers

Implement role-based access control (RBAC) on admin trainer routes

Build bespoke client-facing trainer as isolated instance

AT-03

Implement Payment → Key → Download Flow

In Progress Revenue Gate

Build and validate the complete customer-facing transaction: payment processed via Stripe → key auto-issued → client enters key → downloadable asset is delivered. Every step must work before billing is live.

Flow Steps

① Customer pays via Stripe → ② System generates + issues unique key → ③ Customer enters key in portal → ④ System validates key + serves downloadable package asset

Stripe webhook → key generation on successful payment

Key entry UI + validation endpoint

Secure download delivery on valid key redemption

End-to-end test in staging before enabling billing

AT-04

Fix Package Generation Data Flow

In Progress

Resolve the missing state handoff so onboarding fields (buyer email, company name) persist through to the package generation step without requiring re-entry. This is linked to BUG-01 and DEF-02.

Technical Focus

Identify where context drops between the onboarding form and the generation handler. Likely a missing state pass-through or context provider scope issue. Fix ensures the generator always has access to already-collected buyer data.

AT-05

Prototype Basics, Then Scale to Vending Model

Todo

Validate the core pipeline on a small package first. Once the basic flow is stable and tested, build automated generation of code and files to support a vending-machine model that scales to countless client packages.

Session Note

"Let's start with the basics for now."

Scale Plan

Phase 1: Manually validate small package pipeline end-to-end. Phase 2: Automate code/file generation per client config. Phase 3: Vending-machine model — spin up full package assets on demand.

Agent Trainer Package

Revenue Pipeline Flow