[cristim]

Summary

• Standard users with cancel-own:purchases could not see the Disable button on their own scheduled purchases in the Plans page, even though:
  • The backend deletePlannedPurchase already accepts cancel-own:purchases (PR fix(home): show Cancel button for own scheduled purchases #1421)
  • The Home-page widget's canCancelUpcomingPurchase already accepts cancel-own:purchases (PR fix(home): show Cancel button for own scheduled purchases #1421)
• The Plans-page canDisablePlan gate in plans.ts required delete:purchases exclusively. Standard users hold cancel-own:purchases, not delete:purchases, so the button was hidden even for the creator.
• canManageScheduledPurchase already enforced the ownership check; only the verb gate in canDisablePlan was wrong.

Changes

Frontend (frontend/src/plans.ts)

• canDisablePlan: extended to accept cancel-any:purchases or cancel-own:purchases in addition to delete:purchases, mirroring the backend requireDeleteOrCancelPurchasePermission gate and the dashboard canCancelUpcomingPurchase logic introduced by PR fix(home): show Cancel button for own scheduled purchases #1421.
• Updated comment to reference authorizePlannedPurchaseCancel (the current backend function name after fix(home): show Cancel button for own scheduled purchases #1421, not the old authorizeExecutionManagement).

Tests (frontend/src/__tests__/plans-ownership-950.test.ts)

• Extended setUser helper to accept cancelOwn, cancelAny, and deletePurchases opts (backward-compatible: deletePurchases defaults to true).
• New describe block "Plans-page Disable-button cancel-own gating (issue bug(rbac/plans): creator cannot manage own scheduled purchase created from Plans page #1442)" with 4 cases:
  • Creator with cancel-own (no delete:purchases) sees the Disable button
  • Non-creator with cancel-own does NOT see the Disable button (ownership gate holds)
  • Legacy NULL-creator row shows no Disable for a cancel-own user
  • cancel-any creator also sees Disable (backend supports it)

Verify-first result

PR #1421 updated the backend and the Home-page widget but did NOT update the Plans-page canDisablePlan gate. This is a genuine gap, not a stale re-test.

Test plan

• Frontend tests: 79 suites, 2641 passed, 0 failures, exit 0
• Frontend typecheck: tsc --noEmit exit 0
• Go build: go build ./... exit 0
• Go vet: go vet ./... exit 0
• Pre-commit hooks: all passed
• Manual: log in as Standard user, navigate to Plans page, verify Disable button appears on own scheduled purchases and is absent on other users' rows

Closes #1442

[cristim]

@coderabbitai review

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 50 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0bef76b3-9377-426a-ae7d-1d392d0462da

📥 Commits

Reviewing files that changed from the base of the PR and between f692085 and dd931b7.

📒 Files selected for processing (2)

• frontend/src/__tests__/plans-ownership-950.test.ts
• frontend/src/plans.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/1442-manage-own-plans-scheduled-purchase

---

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.