# SalesFlowChartPath — design + skeptic corrections (2026-10-06)

> Copied verbatim from the session scratchpad (`scratchpad/ai/journey-design.md`), which is deleted when the session ends.
> This is the DESIGN the class `src/Lead/Journey/Support/SalesFlowChartPath.php` was built from (commit `20e1678cb`).
> The **CORRECTIONS** section at the end overrides the sections above it wherever they disagree.
> The code is the truth; this explains WHY. Review findings against it (all fixed 2026-10-13): [05-review-findings-2026-10-07.md](05-review-findings-2026-10-07.md).

---

## SERVER OR CLIENT
Put the step/event → box mapping in PHP: a new pure class `Src\Lead\Journey\Support\SalesFlowChartPath`, next to `Support\HandoffQuestions`, with static methods. The browser only renders the result. Reasons:

(1) The facts the mapping needs reach PHP but never reach the browser:
- the event log uncapped (toPanelArray caps it at 60 newest, FunnelJourney.php:433), already eager-loaded by buildJourneyRows (LeadsController.php:3086);
- `from_step` / `to_step`, to tell moved from rejected (the browser only gets `moved`);
- `data.source = 'preview_candidate'`, which is the pick→project proof;
- the raw `journey_kind` and `stage`.

(2) The list needs a lead-level answer across ALL of a lead's journeys. chipsForLeads already loads them all (FunnelJourney.php:358-369), so this costs 0 extra queries.

(3) One PHPUnit-tested place serves the page, the modal (including the discussion refresh) and the list, instead of three JS copies.

(4) Do NOT change the existing `flowStage()` / `flow_stage`. `FunnelJourneyAnswer::point()` / `pointFor()` (FunnelJourneyAnswer.php:124-151) route DATA points through it. The bar uses a separate "band" of the current node.

