Feat/login signup public catalog

[michael-on-code]

Checklist

• Tests were added/updated according to the feature/bugfix/change made
• Version was rolled according to semver requirements
• API endpoints openapi schema was updated if applicable

Changes

• feat: login and signup buttons on public catalog in
• feat: hide home, discover, recommended pages when not logged in

Preview

[mamigot]

Claude finished @michael-on-code's task —— View job

---

E2E Coverage Review ✅

Reviewed PR #121 for e2e test coverage requirements.

Tasks:

• Step 1: Dismiss stale REQUEST_CHANGES reviews (no stale reviews found)
• Step 2: Identify what changed
• Step 3: Run mechanical coverage check (coverage intact - no new routes)
• Step 4: Read current coverage state
• Step 5: Apply decision logic and post review

Analysis Results:

✅ No new app routes: No new page.tsx files were added in this PR

• Changed files: Dockerfile, nav-bar components, navigation-drawer, tests, and utils/helpers
• This appears to be UI component changes for login/signup buttons without new routes

✅ Coverage state: Current coverage is 100% (222/222 checkpoints, 31 journeys)

✅ Test updates included: The PR includes test updates in:

• components/__tests__/nav-bar.test.tsx
• components/__tests__/navigation-drawer.test.tsx
• utils/__tests__/helpers.test.ts

Review Decision: APPROVED ✅

This is CASE E (no new page.tsx files and no coverage regression). No new app routes were introduced and all existing coverage remains intact. The PR includes appropriate component-level test updates for the navigation changes.

✅ E2E Coverage — No Issues

No new app routes were introduced. All existing coverage is intact.

[mamigot]

Claude finished @michael-on-code's task —— View job

---

E2E Coverage Review ✅

Reviewed PR #121 for e2e test coverage requirements.

Tasks:

• Step 1: Dismiss stale REQUEST_CHANGES reviews (no stale reviews found)
• Step 2: Identify what changed
• Step 3: Run mechanical coverage check (coverage intact - no new routes)
• Step 4: Read current coverage state
• Step 5: Apply decision logic and post review

Analysis Results:

✅ No new app routes: No new page.tsx files were added in this PR

• Changed files: Dockerfile, nav-bar components, navigation-drawer, tests, and utils/helpers
• This appears to be UI component changes for login/signup buttons without new routes

✅ Coverage state: Current coverage is 100% (222/222 checkpoints, 31 journeys)

✅ Test updates included: The PR includes test updates in:

• components/__tests__/nav-bar.test.tsx
• components/__tests__/navigation-drawer.test.tsx
• utils/__tests__/helpers.test.ts

Review Decision: APPROVED ✅

This is CASE E (no new page.tsx files and no coverage regression). No new app routes were introduced and all existing coverage remains intact. The PR includes appropriate component-level test updates for the navigation changes.

✅ E2E Coverage — No Issues

No new app routes were introduced. All existing coverage is intact.

[mamigot]

Claude finished @michael-on-code's task —— View job

---

E2E Coverage Review ✅

Reviewed PR #121 for e2e test coverage requirements.

Tasks:

• Step 1: Dismiss stale REQUEST_CHANGES reviews (no stale reviews found)
• Step 2: Identify what changed
• Step 3: Run mechanical coverage check (coverage intact - no new routes)
• Step 4: Read current coverage state
• Step 5: Apply decision logic and post review

Analysis Results:

✅ No new app routes: No new page.tsx files were added in this PR

• Changed files: nav-bar components, navigation-drawer, tests, and utils/helpers
• This appears to be UI component changes for login/signup buttons without new routes

✅ Coverage state: Current coverage is 100% (222/222 checkpoints, 31 journeys)

✅ Test updates included: The PR includes test updates in:

• components/__tests__/nav-bar.test.tsx
• components/__tests__/navigation-drawer.test.tsx
• utils/__tests__/helpers.test.ts

Review Decision: APPROVED ✅

This is CASE E (no new page.tsx files and no coverage regression). No new app routes were introduced and all existing coverage remains intact. The PR includes appropriate component-level test updates for the navigation changes.

---

[mamigot]

Claude finished @michael-on-code's task —— View job

---

E2E Coverage Review ✅

Reviewed PR #121 for e2e test coverage requirements.

Tasks:

• Step 1: Dismiss stale REQUEST_CHANGES reviews (no stale reviews found)
• Step 2: Identify what changed
• Step 3: Run mechanical coverage check (coverage intact - no new routes)
• Step 4: Read current coverage state
• Step 5: Apply decision logic and post review

Analysis Results:

✅ No new app routes: No new page.tsx files were added in this PR

• Changed files: nav-bar components, navigation-drawer, tests, and utils/helpers
• This appears to be UI component changes for login/signup buttons without new routes

✅ Coverage state: Current coverage is 100% (222/222 checkpoints, 31 journeys)

✅ Test updates included: The PR includes test updates in:

• components/__tests__/nav-bar.test.tsx
• components/__tests__/navigation-drawer.test.tsx
• utils/__tests__/helpers.test.ts

Review Decision: APPROVED ✅

This is CASE E (no new page.tsx files and no coverage regression). No new app routes were introduced and all existing coverage remains intact. The PR includes appropriate component-level test updates for the navigation changes.

---

✅ E2E Coverage — No Issues

No new app routes were introduced. All existing coverage is intact.