feat: redirect root path to /portal

[stabem]

Option A

Make the root path (/) redirect to /portal.

What changes

• add a root route that responds with 302 Location: /portal
• add a focused app test for the redirect

Validation

• npm run typecheck ✅
• npm run build ✅
• src/app.test.ts ✅ (47/47)

Why choose this option

• minimal diff
• no extra public HTML to maintain
• fastest path from root domain to the self-serve product

[stabem]

Claude review verdict: APPROVE. Root redirect is a tiny, self-contained route change with matching test coverage and no obvious security/runtime risk. GitHub blocks self-approval on own PRs, so recording the approval verdict here.

[stabem]

✅ Code Review — Root redirect to /portal

Código trivial e correto. Mas conflita com #299 que adiciona uma landing page completa no mesmo endpoint.

Recomendo fechar este e mergear #299 (abordagem mais completa).

Veredito: APPROVE (sem bloqueios)

[stabem]

🔍 Code Review — CLEAN ✅

Redirect simples e limpo de / → /portal. Teste cobre status 302 e header location.

⚠️ Conflita com #299 (landing page). Apenas um pode ser mergeado.

[stabem]

🤖 Code Review: CLEAN — No blocking issues

Simple one-liner redirect with test. No issues. ⚠️ Conflicts with #299 — recommend #299 (landing page) for better UX.

[stabem]

✅ Code Review — APPROVED

Redirect simples e limpo. Teste adequado.

⚠️ Conflita com #299 (landing page). Se preferir UX polida, mergear #299.

[stabem]

Closing in favor of #299 (landing page approach).

All reviews on both PRs recommend #299 as the more complete solution.

🤖 Software Factory Pipeline