test(ui): cover a period-end cancellation whose final invoice is paid

[otavio]

Summary

Adds a cloud-edition Playwright test for shellhub-io/team#260: an owner who cancels at the end of the period must stay canceled after Stripe charges the final invoice. The fix is shellhub-io/cloud#2616, on the same branch name, so this PR's cloud e2e leg builds it.

create a Stripe test clock and a customer on it
write that customer_id into the namespace's billing (psql)   # the console skips creating one
subscribe through the UI (4242 card)
subscriptions update cancel_at_period_end=true
  poll namespace → to_cancel_at_end_of_period
advance the clock past cancel_at, poll it → ready            # ends the subscription, drafts the final invoice
  poll namespace → canceled
finalize the draft final invoice (stripe CLI)                # Stripe leaves it a draft; $0 is paid on finalization
  poll server log → invoice.paid abandoned for this subscription
assert canceled, max_devices = 3, no active Stripe subscription
teardown: delete the clock, which deletes its customer

The log poll gives the test a positive signal that invoice.paid was handled. Without it, the final assertions would already hold before the webhook arrives.

Evidence

• Before: the server never writes the abandon line, so the poll times out (or, if invoice.paid re-subscribes the namespace first, the status assertion fails).
  After: the cloud e2e leg of this PR's ui-e2e run.
• I couldn't run this locally because the dev environment has no Stripe test keys. The cloud e2e leg in CI is its first real run. ESLint, tsc, knip and Prettier pass.

Merge Danger

Door: two-way

Blast Radius: cloud e2e leg

Test-only. The test adds about a minute to the cloud leg, most of it waiting for Stripe to advance the clock by a month. A slow advance shows up as a timeout on the clock poll.

Merge shellhub-io/cloud#2616 first. Once this is on master, the cloud leg fails against a cloud master that lacks the fix.

[github-actions]

Claude finished @otavio's task in 4m 9s —— View job

---

Code Review Complete

Reviewed 2 files. 1 inline issue posted. Standards: 0 violations, 0 judgement calls. Spec: 0. Correctness: 1.

Standards

No violations. setBillingCustomer follows the existing sql + UPDATE 1 check pattern, the diff adds no comments, and the commit message explains each workaround: the customer written through psql, teardown that deletes the clock, the 2 h offset, and the log poll.

Correctness

billing.spec.ts:377: test.setTimeout(240_000) is smaller than the test's own poll timeouts (270 s), even before the UI subscribe flow. If the clock advance is slow, the test-level timeout fires first and hides the invoice.paid abandon message.

I also checked these against the sibling cloud/ checkout, and they hold:

• The console and cloud CreateCustomer both skip creating a customer when billing.customer_id is set.
• The log string matches cloud/internal/billing/services/handles.go, and that log line carries the subscription ID.
• Teardown covers every failure point once testClock is set.

Spec

The Spec axis did not run. The PR closes no issue in this repo, and the issue it cites (shellhub-io/team#260) is in a repo this run cannot read.

---

To request another review round, comment /review.

[otavio]

/review

[github-actions]

Claude finished @otavio's task in 6m 11s —— View job

---

Code Review Complete

Reviewed 2 files on two axes: Standards (repo rules, language conventions, tests, code smells) and Correctness (security and runtime defects). No new issues found. The code looks good as-is.

The Spec axis did not run. The PR closes no issue in this repo, and the issue it cites (shellhub-io/team#260) is in a repo this run cannot read.