[FE-24] Room-door display page — /display/[workspaceId] (current & next booking)

[yusuftomilola]

Overview

A cheap Android tablet on each meeting-room door showing "In use until 14:00 — Design Sync" or "Free until 15:30" — a signature touch of professionally-run spaces (Robin/Joan devices do exactly this). One always-on web page per room.

Tasks

• New route frontend/app/display/[workspaceId]/page.tsx — standalone full-screen layout, no auth chrome. Auth approach: a signed display token in the query string (?token=) issued by an admin endpoint, or an authenticated device session — check what's simplest with the current guard setup; a tiny backend addition (read-only "current + next booking for workspace" endpoint, public with the signed token) is in scope for this issue — follow the [BE-34] token pattern.
• Display states: FREE (green background; "Free until HH:MM" if a booking is upcoming, else "Free all day") and BUSY (red; booking title/member if permitted, time remaining, "Next: HH:MM–HH:MM").
• Auto-refresh: poll every 30–60s + a clock that updates every second; screen never sleeps into a stale state (handle fetch failures by showing last-known data with a subtle stale indicator).
• Huge typography readable from 3 meters; workspace name always visible; dark-friendly colors (tablets run 24/7).
• Admin: a "Open display page" link (with generated token) per meeting room on /admin/workspaces.

Acceptance Criteria

• The page reflects a new booking within one refresh cycle without any interaction.
• Free↔busy transitions happen at the right minute (client clock + booking times).
• Runs for hours without memory growth or dead intervals (test with the tab throttled/backgrounded).

Dependencies

Better with [BE-17] (hourly bookings); works with daily bookings meanwhile.

Notes for Contributors

Good first issue with a fun visual result. Comment below to be assigned.

[devwums]

@devwums has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I have reviewed this issue and its acceptance criteria carefully. The requirements are clear and well-scoped (large complexity). I have hands-on experience with testing and can implement this following the patterns and conventions already in the codebase. I will deliver complete, tested code that satisfies every acceptance criterion without requiring follow-up corrections. I can start immediately and am happy to discuss approach details with the maintainer beforehand.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @devwums to this issue.

[drips-wave]

Congratulations, @devwums! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @devwums: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