Files
kandev/docs/plans/clarification-active-lifecycle/task-01-clarification-regression-red.md
T
2026-08-23 17:34:52 +00:00

87 lines
4.0 KiB
Markdown

---
id: "01-clarification-regression-red"
title: "Clarification regression red"
status: done
wave: 1
depends_on: []
plan: "plan.md"
spec: "../../specs/tasks/requirements/clarification-active-lifecycle.md"
---
# Task 01: Clarification regression red
## Acceptance
- Desktop production-build E2E reproduces the old-detached/newer-skipped sequence and fails because
the old question or task icon resurfaces after reload or later completion.
- Desktop E2E creates a task whose non-primary session owns clarification and fails because task-row
activation opens the clean preferred/primary session.
- Phone E2E reproduces secondary pending ownership with touch activation and fails on active chat or
question visibility while preserving existing drawer assertions.
- Each failure is captured once for the expected product reason before production code changes.
## Verification
```bash
(cd apps && pnpm install --frozen-lockfile)
(cd apps/web && pnpm e2e:run tests/task/sidebar-pending-question.spec.ts)
(cd apps/web && pnpm e2e:run --no-build --project mobile-chrome tests/task/mobile-sidebar-task-actions.spec.ts)
```
The focused commands are expected to exit nonzero in this RED task. Record the exact failing
assertions and fresh artifact paths; do not weaken assertions or increase timeouts.
## Files likely touched
- `apps/web/e2e/tests/task/sidebar-pending-question.spec.ts`
- `apps/web/e2e/tests/task/mobile-sidebar-task-actions.spec.ts`
- `apps/web/e2e/helpers/clarification.ts` only if shared current test setup removes duplication
- `apps/web/e2e/pages/session-page.ts` only if a stable existing surface lacks a reusable locator
## Dependencies
None.
## Parallelism
Sequential. These black-box failures define every later task's acceptance boundary.
## Inputs
- Spec scenarios for newer-turn supersession and secondary-session navigation.
- Existing `/e2e:clarification-timeout` and `/e2e:clarification` mock scenarios.
- Existing `ApiClient.addUserMessage`, `ApiClient.launchSession`, `SessionPage`, and sidebar helpers.
- E2E guidance: seed via API, assert through UI, verify reload, use `.tap()` on phone, and run managed
production builds.
## Risks
- Confirm the second clarification has a different `pending_id` before clicking Skip; identical prompt
text is not sufficient evidence.
- Wait on exact session states and persisted messages, not arbitrary sleeps or agent output alone.
- Keep mobile file naming/project routing intact so Playwright discovers the intended test.
## Output contract
Report scenarios added, exact commands, expected failure messages/artifact paths, and why each failure
matches the confirmed defect. Mark this task `done`, retain failing tests for later GREEN, and update
the plan checkbox/results.
## Results
- Added production-build regressions for older detached clarification supersession, desktop
secondary-session ownership, and phone drawer secondary-session ownership.
- `cd apps && pnpm install --frozen-lockfile` passed (already up to date).
- `cd apps/web && pnpm e2e:run tests/task/sidebar-pending-question.spec.ts` discovered 3 tests:
1 passed and 2 failed for the expected defects. Reload found one superseded
`clarification-overlay` instead of zero; desktop activation selected the clean primary session
instead of the clarification-owning secondary. Artifacts were reported under
`/tmp/pw-out/task-sidebar-pending-quest-5d9bc-r-a-newer-bundle-is-skipped-chromium/` and
`/tmp/pw-out/task-sidebar-pending-quest-6afec-ion-that-owns-clarification-chromium/`.
- `cd apps/web && pnpm e2e:run --no-build --project mobile-chrome tests/task/mobile-sidebar-task-actions.spec.ts`
discovered 12 tests. The new phone regression failed for the expected reason: active session was
the clean primary instead of the clarification-owning secondary. Artifact was reported under
`/tmp/pw-out/task-mobile-sidebar-task-a-5cc01-ation-from-the-phone-drawer-mobile-chrome/`.
Ten baselines passed; one unrelated existing create-subtask case timed out during setup and will be
rerun in the GREEN wave.