Reactivation Click-Through
peytonworkprojects@gmail.com · 2026-08-22 · plan: docs/testing/click-through/reactivation.md
MIXED — 2 PASS · 2 BLOCKED (plan fixture issue) · 8 NOT RUN
Core fix verified live: a full TMPL-EVBK01 (Event Booking) activation — the exact pipeline
that was broken by #3822/#3823 — completed end to end this sitting: Personalize → Connect → Try → Activate,
landing on Pulse as a running assistant (
ASST-MT3RS76HT47V), then cleanly stopped.
DB confirms status=stopped, activation_count=1.
Screenshots — real, this sitting
Scenario results
| # | Scenario | Result | Notes |
|---|---|---|---|
| CT-REACT-01 | Pulse Past chooser → Reactivate (TMPL-9P3X) | NOT RUN | peyton@mystflo.com scope — needs go-ahead |
| CT-REACT-02 | Pulse Past chooser → Start fresh (TMPL-BRST01) | BLOCKED | TMPL-BRST01 not a real catalog assistant (see below) |
| CT-REACT-03 | Pulse Past "⋮" → Start Fresh, direct bypass | PASS | Wizard opened directly, chooser skipped, as specified |
| CT-REACT-04 | Pulse Past blocked → ReactivationFixModal | NOT RUN | Disconnects real WhatsApp number — awaiting explicit go-ahead |
| CT-REACT-05 | Assistants pre-card → chooser → Reactivate (TMPL-BRST01) | BLOCKED | Same TMPL-BRST01 issue |
| CT-REACT-06 | Assistants pre-card "⋮" → chooser (not direct) | PASS | Chooser opened, confirmed diverges from CT-REACT-03 |
| CT-REACT-07 | Team Permanent direct reactivate | NOT RUN | peyton@mystflo.com scope |
| CT-REACT-08 | Team Permanent blocked, expired credential | NOT RUN | Blocked by TMPL-EVBK01 single-instance constraint |
| CT-REACT-09 | Team Permanent blocked, invalid payment | NOT RUN | Forces real payment failure — awaiting explicit go-ahead |
| CT-REACT-10 | Needs-attention panel inline Reactivate | NOT RUN | Not reached this sitting |
| CT-REACT-11 | Connect-tab swap (Sheet variant) | NOT RUN | Not reached this sitting |
| CT-REACT-11 | Connect-tab swap (WABA variant) | NOT RUN | peyton@mystflo.com scope |
| CT-REACT-12 | Concurrent "Start another" (TMPL-WAITL1) | NOT RUN | Not reached this sitting |
New blockers found
1. TMPL-BRST01 ("Business sections") is not a real catalog assistant.
development_stage IS NULL, persona_slugs=[] — it's part of the Brain-internal
generation engine (TMPL-BR* family), never surfaced in the Assistants catalog. Blocks CT-REACT-02/05 as specified —
the plan's fixture table needs a real multi-instance generation template substituted in. Same class of issue as
the plan's own "TMPL-COHB01 does not exist" note — a plan-authoring correction, not a product bug.
2. TMPL-EVBK01 is single-instance — and the honest-failure fix holds here too.
Activating a second Event Booking instance returned "Assistant already exists... Nothing was created. No
assistant, no workspace, no charge" — a clean, honest block with no orphaned row and no wallet charge. Good
evidence the #3822 fix generalizes. But it means CT-REACT-03/06/08 can't each get independently-stoppable
fixtures as the plan assumes — CT-REACT-03 and 06 shared one fixture this sitting; CT-REACT-08 needs a plan
correction (second template, or a sequential reuse strategy).
Next steps
- Peyton corrects the plan's CT-REACT-02/05/08 fixture assignments.
- Peyton gives explicit go-ahead per scenario before any peyton@mystflo.com walk (CT-REACT-01/04/07/09/11-WABA).
- Next sitting: CT-REACT-10, 11-Sheet, 12 on the WP account — no blockers, just unreached this sitting.
Full findings: docs/testing/click-through/reactivation-findings-2026-08-22.md