docs(redesign): commit port-target ADR + backlog-map spec

[LucasSantana-Dev]

Summary

Commits the load-bearing redesign-migration documents that were sitting untracked in the working tree — all already referenced from in-flight work:

• docs/decisions/2026-04-21-redesign-port-target.md — accepted ADR (Vite-port + dual accent + Sora/Manrope). Already marked [x] in docs/specs/2026-04-21-backlog-map/tasks.md and is the document driving landed PRs feat(frontend): redesign token aliases + brand decision #763 (token aliases) and feat(frontend): SectionHeader eyebrowIcon + statusBand #765 (SectionHeader).
• docs/specs/2026-04-21-backlog-map/{spec,tasks}.md — structured backlog spec tracking the 2026-04-21 backlog map + redesign migration anchors.
• docs/FRONTEND_AI_STUDIO_CONTEXT.md, docs/LOVABLE_PROMPT.md — referenced from the ADR's "Related" and "Execution plan" sections; preserved alongside the index that links them.

Also gitignores packages/*/*.zip — packages/frontend.zip is a ~25 MB AI-Studio export, not source.

Why now

These files have been sitting untracked across sessions. Losing the clone loses the ADR, which is load-bearing for redesign work already in main. Parallel-session churn on the main clone kept reverting attempts to commit on feature branches; committing from a disposable worktree off origin/main avoids the collision.

Test plan

• No source changes — docs + gitignore only
• docs/ is already a tracked directory with many committed docs; pattern is consistent
• ADR cross-references resolve (spec.md → decisions/, tasks.md → decisions/, ADR → LOVABLE_PROMPT.md + FRONTEND_AI_STUDIO_CONTEXT.md)
• CI lint/typecheck/build remain green (docs-only diff, expected pass)

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
lucky	Ready	Preview, Comment	Apr 22, 2026 0:18am

[coderabbitai]

Warning

Rate limit exceeded

@LucasSantana-Dev has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 26 minutes and 56 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 26 minutes and 56 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d416d91e-6e34-426b-82da-521a6fae824d

📥 Commits

Reviewing files that changed from the base of the PR and between 2a4d1e5 and 35fb583.

📒 Files selected for processing (6)

• .gitignore
• docs/FRONTEND_AI_STUDIO_CONTEXT.md
• docs/LOVABLE_PROMPT.md
• docs/decisions/2026-04-21-redesign-port-target.md
• docs/specs/2026-04-21-backlog-map/spec.md
• docs/specs/2026-04-21-backlog-map/tasks.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/redesign-adr-and-backlog-map

---

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 and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
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