Devin FoleyandPaperclip 3290d97417 Scope the release smoke opening question to its card (#15339) ...

## Thinking Path

> - Paperclip is the open source app people use to manage AI agents for
work.
> - The release lane checks onboarding before it promotes a nightly
candidate.
> - The first task shows an unanswered-question summary and an open
question card.
> - Both display the same prompt, so the smoke test's page-wide text
locator fails strict matching.
> - This pull request scopes that assertion to the open interaction
card.
> - The smoke still requires the actual prompt and verifies that
onboarding does not start an agent run.

## Linked Issues or Issue Description

**What happened?**

[Scheduled release run
37441718130](https://github.com/paperclipai/paperclip/actions/runs/37441718130)
failed `smoke_nightly / smoke` on both attempts. The page-wide
`getByText("What would you like to do?")` matched two elements: the
timeline summary and the open question card. This skipped
`publish_nightly`.

**Expected behavior**

The test confirms that the seeded task's open question card displays the
exact prompt. A summary row alone must not satisfy that check.

**Steps to reproduce**

Run the Docker onboarding smoke against published candidate
`2026.1006.0-canary.11`, then run the release-smoke Playwright spec. The
old assertion fails after the greeting appears.

**Paperclip version or commit**

Release workflow commit `f858207161ba29c01c82f4674aef83d91b74480f`;
published candidate `2026.1006.0-canary.11`. The assertion is unchanged
on the current master base `9b3fe260bac576d622ffdfefb923db73cc5273f7`.

**Deployment mode**

Docker smoke harness, authenticated/private, with its existing mock
provider.

Related: #13166 added the first-task chat assertion. I also reviewed
open #12316, which fixes a separate bootstrap race and does not change
this selector. Searches found no duplicate selector fix or public issue.

## What Changed

- Scope the exact opening-prompt text to `task-chat-interaction`.
- Explain why the timeline summary cannot satisfy the assertion.
- Preserve the rest of the smoke flow, including the 15-second check for
no agent runs.

## Verification

- Local Docker harness ran the exact failed published candidate,
`2026.1006.0-canary.11`, with the existing mock provider.
- The old spec reproduced the same two-element strict-mode error in
Chrome.
- The fixed spec passed the full authenticated onboarding flow and the
15-second no-run check: 1/1, 32.6 seconds. The executed spec copy was
byte-identical to the changed repository file; only artifact output
paths and the local port were overridden.
- Independent Chrome checks: the scoped locator passes with both summary
and card present. Summary-only, wrong prompt, hidden prompt, and
duplicate active prompts each fail as intended.
- `pnpm typecheck` and `pnpm build` passed on Node 24.21.0. Canonical
Linux CI passed all 55 checks (53 success, 2 intentional Storybook
skips), including the full aggregate tests, build, typecheck, all eight
E2E shards, and post-ready security scan.
- Greptile scored the exact head
`5a30e667396600a052a4041c819652c19b8c68ff` at 5/5 with no actionable
issues. Independent review found no issues; there are no review threads.
- `git diff --check` passed. The diff and PR text were scanned for
secrets and private identifiers.

## Risks

Low risk: one assertion in a release smoke test changes. A missing or
hidden prompt still fails, and multiple matching prompts in interaction
cards still fail strict mode. This does not change the product, release
selection, or publishing. The scheduled release lane still needs its
next normal successful run to prove nightly recovery.

## Model Used

OpenAI GPT-6 through Codex, with reasoning, shell tools, and an
independent Codex review. The exact serving model identifier and
context-window size are not exposed in this session.

## Checklist

- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have searched GitHub for duplicate or related PRs and linked
them above
- [x] I have either (a) linked existing issues with `Fixes: #` / `Closes
#` OR (b) described the issue in-PR following the relevant issue
template
- [x] I have not referenced internal/instance-local Paperclip issues or
links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip`
URLs)
- [x] My branch name describes the change (e.g. `docs/...`, `fix/...`)
and contains no internal Paperclip ticket id or instance-derived details
- [x] I have run tests locally and they pass
- [x] I have added or updated tests where applicable
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [x] All Paperclip CI gates are green
- [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge

Co-authored-by: Paperclip <noreply@paperclip.ing>

2026-10-06 06:42:21 -07:00

..

docker-auth-onboarding.spec.ts

Scope the release smoke opening question to its card (#15339)

2026-10-06 06:42:21 -07:00

playwright.config.ts

ci: use runner Chrome for headless workflows (#6967)

2026-05-29 00:18:52 -07:00