docs(ai): refresh handoff for PR #156 — pending-verification feature

Closes out Escalation Mode (PR #155 merged) and pivots active task to
the new applied_pending suggested-fix outcome on PR #156.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

.ai/CURRENT_TASK.md

@@ -1,83 +1,47 @@
 # CURRENT_TASK.md
 
-**Task:** Build **Escalation Mode** — the wedge for ResolutionFlow's GTM (first paying-customer push). When a junior tech escalates a FlowPilot session, the senior tech sees structured handoff context in seconds instead of running a 5-minute verbal "tell me what you tried" call.
+**Task:** Add a fourth, non-terminal outcome to the suggested-fix banner — **Awaiting verification** (`applied_pending`). Today the verifying banner forces a synchronous verdict (worked / didn't / partial), but a lot of real fixes are async — engineer ran the script but is waiting on the client to power-cycle, AD replication, an O365 license sync. Without a fourth state the banner sits stale or the engineer guesses wrong.
 
-**Status:** ✅ **Engineering complete.** Browser QA passed (2026-04-30). Branch `feat/escalation-metric-endpoint`; PR #155 ready to mark ready-for-review.
+**Status:** ✅ **Engineering complete; PR #156 open.** Backend tests + tsc clean, Alembic migration applies. Pending browser QA.
 
-**Plan:** [`docs/plans/2026-04-27-escalation-mode-wedge-design.md`](../docs/plans/2026-04-27-escalation-mode-wedge-design.md). Reviewed by `/office-hours`, `/plan-eng-review`, `/plan-design-review`, `/codex review`. Eng + Design CLEARED.
+**Branch:** `feat/fix-pending-verification` (off `main` after the Escalation Mode merge).
 
-**Test plan artifact:** [`docs/plans/2026-04-27-escalation-mode-wedge-test-plan.md`](../docs/plans/2026-04-27-escalation-mode-wedge-test-plan.md).
+**PR:** https://gitea.resolutionflow.com/chihlasm/resolutionflow/pulls/156
 
-## What's done (all sessions combined)
+## What ships
 
-All plan items complete. Key commits on `feat/escalation-metric-endpoint`:
-
-| Commit | What it ships |
+| Layer | Change |
 |---|---|
-| `d51e95c` | Plan + test-plan artifacts |
-| `52f6d03` | `GET /analytics/flowpilot/escalations` — time-to-first-action metric |
-| `7a5b853` | Role-gate claim to engineer-or-admin |
-| `07d0db9` | Email notifications on escalation |
-| `9f0bfd4` | `EscalationMetricCard` on `/escalations` |
-| `b8627f4` | SSE live-arrival animations in `EscalationQueue` |
-| `8e9d22e` | Magic-moment handoff-context screen |
-| `641853a` | Bell-icon opens pickup flow |
-| `029680a` | Unify `/escalate` through `HandoffManager` |
-| `0f00ee5` | Plan-locked polish: chips, unread dot, race toast, AI refresh |
-| `665530f` | Structural task-lane race fix |
-| `db717b0` | 3-option CTA, copy button fix, post-escalation redirect, claim 500 fix |
-| `dc69c9d` | Allow `escalated_to_id` to send chat (GET AI analysis fix) |
+| Schema | New `FixStatus="applied_pending"` + new `pending_reason` Text column on `session_suggested_fixes`. |
+| Migration | `c0f3a4b7e91d` — adds `pending_reason`, extends status CHECK constraint. |
+| API | `PATCH /suggested-fixes/{id}/outcome` accepts `applied_pending`, requires `notes`, stamps `applied_at` only (NOT `verified_at`). Pending in/out transitions allowed (parked, like partial). |
+| Generators | `resolution_note_generator` and `escalation_package_generator` system prompts handle the new status: resolution note frames the fix as provisional; escalation package surfaces pending verification as the leading hypothesis with reference to what's being waited on. |
+| Frontend | New `BannerMode='pending'` + `PendingBanner` component (info-tone, mirrors `PartialBanner`); "Waiting to verify…" overflow option in `VerifyingBanner`; nudge "Still checking" now records pending with a reason instead of just silencing; `AssistantChatPage` banner-mode derivation maps `applied_pending → 'pending'`. |
+| Tests | 4 new integration tests in `test_fix_outcome_endpoint.py`: pending-requires-notes, pending stores reason + applied_at-not-verified_at, pending→success transition, pending_reason update on re-PATCH. 21/21 pass. |
 
-**Browser QA results (2026-04-30):**
+## Out of scope (intentionally)
 
-- ✅ Post-escalation redirect (dashboard + toast)
-- ✅ Magic-moment screen: header, AI assessment, 2-option CTA
-- ✅ "I'll take it from here": claim → dismiss → composer focused
-- ✅ "Get AI analysis": claim → briefing → AI responds → task lane populates
-- ✅ Task lane copy button: toast + checkmark
-- ✅ Chip expansion: inline detail + "Open in Tasks panel"
-- ✅ Post-claim overlay: dismissible mode, Close only
+- Cross-session "Follow-ups" dashboard rollup. The chat-anchored `PendingBanner` is the per-session reminder. Add the dashboard surface only if engineers report losing track across multiple pending sessions.
+- Optional follow-up timer ("remind me in 30m"). Nice but not the wedge.
 
-## Done on `feat/escalation-metric-endpoint` (branched from `main` @ `c0ed6d9`)
+## Resume point — DO THIS NEXT
 
-| Commit | What it ships |
-|---|---|
-| `d51e95c` | Plan + test-plan artifacts |
-| `52f6d03` | `GET /analytics/flowpilot/escalations` — in-product time-to-first-action |
-| `7a5b853` | Role-gate POST `/handoffs/{id}/claim` to engineer-or-admin |
-| `07d0db9` | `HandoffManager.dispatch_escalation_notifications` — emails engineer/admin teammates |
-| `9f0bfd4` | `EscalationMetricCard` mounted above the queue list |
-| `bc15952` | Codex: stabilize SSE backend tests |
-| `9bdd995` | Bound escalation assessment latency (ORIGINAL: 5s) |
-| `b8627f4` | Frontend SSE subscription in `EscalationQueue.tsx` — live-arrival animations |
-| `8e9d22e` | Magic-moment handoff-context screen on pickup |
-| `641853a` | Bell-icon notification opens the pickup flow |
-| `029680a` | Unify `/escalate` through `HandoffManager` |
-| `8914391` | First task-lane race fix (insufficient — see `665530f`) |
-| `0f00ee5` | Four plan-locked items: live AI refresh, suggested-step chips, unread dot, race-condition toast |
-| `665530f` | Structural task-lane fix — `taskLaneOwnerChatId` tagging |
-| `b7d7ff0` | docs(ai): refresh handoff for compute swap |
-| `0d1b305` | **Live-test fixes**: selectChat-gating bug (loadedChatIdsRef), 45s timeout bump, Enter-to-submit on escalate forms, dashboard expand-to-preview |
+**Browser QA:** verify the new flow end-to-end in dev:
+1. Trigger a suggested fix, click Apply, then open the verifying banner overflow → "Waiting to verify…" → enter a reason → confirm `PendingBanner` renders with the reason.
+2. From `PendingBanner`, click "It worked" → confirm transition to terminal success and banner dismissal.
+3. From `PendingBanner`, click "Update reason" → confirm reason updates server-side.
+4. Trigger the nudge state (3+ post-apply messages) → click "Still checking" → enter a reason → confirm pending state takes over.
 
-## Live-test results (2026-04-29 morning)
+After QA passes, merge PR #156.
 
-After the structural task-lane fix and the four polish items, end-to-end test confirmed:
+## Just-shipped (2026-04-30)
 
-- ✅ Junior escalates → senior gets bell-icon notification.
-- ✅ Magic-moment screen renders with handoff data on Pick Up.
-- ✅ Senior's chat surface loads with conversation history (after `0d1b305`'s selectChat fix — was completely broken before).
-- ✅ Sidebar shows the picked-up session with the "Escalated" pill (after `0d1b305`'s `loadChats()` call).
-- ✅ Suggested-step chips render below the composer.
-- ✅ Unread 6px dot on queue cards.
-- ✅ Task-lane regression is gone — no stale flash on new sessions.
-- ❌ **AI assessment placeholder never clears.** Drives the consolidation work above.
+**PR #155 — Escalation Mode wedge** merged into main as `ac42f97`. The wedge for ResolutionFlow's GTM (first paying-customer push). Senior tech sees structured handoff context in seconds via the magic-moment screen. Plan: [`docs/plans/2026-04-27-escalation-mode-wedge-design.md`](../docs/plans/2026-04-27-escalation-mode-wedge-design.md).
 
-Untested live (low priority, can verify post-consolidation): race-condition toast (needs second user in same account).
+## Two-metric framing (Escalation Mode — read before quoting numbers)
 
-## Two-metric framing — read this before quoting numbers to anyone
+The in-product `GET /analytics/flowpilot/escalations` endpoint measures *post-claim time-to-first-action*. The "minutes recovered" sales claim is `manual_baseline − in_product_metric`. Manual baseline comes from the founder's stopwatch on the next 5 escalations. Don't roll the in-product number alone into "minutes recovered" — that's the apples-to-oranges miscount Codex caught.
 
-The in-product endpoint measures *post-claim time-to-first-action*. The "minutes recovered" sales claim is `manual_baseline − in_product_metric`. Manual baseline comes from the founder's stopwatch on the next 5 escalations. Don't roll the in-product number alone into "minutes recovered" — that's the apples-to-oranges miscount Codex caught.
-
-## Kill-switch
+## Kill-switch (Escalation Mode)
 
 Week 8: if 0 of 3 pilots produce a verifiable hours-saved-per-week number above 1.0, revisit the wedge.