The node ids (and each id's band) are a contract shared with FLOW_CHART (salesFlowGuide.js:28-81). Guard it with one vitest that reads the PHP NODES const and compares it with FLOW_CHART.stages. The client keeps FLOW_CHART for titles and labels only.

## STEP -> CURRENT NODE
- registered (journey.stage 1) [preview] -> start (stage 1) — Also the seed node of every Preview journey, including one opened without a `registered` event (import / walk-in, FunnelJourneyRecorder.php:105-112).
- welcome_sent [preview] -> welcome (stage 1)
- offer_sent (M2) [preview] -> clicked (stage 1) — There is no M2 box. The lead is waiting on the 6-hour click question (STEPS 'waits', FunnelJourney.php:89). ai1, answered and m3 stay grey.
- ai_call_pending (stage 1) [preview] -> ai1 (stage 1) — Only a funnel-rule call writes ai_call_placed (SendFunnelAiCall.php:236). A callback call never does, so the callback path is aiBack (see callback_clicked).
- ai_call_answered (stage 1) [preview] -> useful (stage 1) — The scanner decides 'useful?' at once (HandOffAfterAiCall.php:55-61, :76-90). If a callback came first, the event walk shows aiBack as passed instead of answered.
- ai_call_missed (stage 1) [preview] -> answered (stage 1) — Waits for M3 or the hand-off. In the event walk, a miss on the CALLBACK call leaves aiBack as current.
- missed_sent (stage 1) [preview] -> clicked (stage 1) — M3 was sent and the lead is waiting on the click (waits, 6 h).
- callback_clicked (stage 1) [preview] -> aiBack (stage 1) — The step stays callback_clicked while the callback call rings (FunnelJourneyHooks.php:423-433).
- human_pending (stage 1) [preview] -> task1 (stage 1)
- human_done (stage 1) [preview] -> preview (stage 1) — Waiting for the Preview webinar.
- not_called [preview] -> preview (stage 1) — The task expired at webinar start (ExpireCallAtWebinarStart, stage 1 only). task1 shows as passed even though nobody called; see gaps.
- reminders [preview] -> preview (stage 1) — ai_handled before the webinar (Repo TRANSITIONS :40).
- attended [preview] -> paidMember (stage 2) — Waiting on 'paid?' (UnpaidAfterWebinar fires 120 min after the end, Rules/UnpaidAfterWebinar.php:44-46).
- no_show [preview] -> noShow (stage 2)
- unpaid [preview] -> unpaid (stage 2) — Only on the ATTENDED branch. unpaid is also accepted from no_show (Repo ONLY_FROM :112), and on that branch the node is noShow. The event walk uses the verdict of the current cycle. The step-only map (list) uses attended_at.
- ai_call_pending / ai_call_answered / ai_call_missed / missed_sent / callback_clicked (journey.stage 2) [preview] -> unpaid | noShow (stage 2) — This is the after-webinar follow-up call (ONLY_FROM_AFTER_WEBINAR, Repo :133-138). The noShow and unpaid boxes already contain 'AI 打电话 / 没接：发 M4'. Branch: unpaid if attended, else noShow.
- human_pending (stage 2) [preview] -> task2 (stage 2)
- human_done (stage 2) [preview] -> pick (stage 2) — Waiting for an admin to pick the lead for the Project webinar.
- followed_up [preview] -> pick (stage 2) — The AI follow-up got the answers, so task2 is skipped. The chart has no noShow/unpaid→pick edge.
- paid [preview] -> rep1 (stage 2) — TRAP: paying before the verdict keeps journey.stage=1 and flow_stage=1 (Repo TRANSITIONS :48 sets no stage). The bar must read the node's band (2), not flow_stage.
- rep_assigned [preview] -> rep1 (stage 2) — Same trap: it can be stage 1.
- zoom_pending [preview] -> rep1 (stage 2) — Zoom booked but not held yet.
- zoom_done [preview] -> pick (stage 2) — rep1 is passed (the rep1→pick edge exists).
- won / lost / journey.stage 3 [preview] -> (unreachable) (stage 2) — Preview journeys are never closed: closed_* is recorded only on Project journeys (FunnelJourneyHooks.php:721). Fallback: treat as ended and keep the last band.
- registered, welcome_sent, offer_sent, ai_call_pending, ai_call_answered, ai_call_missed, missed_sent, callback_clicked, human_pending, human_done, not_called, reminders (journey.stage 1) [project] -> project (stage 2) — All of the Project funnel's own pre-webinar automation collapses onto the 'project' moment box (gap). flowStage() is 2 here too (FunnelJourney.php:335-336).
- attended [project] -> paidFee (stage 3) — Waiting on 'paid project fee?' (120-min unpaid clock).
- no_show [project] -> follow3 (stage 3) — paidFee is passed via the '没来 / 没付' edge. Cold no-shows only get a WhatsApp and stay here (readMe §3c).
- unpaid [project] -> follow3 (stage 3)
- ai_call_pending / ai_call_answered / ai_call_missed / missed_sent / callback_clicked (journey.stage 2) [project] -> follow3 (stage 3)
- human_pending (stage 2) [project] -> task3 (stage 3)
- human_done (stage 2) [project] -> paidFee (stage 3) — There is no box after task3 in FLOW_CHART, so the open question 'paid project fee?' becomes current again (a revisit). See gaps.
- followed_up [project] -> paidFee (stage 3) — Same as human_done: a revisit of paidFee.
- paid [project] -> rep2 (stage 3) — TRAP: paying before the Project webinar's verdict keeps journey.stage=1 and flow_stage=2, but the node band is 3.
- rep_assigned [project] -> rep2 (stage 3)
- zoom_pending [project] -> rep2 (stage 3)
- zoom_done [project] -> closed (stage 3) — The REP still has to mark the deal Booked / Not closed.
- won [project] -> closed (stage 3) — ENDED: no current box. 'closed' counts as PASSED. Outcome Booked (STATUS_WON).
- lost [project] -> closed (stage 3) — ENDED: no current box. 'closed' counts as passed. Outcome Not closed (+ lost_reason). A new registration reopens the journey (FunnelJourneyRecorder.php:145-147), which starts a new cycle at 'project'.
- stopped [any] -> (none) (stage 0) — Never written: EVENT_STOPPED has no caller. Handle it as ENDED with outcome 'stopped', and keep the band of the last path node.

## EVENT -> PASSED NODES
- registered (to_step = registered, i.e. accepted) [preview] ->  — Starts a NEW cycle. The walk throws away the earlier path; current = start. A rejected registered (lead already paid or with a REP, Repo ONLY_FROM :87) has to_step = from_step and is ignored.
- reopened [any] ->  — Starts a new cycle, the same way as registered. It only follows LOST/STOPPED, so in practice it only happens on Project journeys.
- welcome_sent [preview] -> start — current → welcome
- offer_sent [preview] -> start, welcome — welcome only if it was entered. current → clicked (there is no M2 box).
- ai_call_placed (journey.stage 1) [preview] -> welcome — The previous box (welcome, or start) becomes passed. current → ai1.
- ai_call_refused (journey.stage 1) [preview] -> ai1 — The call never rang, so ai_call_placed was never recorded. Enters ai1 and answered; current → answered.
- ai_call_answered (journey.stage 1) [preview] -> ai1, answered — Lights the 接了 edge; current → useful. After a callback the passed node is [aiBack] (no 'answered'), and current → useful.
- ai_call_missed (journey.stage 1) [preview] -> ai1 — current → answered. If the missed call was the callback call: nothing new, aiBack stays current until the hand-off.
- missed_message_sent (journey.stage 1) [preview] -> answered, m3 — Lights 没接; current → clicked.
- callback_clicked (journey.stage 1) [preview] -> clicked — Lights 按了 when it came from m3/clicked; current → aiBack.
- ai_handled (journey.stage 1 → reminders) [preview] -> useful — Lights 有; current → preview.
- handed_to_human (journey.stage 1) [preview] -> useful | clicked | answered | aiBack | welcome — Whichever box was current becomes passed. Lights 没有 (from useful) or 没按 (from clicked). current → task1. A reopened task (from human_done) makes task1 current again.
- human_attempt [any] ->  — Log only (Repo TRANSITIONS :42).
- human_done (journey.stage 1) [preview] -> task1 — current → preview
- human_expired [preview] -> task1 — current → preview. The call never happened (step not_called); see gaps.
- reminder_sent [any] ->  — Log only.
- webinar_attended (moved) [preview] -> preview, came — Lights 来了; current → paidMember. If REJECTED because the journey was already on the paid path (from_step ∈ paid/rep_assigned/zoom_pending/zoom_done), splice 'came' in right after 'preview' as a fact (attended_at is stamped regardless, Repo :340-341) and do not move current. Ignore a move=false verdict about an older session.
- webinar_no_show (moved) [preview] -> preview, came — Lights 没来; current → noShow.
- paid [preview] -> paidMember — Lights 付了; current → rep1 (band 2) even while journey.stage = 1. A rejected second payment is ignored.
- payment_refunded [any] ->  — Log only. The path keeps paidMember / paidFee (see gaps).
- unpaid [preview] -> paidMember — Attended branch: lights 没付; current → unpaid. No-show branch: nothing new, noShow stays current.
- ai_call_placed / ai_call_answered / ai_call_missed / ai_call_refused / missed_message_sent / callback_clicked (journey.stage 2) [preview] ->  — The after-webinar follow-up. It keeps or makes the branch box current (noShow, or unpaid with paidMember passed). It never re-enters the stage-1 boxes.
- ai_handled (journey.stage 2 → followed_up) [preview] -> noShow | unpaid — current → pick. There is no chart edge for this.
- handed_to_human (journey.stage 2) [preview] -> noShow | unpaid — current → task2
- human_done (journey.stage 2) [preview] -> task2 — current → pick
- rep_assigned [preview] ->  — rep1 is already current (it was entered at paid).
- zoom_scheduled [preview] ->  — rep1 stays current.
- zoom_done [preview] -> rep1 — current → pick
- candidate_marked (log only, on the Preview journey) [preview] -> task2 | rep1 | noShow | unpaid | paidMember — Whatever was current becomes passed; current → pick. At lead level, pick is PASSED as soon as a Project journey exists.
- closed_won / closed_lost [preview] ->  — Never recorded on Preview (FunnelJourneyHooks.php:721).
- stopped [any] ->  — Never written. If it were, the journey is ended with outcome 'stopped'.
- note [any] ->  — Log only (template button tap).
- registered (accepted), data.source = 'preview_candidate' [project] -> pick — New cycle. Lights pick→project; current → project. Any other source: nodes [] and current → project.
- welcome_sent / offer_sent / ai_call_* / missed_message_sent / callback_clicked / ai_handled / handed_to_human / human_done / human_expired (journey.stage 1) [project] ->  — There are no chart boxes for this; 'project' stays current (gap).
- webinar_attended (moved) [project] -> project — current → paidFee. A rejected attended (lead already paid) adds nothing.
- webinar_no_show (moved) [project] -> project, paidFee — Lights 没来 / 没付; current → follow3.
- paid [project] -> project, paidFee — Lights 付了; current → rep2 (band 3) even before the verdict.
- unpaid [project] -> paidFee — current → follow3
- ai_call_placed / ai_call_answered / ai_call_missed / ai_call_refused / missed_message_sent / callback_clicked (journey.stage 2) [project] -> paidFee — current → follow3 (no-op if it is already there).
- handed_to_human (journey.stage 2) [project] -> follow3 — current → task3
- human_done / ai_handled (journey.stage 2) [project] -> task3 | follow3 — current → paidFee (a revisit; FLOW_CHART has no box after task3).
- rep_assigned / zoom_scheduled [project] ->  — rep2 stays current.
- zoom_done [project] -> rep2 — current → closed
- closed_won [project] -> closed — ENDED (outcome Booked): there is no current box.
- closed_lost [project] -> closed — ENDED (outcome Not closed + lost_reason).

## BUILD PLAN
## Build plan: lead sales-flow bar + highlighted chart

### 0. Concepts
- **node**: a FLOW_CHART id (salesFlowGuide.js:28-81).
- **band**: the 1/2/3 stage band of a node:
  - 1 = start, welcome, ai1, answered, useful, m3, clicked, aiBack, task1, preview
  - 2 = came, noShow, paidMember, unpaid, task2, rep1, pick, project
  - 3 = paidFee, follow3, task3, rep2, closed
- **path**: the ordered list of nodes the lead entered, with repeats allowed.
  - current = last node (unless ended)
  - passed = set(path) − current
  - lit arrows = consecutive pairs, in the same `from-to` key format as SalesFlowChart.vue:51
- The bar reads `band(current)`. It **never** reads `flow_stage`, which is wrong for paid-before-verdict (Repo TRANSITIONS :48).

### 1. Server: `src/Lead/Journey/Support/SalesFlowChartPath.php` (new, pure static)
```php
public const NODES = ['start' => 1, /* … 24 ids … */ 'closed' => 3];
public static function nodeFor(FunnelJourney $j): ?string;            // step table (list + fallback)
public static function pathFor(FunnelJourney $j): array;              // {kind, path[], node, ended, outcome} from $j->events
public static function forLead(iterable $journeys, bool $withPath): ?array; // {path[], node, band, bands[3], ended, outcome}
```

**`nodeFor()`** is the step_to_current_node table. Its inputs are kind + `stage` + `step` + `attended_at` + `status`.

**`pathFor()`** walks `$j->events`, which are id-ordered (FunnelJourney.php:502). Order by id because `created_at` can be backdated.
- **Cycle start:** begin at the LAST `registered` or `reopened` event whose `to_step === 'registered'`.
- **Seed:** `[start]` for a Preview journey. For a Project journey, `[project]`, or `[pick, project]` when that registered event's `data.source === 'preview_candidate'`.
- **Effective event:** an event counts when `to_step !== from_step`. Three exceptions are used even though they do not move the step:
  - `candidate_marked`, which enters pick;
  - a `webinar_attended` rejected from the paid path (paid, rep_assigned, zoom_pending, zoom_done), which splices `came` after `preview`;
  - the cycle-start registered.
- **State the walk tracks:**
  - `stage`: becomes 2 on a moved attended/no_show and 3 on closed_*.
  - `branch`: came or noShow.
  - `lastAi`: ai1 or aiBack.
- **Entering a list of nodes:** append each node unless it is already in the path. The LAST node is always appended unless it equals the current node.
- **Reconcile:** if the journey is active and `band(walk node) ≠ band(nodeFor())`, append `nodeFor()`. This is a safety net for unknown or new events.
- **Ended:** status WON, LOST or STOPPED → `ended = true`, outcome = `won`, `lost` or `stopped`.

**`forLead()`** combines the journeys into one path:
- Pick one Preview and one Project journey. For each kind: active first, then `step_since` desc, then id desc, which is the existing order (FunnelJourney.php:367).
- **Lead re-entered the flow:** if the Project journey is closed and the Preview journey's cycle started after the Project's `closed_at`, use the Preview journey alone.
- Otherwise `path = preview.path ++ project.path`, dropping the Project path's first node when it equals the Preview path's last node.
- `node` and `ended` come from the Project journey when there is one (a superseded Preview journey's current box becomes passed); else from the Preview journey.
- `bands[i]`:
  - `current` when i = band, and `todo` when i is after it;
  - `done` when i is before the band and the path has a node of band i, else `skipped`;
  - when the flow has ended: bands 1–2 are `done` and band 3 is the outcome (`won` or `lost`).
- With `$withPath=false` (the list), path is `[]`. Band 1 is `done` if a Preview journey exists, else `skipped`; band 2 is `done` whenever band 3 is current.

### 2. Server wiring (all 0 new queries)
- **`FunnelJourney::toChipArray()`** (:380-418): add `kind` (raw journey_kind), `stage` (int) and `flow_node` (from `nodeFor`). Keep `flow_stage` as it is.
- **`FunnelJourney::chipsForLeads()`** (:366-369): add `'lead_flow' => SalesFlowChartPath::forLead($journeys, false)` to the chosen chip.
  - Do NOT add `->with('events')`: that has no cap and would load every event row.
  - The list row stays `journey` (LeadsController.php:1055). Never use the row-level `stage` key; it is the LeadStages ladder (:4422).
- **`LeadsController`:**
  - Split `buildJourneyRows()` (:3079) into `loadJourneys(Lead): Collection` (today's query + `events.actor.profile` eager load) and `buildJourneyRows(Collection)`.
  - At :2217 (show), :2494 (quick?section=discussion) and :2943 (quick), add `'journeyFlow' => SalesFlowChartPath::forLead($journeys, true)` next to `journeys`. The modal's `Object.assign` (LeadDetailModal.vue:164) then keeps it live after a call is logged.

### 3. Client
- **`SalesFlowChart.vue`** (stays in Pages/Manage/MyWork/Partials; JourneyTab imports it across pages, the same precedent as LeadDetailModal.vue:38).
  - New props, all defaulting to off: `path: Array = []`, `ended: Boolean = false`, `maxHeight: Number|null`. The bare `<SalesFlowChart />` in MyWork/SalesFlow.vue:60 must render exactly as today.
  - Node classes (:149-153) → `nodeClass(node)`. In highlight mode REPLACE the WHO fills, because WHO.rep is already emerald and WHO.you already brand (salesFlowGuide.js:17-18):
    - passed: emerald-500 border + emerald-50 fill, with a check icon;
    - current: brand-600 border + ring, a 现在 tag and `aria-current="step"`;
    - rest: `opacity-40 grayscale`.
  - Lit edges (`stroke-emerald-500`, width 2.5) and a second arrow marker.
  - Marker ids per instance via `useId()` (Vue 3.5.35). Today the id is the fixed `sales-flow-arrow` (:116), and the page and the global modal can be in the DOM together.
  - Add `data-flow-node` and `data-state` attributes for tests.
  - The `maxHeight` viewport scrolls its OWN `scrollTop` to the current node (no `scrollIntoView`).
- **`resources/js/Components/Leads/SalesFlowProgress.vue`** (new).
  - Props: `flow` (journeyFlow or lead_flow), `compact: Boolean`.
  - An `<ol>` of 3 chevrons (geometry copied the PathMap way, not by reusing StageTabs).
  - Labels come from `FLOW_CHART.stages[i].label`.
  - States: done = emerald-600 + check; current = brand-600 + 现在; todo = slate-200; skipped = slate-200 + tooltip "没有记录"; won = emerald; lost = slate-500 + "Not closed".
  - The non-compact bar adds a line "现在：{FLOW_CHART node title}".
  - Emits `open`.
  - Compact mode: 3 small pills plus an sr-only "第 N 段 / 3".
- **`Show.vue`:**
  - Add the prop `journeyFlow: { type: Object, default: null }` next to `journeys` (:141-142).
  - Mount `<SalesFlowProgress v-if="!aeSuite && journeyFlow" :flow="journeyFlow" class="mb-6" @open="activeTab='sales'; activeSalesTab='journey'" />` between the header's close (:456) and `<!-- Tabs -->` (:458).
  - At :534, use `<JourneyTab :journeys="journeys" :flow="journeyFlow" />`.
- **`LeadDetailModal.vue`:**
  - Same bar after the AM/funnels strip (:566-596) and before `<ShowTabs` (:598), bound to `data.journeyFlow`, with the same `activeTab` / `activeSalesTab` jump (:340, :342).
  - At :671, add `:flow="data.journeyFlow"`.
  - Do NOT add any `<ShowTabs` literal: useLeadTabs.test.js requires exactly 5.
- **`JourneyTab.vue`:**
  - New prop `flow`.
  - Inside the `v-else` (:49) and before the per-funnel `v-for` (:50), add ONE lead-level "流程图" card:
    - a legend (绿 = 走过 · 蓝 = 现在 · 灰 = 还没到);
    - `<SalesFlowChart :path="flow.path" :ended="flow.ended" :max-height="520" />`;
    - a 显示全部 toggle.
  - No chart per card.
- **`JourneyCell.vue`:**
  - Put `<SalesFlowProgress compact :flow="journey.lead_flow" />` before the chip (:43-54), in an `inline-flex gap-1.5` wrapper.
  - The hover card (:56-96) gets the full bar line.
  - Same column, so there is no Index.vue column change.

### 4. Tests (proportionate)
- **PHPUnit:** 2 methods in `tests/Feature/Lead/FunnelJourneyTest.php`, next to :725-755.
  - (a) Preview landing → AI answered and useful → attended → paid, then picked From Preview onto a Project session. Assert `/quick` `journeyFlow.path` contains `came`, `paidMember`, `rep1`, `pick`, `project`, plus `journeyFlow.node` and `journeyFlow.band == 2`; and assert the list row `journey.lead_flow.band`.
  - (b) The trap: paid BEFORE the attendance verdict → `node` `rep1` and band 2 while `flow_stage` is still 1, and `came` is spliced in.
- **vitest:**
  - SalesFlowChart with `path` sets `data-state` passed/current/idle; the bare chart has no `data-state`.
  - A parity test: the PHP `NODES` ids and bands equal FLOW_CHART.stages.
- **Run** `npx vitest run` on those files plus `useLeadTabs.test.js` and `Index.slots.test.js`, then phpunit on FunnelJourneyTest.php only.

### 5. Docs (same change)
- `docs/modules_handbook/manage/leads/funnel-journey/readMe.md`:
  - §6 "Where it shows" gets the bar, the chart and `lead_flow`.
  - New §6d: the step → box table, the cycle rule and the combination rule.
  - Related files gets SalesFlowChartPath.php and SalesFlowProgress.vue.
- `docs/modules_handbook/manage/my-work/readMe.md`: the chart is now also on the lead's Journey tab.
- `docs/modules_handbook/manage/leads/readMe.md`: the Show header, the modal strip and the list Journey column.

### 6. Cautions
- Show.vue, LeadDetailModal.vue and Leads/Index.vue are already modified by other sessions. Re-read them right before editing.
- All the journey files are untracked (`??`).
- Hide the bar in the AE suite, the same way the Journey tab is hidden (useLeadTabs.js:130).
- Hide the bar when `journeyFlow` is null: no tracked journey, or a lead from before 2026-10-04 (there is no backfill).

## GAPS
- M2 (offer_sent, the 'let the AI call you' message sent to someone who unticked the AI call) has no box. It is mapped to `clicked`, and ai1, answered and m3 stay grey. There is no welcome→clicked edge, so no arrow lights up.
- The Project funnel's own pre-webinar automation (welcome, AI call, missed message, hand-off task, reminders, not_called) has no boxes, so all of it collapses onto `project`. The code already files those calls as 'DATA 3 / DATA 4 · Stage 2' (FunnelJourneyAnswer::point with flowStage 2), which looks like noShow/task2 but sits before `project` on the chart. Owner: add boxes, or accept 'project' as current.
- FLOW_CHART has no box after task3 (and no edge from follow3/task3 onward). A Project lead whose follow-up is done (human_done or followed_up) and still unpaid is shown with `paidFee` current again (a revisit). Owner may want an explicit 'waiting for payment / end' box.
- Preview `followed_up` (the AI follow-up got the answers) goes noShow/unpaid → pick, but the chart has no such edge, so no arrow lights. The same applies to a missed callback call: aiBack → task1 has no edge.
- not_called (the task expired at webinar start) and human_expired show task1 as PASSED (green) although nobody called. The owner's three colours cannot say 'skipped / missed'. Decide whether to add a fourth state, or a strike-through on that box.
- Re-registering for a later session restarts the journey (Repo ONLY_FROM :87; Recorder :136-162). The design shows only the CURRENT cycle, so an earlier session's boxes (e.g. a no-show) disappear from the chart but stay in the log. Owner decision: keep it this way, or show earlier cycles faded.
- A lead with several Preview funnels or several Project journeys feeds only ONE of each kind into the lead-level bar and chart (active first, then the latest step_since). The others appear only as cards.
- A lead who reached 第2/第3段 without a Preview journey (imported or admin-added Project registrant, From-Preview pick of someone whose Preview was untracked, or leads from before 2026-10-04) shows the earlier bands as 'skipped' (grey, 'no record'), not done. Owner may prefer 'done'.
- A Lost Project journey followed by a new Preview registration: the plan uses the Preview journey alone when its cycle started after the Project's closed_at. This rule is my proposal, not owner-decided.
- payment_refunded only clears paid_at and does not move the step (Repo :344-345). The path keeps paidMember/paidFee and rep1/rep2 green, and the bar still reads 付了.
- STEP_STOPPED / EVENT_STOPPED / STATUS_STOPPED are never written (EVENT_STOPPED has no caller). 'Ended + outcome stopped' handling exists only for completeness.
- The existing `flow_stage` and `journeyStageLine()` ('Preview webinar · Stage N', funnelJourney.js:53-56, shown on the cards and the list hover) will disagree with the new bar for paid-before-verdict leads (flow_stage 1 vs band 2). flowStage() must stay because DATA-point routing depends on it. Decide whether the card/hover line should switch to the band, or drop 'Stage N'.
- In the list, the node comes from the step-only map. It is band-accurate, but noShow vs unpaid uses attended_at, which survives across cycles, and it cannot see aiBack. Only the band pills are shown there, so this is acceptable. The page and modal use the event walk.
- 'paid before the webinar happened' while the lead sits at reminders makes `preview` green (passed) before the webinar took place. This is minor; the alternative is to not mark preview passed until a verdict.
- A superseded Preview journey's current box (for example task2 with an open call task) is shown as PASSED once a Project journey exists. Its open task still shows on its card and in My Work, but the chart will not show it in blue.
- Bilingual rule: the bar and chart reuse FLOW_CHART's Chinese labels (a staff guide, manage-side). The CLAUDE.md bi()/tx() rule covers member-facing learning copy, so it does not apply. Confirm the staff-only scope stays.

## CORRECTIONS
- [skeptic 1] event_to_passed_nodes: welcome_sent (preview), together with the build plan's rule that an event counts only when to_step !== from_step: WRONG The welcome box is entered only by a welcome_sent event that moved the step. If the AI call is placed first, the welcome is ignored: it stays grey and the path reads start → ai1, with no lit edge. → RIGHT Treat welcome_sent as a fact, the same way the plan already splices a rejected webinar_attended. Enter 'welcome' right after 'start' whenever a welcome_sent event exists in the cycle, whatever its to_step.
    evidence: welcome_sent only moves from `registered` (FunnelJourneyRepository.php:88). ai_call_placed moves from any STEPS_AUTOMATION step, `registered` included (:90). If the AI call lands first, the step is ai_call_pending and the later welcome_sent is logged with to_step = from_step (:316-321, :356). The two are independent queue jobs fired at the same moment: SendFunnelWhatsAppMessage::dispatch with no delay (DispatchFunnelWelcomeAction.php:115), and SendFunnelAiCall::dispatch with the delay set to null when the rule has none (:182-183). The repository itself says 'the welcome send and the AI call fire seconds apart' (FunnelJourneyRepository.php:186-188).
- [skeptic 1] event_to_passed_nodes: candidate_marked note 'At lead level, pick is PASSED as soon as a Project journey exists'; step_to_current_node: human_done (stage 2) / followed_up / zoom_done (preview) → pick; build plan forLead() concatenation: WRONG 'pick' is used as a WAITING box (current) for human_done(2), followed_up and zoom_done. Once the lead leaves it any other way, it turns PASSED (green). That happens when they pay, when a second after-webinar AI call drags followed_up back, or when forLead() glues on a Project path seeded [project]. The design also says pick is passed whenever a Project journey exists. Either way the chart claims an admin picked the lead when nobody did. → RIGHT Mark 'pick' PASSED only on proof:
- the Project journey's cycle-start registered event has data.source === 'preview_candidate';
- or a candidate_marked event exists on the Preview journey.
A waiting 'pick' that the walk leaves by any other event should be dropped from the path, not counted as passed. In forLead(), do not keep the Preview path's trailing waiting 'pick' when the Project path is seeded [project] only.
    evidence: Only candidateRegistered writes source 'preview_candidate' (FunnelJourneyHooks.php:137-145) and candidate_marked (:152-158). A Project landing registrant gets source 'landing' (Hooks :104; HandOffWhenAiNeverReached.php:77). 'The CSV import stays as the fallback for people who never came through the Preview' (funnel-journey/readMe.md:266). followed_up is in STEPS_AFTER_WEBINAR (FunnelJourney.php:143-145), so a later after-webinar AI call moves it (ONLY_FROM_AFTER_WEBINAR, Repo :134). paid moves from human_done and followed_up (Repo :116).
- [skeptic 1] event_to_passed_nodes: candidate_marked (log only, on the Preview journey) → 'current → pick': WRONG candidate_marked makes 'pick' the CURRENT box, meaning 'waiting for an admin to pick'. → RIGHT candidate_marked proves the pick already HAPPENED: the lead was registered on a Project session. Enter 'pick' as passed and make 'project' current. This matters when the Project funnel is untracked: then no Project journey exists, and the Preview path is the only one.
    evidence: The event's label is 'Registered for the Project webinar' (FunnelJourneyEvent.php:85). It is written after the Project registration exists (FunnelJourneyHooks.php:130-160). It is logged on the Preview journey even when the Project funnel is not tracked: the Project journey opens only `if tracks($funnelId)` (:136), but the candidate_marked write at :152-158 is outside that check.
- [skeptic 1] build plan forLead(): '`node` and `ended` come from the Project journey when there is one'; 'Lead re-entered the flow' only when the Project journey is CLOSED: WRONG An ACTIVE Project journey always wins. A lead who no-showed or did not pay at a Project webinar months ago, and has now registered for a Preview webinar again, is shown at 第3段 (follow3 / paidFee). The new Preview cycle is glued in front of an old Project path. → RIGHT Choose the lead-level journey by the most recent cycle start (the latest accepted registered/reopened event, else created_at). Do not prefer Project merely because one exists. Apply the 're-entered' rule to active Project journeys too, comparing the Preview cycle start with the Project's last move.
    evidence: A Project journey closes only when a deal it provably owns turns Booked or Lost (FunnelJourneyHooks.php:697-730, journeyOwnsDeal :742-754). 'A Booked deal made by hand … leaves the journey open' (readMe.md:142). EVENT_STOPPED has no caller. So no_show, unpaid, followed_up and human_done Project journeys stay ACTIVE indefinitely. A Preview `registered` restarts that journey from any before- or after-webinar step (Repo ONLY_FROM :87). The list chip already picks the journey with the latest step_since (FunnelJourney.php:366-368). So the list chip would show the new Preview cycle while the bar shows Project 第3段.
- [skeptic 1] event_to_passed_nodes: webinar_no_show (moved), preview and project, when it is later corrected by webinar_attended: WRONG An inferred no-show enters noShow (Preview), or paidFee and follow3 (Project). A real 'attended' that arrives later moves the journey on, and the walk then shows noShow / follow3 as PASSED (green), as if the lead had not come. → RIGHT If a webinar_attended for the same registration or event_id moves the journey out of no_show or unpaid, remove the no-show branch box from the passed set. Keep it only if an after-webinar AI call or hand-off actually ran from it.
    evidence: SettleAttendanceAfterWebinar records an inferred no_show (data.inferred) when the registration has no verdict (Rules/SettleAttendanceAfterWebinar.php:90-97), and documents that 'a real verdict arriving later still wins' (:23-25). webinar_attended moves a journey from no_show and unpaid (Repo ONLY_FROM :110, which includes STEPS_AFTER_WEBINAR).
- [skeptic 1] step_to_current_node: registered (preview) note 'Also the seed node of every Preview journey, including one opened without a registered event (import / walk-in)'; build plan seed `[start]`: WRONG Every Preview journey is seeded with 'start', so imported, admin-added and walk-in people show '客户在 landing page 报名' as passed or current. → RIGHT Seed 'start' only when the cycle starts with a `registered` event whose data.source is 'landing'. A journey opened by a reminder or an attendance verdict has no sign-up box: band 1 starts at 'preview' (or shows 'skipped').
    evidence: The start node's title is '客户在 landing page 报名' (salesFlowGuide.js:33). 'Admin adds, imports and Zoom-side registrations do not come through here … their journey opens later, when the first reminder or the attendance verdict reaches them' (FunnelJourneyHooks.php:71-74; FunnelJourneyRecorder.php:86-112). HandOffWhenAiNeverReached::cameThroughLanding() uses exactly this test: a `registered` event with source 'landing' (Rules/HandOffWhenAiNeverReached.php:66-78).
- [skeptic 1] event_to_passed_nodes: ai_call_refused (journey.stage 1); callback_clicked with data.refused: WRONG A refused call marks 'ai1' passed (and 'answered'). A refused callback marks 'aiBack' passed. Both show the lead as called by the AI. → RIGHT A refused call never rang. Handle it like not_called: do not paint ai1 or aiBack green, or flag it as 'refused / 没打出去'. Add it to the gaps next to not_called / human_expired.
    evidence: SendFunnelAiCall's hook records EVENT_AI_CALL_REFUSED INSTEAD of ai_call_placed when the call is STATUS_FAILED (FunnelJourneyHooks.php:287, :296). Refused lands on step ai_call_missed (Repo TRANSITIONS :37). Refusal rows never get the missed-call M3 (AiCallAftermath.php:53-56, :79). callbackClicked still records callback_clicked, and so moves the step, for a refused call (data.refused, Hooks :426-431).
- [skeptic 1] event_to_passed_nodes: ai_call_missed (journey.stage 1) note 'If the missed call was the callback call: nothing new, aiBack stays current until the hand-off': WRONG The note assumes that after a missed callback call only the hand-off can follow. → RIGHT A missed callback call can trigger M3 again, which moves the step to missed_sent and has the scanner wait for a click again. The walk must then enter m3 → clicked after aiBack (a revisit), not keep aiBack current.
    evidence: AiCallAftermath::settled() records aiCallMissed and then dispatches SendAiCallFollowUp KIND_MISSED for ANY lead call that rang, the callback call included (AiCallAftermath.php:76-110). That send is capped only at one per lead per day (SendAiCallFollowUp.php:150-158). missed_message_sent moves from ai_call_missed (Repo ONLY_FROM :95), and missed_sent is a 'waits' box (FunnelJourney.php:93).
- [skeptic 1] event_to_passed_nodes: handed_to_human (journey.stage 1) nodes 'useful | clicked | answered | aiBack | welcome': WRONG The list of boxes a stage-1 hand-off can come from is incomplete. → RIGHT Add 'start' (from step registered) and 'ai1' (from ai_call_pending when the call's outcome never arrived). Neither has an edge to task1, so no arrow lights.
    evidence: HandOffWhenAiNeverReached fires from registered OR welcome_sent (Rules/HandOffWhenAiNeverReached.php:41). HandOffAfterAiCall fires from ai_call_pending, callback_clicked and ai_call_missed after the wait (Rules/HandOffAfterAiCall.php:32-36, :64-65). ONLY_FROM handed_to_human accepts every STEPS_AUTOMATION step plus human_done (Repo :105).
- [skeptic 1] event_to_passed_nodes: webinar_attended rejected on the paid path → 'splice came in right after preview': WRONG This assumes 'preview' is already in the path. → RIGHT 'paid' is accepted from ANY before-webinar step (task1, ai1, clicked …), so 'preview' may never have been entered. Splice the pair [preview, came] after the last band-1 node (before paidMember), not 'came' after 'preview'.
    evidence: ONLY_FROM paid = STEPS_BEFORE_WEBINAR + STEPS_AFTER_WEBINAR (Repo :116). STEPS_BEFORE_WEBINAR includes human_pending, ai_call_pending, missed_sent and the rest (FunnelJourney.php:130-133). attended_at is stamped regardless of the move (Repo :340-341).
- [skeptic 1] event_to_passed_nodes: paid (project) nodes [project, paidFee]; webinar_attended rejected (project) 'adds nothing': WRONG Paying before the Project webinar marks the 'project' webinar box PASSED before it happened. The gaps list names this defect only for Preview ('preview' green). A later rejected Project attendance is also dropped, although it is a recorded fact. → RIGHT Add the Project case to the same gap: for a stage-1 Project journey (attended_at null), 'project' should not read as attended. When the Project journey later gets a webinar_attended rejected from the paid path, keep it as a fact (attended_at), consistent with the Preview 'came' splice.
    evidence: paid sets no stage (Repo TRANSITIONS :48) and moves from any before-webinar step (:116). A Project journey at stage 1 still has flowStage 2 (FunnelJourney.php:335-336). webinar_attended is not accepted from paid, rep_assigned, zoom_pending or zoom_done (Repo :110), but attended_at is stamped anyway (:340-341).
- [skeptic 2] event_to_passed_nodes: welcome_sent (and the plan's 'Effective event = to_step !== from_step' rule): WRONG welcome is entered only when welcome_sent MOVED the step. A rejected welcome_sent is ignored, so 'welcome' stays grey. → RIGHT Treat welcome_sent as a fact even when it was rejected. ONLY_FROM accepts it only from 'registered', so whenever the AI call (ai_call_placed), the M2 (offer_sent) or a callback click lands first, the M1 that really went out is logged with to_step = from_step. Splice 'welcome' right after 'start' for any welcome_sent in the cycle, the same way 'came' is spliced for a rejected attended.
    evidence: FunnelJourneyRepository.php:88 (ONLY_FROM welcome_sent = [STEP_REGISTERED]); :186-189 (open() doc: 'the welcome send and the AI call fire seconds apart'); :352-362 (a rejected event is still written, to_step = from_step); FunnelJourneyHooks.php:214-234 (whatsappSent, a queued send); SendFunnelAiCall.php:236 (a separately queued call).
- [skeptic 2] event_to_passed_nodes: handed_to_human (journey.stage 1), nodes 'useful | clicked | answered | aiBack | welcome': WRONG The list of boxes a stage-1 hand-off can leave is incomplete. → RIGHT Add 'start' and 'ai1'. HandOffWhenAiNeverReached also fires from STEP_REGISTERED (no welcome rule, or a failed send), not only from welcome_sent. HandOffAfterAiCall also fires from STEP_AI_CALL_PENDING (the call was placed and its result webhook never came). Neither box has an edge to task1.
    evidence: Rules/HandOffWhenAiNeverReached.php:40-47 (wakes for registered OR welcome_sent); Rules/HandOffAfterAiCall.php:32-36 (UNANSWERED includes ai_call_pending), :64-66, :26-27 doc ('placed … and then nothing more was ever heard'); FunnelJourneyHandoff.php:136; FunnelJourneyRepository.php:105.
- [skeptic 2] step_to_current_node: registered (journey.stage 1) → start, note 'Also the seed node of every Preview journey, including one opened without a registered event (import / walk-in)': WRONG 'start' (客户在 landing page 报名) is used as the seed and the current box for imported, admin-added and walk-in registrants. → RIGHT Those people never registered on the landing page, and nothing welcomes, calls or hands them off: they just wait for the webinar. Seed/enter 'start' only when the cycle has a `registered` event with data.source 'landing'; the code uses the same test to decide 'came through the landing'. A Preview journey opened by open() with no registered event should start with an empty path and show step 'registered' as 'preview' (waiting for the webinar). The step-only map cannot tell the two apart, so the walk must decide.
    evidence: FunnelJourneyHooks.php:70-75 ('Admin adds, imports and Zoom-side registrations do not come through here — nothing welcomes or calls those people, so their journey opens later, when the first reminder or the attendance verdict reaches them'); FunnelJourneyRepository.php:198-216 (open() writes step registered with no event); Rules/HandOffWhenAiNeverReached.php:21-25, :66-78.
- [skeptic 2] event_to_passed_nodes: candidate_marked note 'At lead level, pick is PASSED as soon as a Project journey exists': WRONG Any Project journey proves the From-Preview pick. → RIGHT A Project journey also opens from the Project funnel's OWN landing (landingRegistered runs for any tracked funnel, source 'landing'), or from an admin add / CSV import (opened by the first reminder or verdict, with no registered event). Light 'pick' only when the Project cycle starts with registered data.source === 'preview_candidate', or when the Preview journey has a candidate_marked. The design's own Project 'registered' row already says 'Any other source: nodes []', so this note contradicts it.
    evidence: FunnelJourneyHooks.php:83-105 (landingRegistered: any tracked funnel, data source 'landing'), :70-75, :130-160 (only candidateRegistered writes 'preview_candidate'); PreviewCandidatesController.php:124; funnel-journey readMe §3e ('The CSV import stays as the fallback for people who never came through the Preview').
- [skeptic 2] event_to_passed_nodes: webinar_no_show (moved), preview [preview, came]→noShow and project [project, paidFee]→follow3: WRONG A moved no-show is taken as proof that the lead passed noShow / follow3, even when it was overturned. → RIGHT 30 minutes after the end, SettleAttendanceAfterWebinar writes an INFERRED no-show (data.inferred = true) when no verdict exists yet. The real ATTENDED for the same registration then arrives as a different event and moves no_show → attended. When a no_show is followed by webinar_attended with the same data.event_id, remove noShow (Preview) or follow3 (Project) from the path instead of showing it green.
    evidence: Rules/SettleAttendanceAfterWebinar.php:20-25, :90-97 (inferred no-show keyed on the registration; 'A real verdict arriving later still wins'); FunnelJourneyRepository.php:108-111 (ONLY_FROM attended includes STEPS_AFTER_WEBINAR); FunnelJourneyEvent.php:156-157.
- [skeptic 2] event_to_passed_nodes: ai_call_refused (stage 1) 'Enters ai1 and answered'; step ai_call_missed → answered; event callback_clicked → aiBack: WRONG A refused call marks ai1, or aiBack, as passed (green), and its step is read as a 接了吗？ answer. → RIGHT A refused call never rang (budget, blocked number, concurrency, quiet hours), so no AI call happened. Leave ai1 out on ai_call_refused, and aiBack out when callback_clicked has data.refused. Give both the same 'not done' treatment the design proposes for not_called. Refused and missed share STEP_AI_CALL_MISSED, so the step-only map cannot tell them apart; only the event walk can.
    evidence: FunnelJourneyHooks.php:287-307 (STATUS_FAILED → EVENT_AI_CALL_REFUSED), :426-431 (callback_clicked is recorded even when refused, with data.refused); FunnelJourneyRepository.php:37 (refused → STEP_AI_CALL_MISSED); AiCallbackController.php:118-129 (quiet_hours / failed states).
- [skeptic 2] step ai_call_missed (stage 1) note + event ai_call_missed: 'a miss on the CALLBACK call leaves aiBack as current [until the hand-off]': WRONG After a missed callback call, aiBack stays current until the hand-off. → RIGHT The miss moves the step callback_clicked → ai_call_missed. AiCallAftermath then sends M3 again for the callback call; the per-lead cap blocks it only if an M3 already went out TODAY. That records missed_message_sent → missed_sent (a new 6-hour click wait), so the lead loops back to m3/clicked. Also, the step-only map (list) says 'answered' for the same state, so list and page disagree.
    evidence: AiCallAftermath.php:94-108 (aiCallMissed, then SendAiCallFollowUp KIND_MISSED); SendAiCallFollowUp.php:150-162 and missedSentToday() :409-416 (cap = since startOfDay); FunnelJourneyHooks.php:397-401 + journeysOfCall :446-457 (the callback_clicked event refs the call, so the M3 lands on that journey); FunnelJourneyRepository.php:95.
- [skeptic 2] step no_show (project) note 'Cold no-shows only get a WhatsApp and stay here (readMe §3c)': WRONG Cold no-shows stay at no_show. → RIGHT 120 minutes after the end, UnpaidAfterWebinar moves them no_show → unpaid (paid_at null). The box (follow3) is still right; only the note is wrong, and readMe §3c line 210 is stale on the same point.
    evidence: Rules/UnpaidAfterWebinar.php:33-46 (wakes for STEP_ATTENDED or STEP_NO_SHOW); FunnelJourneyRepository.php:112 (ONLY_FROM unpaid = attended, no_show).
- [skeptic 2] Leaving a task box without the task being done (extends the not_called gap): human_pending → attended/no_show/paid/registered, and rep_assigned → closed_*: WRONG Only not_called / human_expired are flagged as 'task1 shown passed though nobody called'. → RIGHT Any move out of human_pending other than human_done or not_called closes the call task as SUPERSEDED, 'Closed by the sales flow before anyone called'. Any move out of rep_assigned other than zoom_pending closes the Zoom task as no longer needed (for example, the deal is marked Booked/Lost before any Zoom). In those cases task1/task2/task3 or rep1/rep2 were not done. Mark them the same way as not_called, not green.
    evidence: FunnelJourneyRepository.php:368-370, :406-412 (closesOpenTasks); FunnelJourneyHandoff.php:537-559 (SUPERSEDED outcome and note); readMe §3d ('The deal closing before any Zoom closes the task as "no longer needed"').
- [skeptic 2] event_to_passed_nodes: candidate_marked, nodes 'task2 | rep1 | noShow | unpaid | paidMember': WRONG candidate_marked always arrives after the Preview verdict (a stage-2 box). → RIGHT From Preview lists registrants of every Preview session that starts before the PROJECT session; that session need not have happened yet. store() refuses only when the Project session has started, and recordOn has no step guard. So the Preview journey can still be in stage 1 (preview/task1/reminders…), and a later Preview verdict then moves it past pick (came → paidMember). Handle stage-1 current boxes, and do not let a later verdict pull the Preview path's current before pick.
    evidence: PreviewCandidates.php:160-168 (sources: startsAt ≥ since and < the Project start, not < now); PreviewCandidatesController.php:83-87; FunnelJourneyHooks.php:152-158.
- [skeptic 2] callback_clicked (any stage) — which journey it proves: WRONG A callback click is treated as an event of the one journey that sent the M2/M3. → RIGHT recordForLead writes callback_clicked on EVERY active journey of the lead that accepts it (a Preview and a Project journey can both be at missed_sent / welcome_sent / registered). journeysOfCall then attaches the callback call's answered/missed result to all of them. Light clicked/aiBack only on the journey whose own M2/M3 (offer_sent / missed_message_sent) is current, not on every journey that logged the click.
    evidence: FunnelJourneyRecorder.php:333-349; FunnelJourneyHooks.php:423-433, :446-457; FunnelJourneyRepository.php:96-99 (ONLY_FROM callback_clicked includes registered and welcome_sent).
- [skeptic 2] Stage column vs flowStage(): zoom_pending / zoom_done rows (preview stage 2, project stage 3): WRONG Only the paid and rep_assigned rows carry the 'journey.stage can still be 1' trap note. → RIGHT zoom_pending and zoom_done have the same disagreement. When the lead paid before the verdict, the journey stays at stage 1 for the whole paid path, so flowStage() returns 1 (Preview) or 2 (Project) while the band is 2 or 3. Every other row's stage matches flowStage(). Any test or doc that equates band with flow_stage must exclude all four paid-path steps.
    evidence: FunnelJourneyRepository.php:48, :51-53 (paid, rep_assigned, zoom_* set no stage), :110-111 (attended/no_show rejected from the paid path); Rules/SettleAttendanceAfterWebinar.php:44-51 (never wakes for the paid path); FunnelJourney.php:333-340.
- [skeptic 2] build plan §1 pathFor 'Reconcile: if active and band(walk node) ≠ band(nodeFor()), append nodeFor()': WRONG A band check is enough of a safety net. → RIGHT A lead merge moves the loser journey's whole event log onto the winner but keeps the WINNER's step. The id-ordered walk then interleaves two histories and can end on a box in the SAME band as the real step but a different box (for example walk = preview while step = human_pending/task1), which a band check misses. Reconcile on the node whenever nodeFor() is unambiguous (at least for human_pending, the closing steps and the after-webinar verdict steps).
    evidence: LeadRepository.php:2565-2618 (mergeFunnelJourneys: events repointed at :2584; 'The winner's BOX is kept' :2600).
- [skeptic 2] build plan §1 forLead 'Lead re-entered the flow: only if the Project journey is closed …; node comes from the Project journey when there is one': WRONG A Project journey that still exists outranks the Preview journey unless it is closed. → RIGHT A Project journey closes only through a deal marked Booked/Lost that journeyOwnsDeal accepts. A no-show or unpaid Project journey stays ACTIVE indefinitely. A lead who re-registers on the Preview landing afterwards gets a fresh Preview cycle (registered is accepted from STEPS_AFTER_WEBINAR), but the bar would still show follow3/paidFee (band 3). Choose by which journey's current cycle started last (the latest accepted registered/reopened event, or step_since), not 'Project if any'.
    evidence: FunnelJourneyHooks.php:697-730 (the only close path, Project only); FunnelJourneyRepository.php:84-87 (registered restarts from after-webinar steps); FunnelJourney.php:367 (step_since ordering already exists).
- [skeptic 2] build plan §1 'NODES = [start => 1, /* … 24 ids … */ closed => 3]': WRONG 24 node ids. → RIGHT FLOW_CHART has 23 nodes: 10 in 第1段, 8 in 第2段 and 5 in 第3段. The parity vitest should expect 23.
    evidence: resources/js/Pages/Manage/MyWork/Partials/salesFlowGuide.js:33-42 (10), :48-55 (8), :61-65 (5).