fix(aluno): prd-8 mobile card variant for detail tables

[EmiyaKiritsugu3]

PRD-8 — last mobile-first PRD.

Changes

• src/app/dashboard/alunos/[id]/page.tsx: MatriculasTable + PagamentosTable gain <md stacked key-value card variant (dl/dt/dd grid-cols-2). Desktop Table wrapped in hidden md:block, untouched. Pure CSS show/hide — no JS, no new helpers. TreinosList already grid, no change.
• src/app/dashboard/alunos/[id]/page.test.tsx: 4 getByText status/metodo/plano asserts → getAllByText (mobile card + desktop table both in DOM). Added dl count test for mobile variant structure.

Scope decisions (user-confirmed)

• Row actions (spec §3): skipped — tables static, no card footer / touch-target added.
• E2E: existing suite green only. No new spec, no playwright.config mobile project.
• Test asserts: structure-only (dl counts), not exact R$ text (jsdom Intl BRL flaky).

Verification

• typecheck pass, full unit suite 1137/1137 pass, own-src lint clean.
• E2E gate running.

Spec: docs/superpowers/specs/2026-07-07-aluno-detail-tables-mobile-design.md

🤖 Generated with Claude Code

---

Summary by cubic

Implements PRD-8 mobile-first design on the Aluno details page: Matriculas and Pagamentos render stacked key-value card views below md while desktop tables remain unchanged.
Uses CSS-only show/hide (md:hidden + hidden md:block); updates tests (getAllByText, dl count) and adds an inline note on the deliberate toggle duplication, with a plan to extract a helper when a third responsive table appears.

^{Written for commit 0717bd5. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
smartmanagementsystem	Ready	Preview, Comment	Jul 6, 2026 7:00pm

[coderabbitai]

Warning

Review limit reached

@EmiyaKiritsugu3, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 13 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 45b95606-1c1f-456f-8140-5eb3180b6a42

📥 Commits

Reviewing files that changed from the base of the PR and between de744c4 and 0717bd5.

📒 Files selected for processing (2)

• src/app/dashboard/alunos/[id]/page.test.tsx
• src/app/dashboard/alunos/[id]/page.tsx

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/aluno-detail-tables-mobile

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[cubic-dev-ai]

1 issue found across 2 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/app/dashboard/alunos/[id]/page.tsx">

<violation number="1" location="src/app/dashboard/alunos/[id]/page.tsx:183">
P3: The responsive card/table wrapper pattern (`<div className="md:hidden..."><div className="hidden md:block...">`) is duplicated identically in both `MatriculasTable` and `PagamentosTable`. If the breakpoint (`md`), the grid gap (`gap-3`), or the visibility strategy ever needs to change, both components must be updated in sync, increasing maintenance surface area. Consider extracting the responsively-switching container into a small shared wrapper component (e.g. `ResponsiveStack` or `CardStack`) that receives the mobile card renderer and desktop table renderer as children or render props. This keeps the responsiveness logic in one place while each component still provides its own content.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

P3: The responsive card/table wrapper pattern (<div className="md:hidden..."><div className="hidden md:block...">) is duplicated identically in both MatriculasTable and PagamentosTable. If the breakpoint (md), the grid gap (gap-3), or the visibility strategy ever needs to change, both components must be updated in sync, increasing maintenance surface area. Consider extracting the responsively-switching container into a small shared wrapper component (e.g. ResponsiveStack or CardStack) that receives the mobile card renderer and desktop table renderer as children or render props. This keeps the responsiveness logic in one place while each component still provides its own content.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At src/app/dashboard/alunos/[id]/page.tsx, line 183:

<comment>The responsive card/table wrapper pattern (`<div className="md:hidden..."><div className="hidden md:block...">`) is duplicated identically in both `MatriculasTable` and `PagamentosTable`. If the breakpoint (`md`), the grid gap (`gap-3`), or the visibility strategy ever needs to change, both components must be updated in sync, increasing maintenance surface area. Consider extracting the responsively-switching container into a small shared wrapper component (e.g. `ResponsiveStack` or `CardStack`) that receives the mobile card renderer and desktop table renderer as children or render props. This keeps the responsiveness logic in one place while each component still provides its own content.</comment>

<file context>
@@ -179,30 +179,57 @@ function MatriculasTable({
-            </TableHeader>
-            <TableBody>
+          <>
+            <div className="md:hidden grid gap-3">
               {matriculas.map((m) => (
-                <TableRow key={m.id}>
</file context>

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud