ux(recommendations): inline Plan button deep-links into Create Plan modal (closes #120)

[cristim]

Summary

• Adds an inline Plan button to each recommendation row in the Opportunities table
• Clicking the button opens the Create Purchase Plan modal pre-seeded with that row's recommendation, eliminating the select-then-scroll-then-click flow
• Permission gate mirrors the bulk Create Plan button: only visible when the session has create:plans (admin and user roles; hidden for readonly)

Implementation

• buildVariantRowMarkup emits a <button class="rec-plan-btn" data-rec-id="..." data-action="plan">Plan</button> inside the checkbox cell when canAccess('create', 'plans') is true; empty string otherwise (fail-closed)
• renderRecommendationsList wires a click handler on .rec-plan-btn buttons that calls openCreatePlanFromBottomBox([rec]) - the same function used by the bulk Create Plan button, scoped to one rec
• data-action="plan" attribute ensures the row-click selection handler skips button clicks (existing target.closest('[data-action]') guard)
• e.stopPropagation() prevents the click from bubbling to the row handler

Test plan

• tsc --noEmit clean
• 8/8 tests pass in recommendations-permissions.test.ts (5 existing + 3 new)
• 332/332 total tests pass across all three recommendations test files
• New tests added:
  • admin role sees a rec-plan-btn when rows are rendered
  • readonly role has no rec-plan-btn buttons (gated)
  • clicking the button calls openCreatePlanModal with the correct rec pre-seeded

[coderabbitai]

Warning

Review limit reached

@cristim, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 23 minutes and 31 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a78ef1d8-dd49-4dc0-bb9e-b72585e0c24a

📥 Commits

Reviewing files that changed from the base of the PR and between 80c20d2 and 055dded.

📒 Files selected for processing (2)

• frontend/src/__tests__/recommendations-permissions.test.ts
• frontend/src/recommendations.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/120-wave14

---

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

[cristim]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

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.

[cristim]

@coderabbitai full review

[coderabbitai]

✅ Actions performed

Full review triggered.

[cristim]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

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.