Add temporary notify keep-me-informed page #27

Merged

florianbeisel merged 1 commit from clawteam/rauchbar-dev/site-foundation-notify-page into main

2026-03-26 08:45:18 +01:00

florianbeisel commented

2026-03-26 08:35:54 +01:00

(Migrated from github.com)

Summary

add a temporary /notify keep-me-informed route without changing the default route yet
implement the minimal pathname-based route split in the site app
add the supporting styles for the new notify surface

Verification

corepack pnpm install --frozen-lockfile
corepack pnpm --filter @rauchbar/site build
corepack pnpm --filter @rauchbar/site typecheck

## Summary - add a temporary /notify keep-me-informed route without changing the default route yet - implement the minimal pathname-based route split in the site app - add the supporting styles for the new notify surface ## Verification - corepack pnpm install --frozen-lockfile - corepack pnpm --filter @rauchbar/site build - corepack pnpm --filter @rauchbar/site typecheck

florianbeisel commented

2026-03-26 08:39:15 +01:00

(Migrated from github.com)

No blocking findings on PR #27 at head 3a79fdafdc. I verified this in a clean PR worktree with:\n\n- corepack pnpm install --frozen-lockfile\n- corepack pnpm --filter @rauchbar/site build\n- corepack pnpm --filter @rauchbar/site typecheck\n- corepack pnpm --filter @rauchbar/site test\n\nI also checked the visible surface locally with agent-browser against the PR worktree. The new route renders separately from , and the added notify page stayed within the mobile viewport in that local review. The existing homepage mobile overflow still reproduces, but it predates this diff and is not introduced by the notify-route slice itself.

No blocking findings on PR #27 at head 3a79fdafdc7b59e6888f56d9f92b9ad468a313a2. I verified this in a clean PR worktree with:\n\n- corepack pnpm install --frozen-lockfile\n- corepack pnpm --filter @rauchbar/site build\n- corepack pnpm --filter @rauchbar/site typecheck\n- corepack pnpm --filter @rauchbar/site test\n\nI also checked the visible surface locally with agent-browser against the PR worktree. The new route renders separately from , and the added notify page stayed within the mobile viewport in that local review. The existing homepage mobile overflow still reproduces, but it predates this diff and is not introduced by the notify-route slice itself.

florianbeisel commented

2026-03-26 08:39:34 +01:00

(Migrated from github.com)

No blocking findings on PR #27 at head 3a79fdafdc.

I verified this in a clean PR worktree with:

corepack pnpm install --frozen-lockfile
corepack pnpm --filter @rauchbar/site build
corepack pnpm --filter @rauchbar/site typecheck
corepack pnpm --filter @rauchbar/site test

I also checked the visible surface locally with agent-browser against the PR worktree. The new notify route renders separately from /, and the added notify page stayed within the mobile viewport in that local review. The existing homepage mobile overflow still reproduces, but it predates this diff and is not introduced by the notify-route slice itself.

No blocking findings on PR #27 at head 3a79fdafdc7b59e6888f56d9f92b9ad468a313a2. I verified this in a clean PR worktree with: - corepack pnpm install --frozen-lockfile - corepack pnpm --filter @rauchbar/site build - corepack pnpm --filter @rauchbar/site typecheck - corepack pnpm --filter @rauchbar/site test I also checked the visible surface locally with agent-browser against the PR worktree. The new notify route renders separately from /, and the added notify page stayed within the mobile viewport in that local review. The existing homepage mobile overflow still reproduces, but it predates this diff and is not introduced by the notify-route slice itself.