## Thinking Path
> - Paperclip is the open source app people use to manage AI agents for
work
> - The applications page shows connected services and their status
> - The e2e suite covers the Connections row on that page
> - The server runs a periodic connection health sweep during the test
> - The sweep can change the connected row label and action after the
first render
> - This pull request accepts both connected states on that row
> - The benefit is the test checks the real user path without a sweep
race
## Linked Issues or Issue Description
No public issue exists. This pull request fixes a race in the
applications Connections e2e test.
**Bug:** The test pinned the exact connected-state pill and action.
**Expected:** The test should accept both connected states for the same
connection row.
**Impact:** The health sweep can change the label between assertions.
**Fix:** The test now accepts either label and action on the connected
row.
## What Changed
- Allowed the connected row pill to match `Healthy` or `Needs
attention`.
- Allowed the connected row action to match `Open` or `Reconnect`.
- Kept the not-connected row exact.
## Verification
- `git diff --check
origin/master..origin/test/deflake-applications-crud-health-sweep`
- `git show --stat --summary --oneline
9785785a5d41cd13ee5a0f8aeb73f389cdbdac2e`
- Local Playwright e2e did not run in this worktree.
- CI on this pull request should provide the full proof.
## Risks
- Low risk. The change only widens the expected labels for the connected
row.
- If the UI adds a new state, the test may need another update.
## Model Used
OpenAI GPT-5, tool use, context window not exposed in this shell
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
#` / `Refs #` 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
- [ ] I have run tests locally and they pass
- [x] I have added or updated tests where applicable
- [ ] I have updated relevant documentation to reflect my changes
- [ ] All Paperclip CI gates are green
- [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [ ] I will address all Greptile and reviewer comments before
requesting merge
Co-authored-by: Paperclip <noreply@paperclip.ing>
42d0ddcb86