Feature/create event UI polish

[monicataccoli-byte]

Completed rebase and resolved merge conflicts.

Cleaned and stabilised the EventDetailsPage integration with:

• API-connected event fetching
• updated event routing
• facilitator navigation actions
• cleaned App.jsx routing conflicts
• dashboard UI cleanup

Also resolved overlapping session/event terminology conflicts during rebase.

PR is now rebased onto latest main and ready for review/merge.

[netlify]

✅ Deploy Preview for workshopnavigator ready!

Name	Link
🔨 Latest commit	0480ddd
🔍 Latest deploy log	https://app.netlify.com/projects/workshopnavigator/deploys/6a0be1ed97e1620008e84fac
😎 Deploy Preview	https://deploy-preview-24--workshopnavigator.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[monicataccoli-byte]

Completed API integration testing and resolved the backend event retrieval issue affecting the attendee event flow.

Verified:

• working /events/ backend endpoint
• successful event retrieval through /event/1
• attendee join flow
• frontend/backend integration

Rebased and pushed latest updates.

[monicataccoli-byte]

Completed end-to-end attendee event workflow integration and testing.

Changes include:

• Confirmed frontend/backend API communication
• Successfully generated and resolved live event codes
• Verified attendee session routing
• Confirmed QuestionForm, audience questions, live polls, and GetSlidesCard rendering
• Tested QR code event join workflow
• Resolved previous “Event not found” issues

Testing completed:

• Create event flow
• Join event flow
• Event code lookup
• Attendee session page rendering
• End-to-end workflow validation

[monicataccoli-byte]

PR#24 After reviewing and comparing the branch against the current main architecture, I identified a number of inconsistencies caused by earlier rebases and iterative recovery work (including outdated routes, stale service logic, duplicated files, and mismatched component versions).

To reduce merge risk and avoid introducing unstable or outdated code into main, I’ve created a new clean stabilization branch where the working functionality is being manually compared, validated, and selectively reconstructed against the current main branch.

The useful functionality and UI improvements from this PR are still being preserved, but only after verification against the current backend/frontend architecture.

For safety and maintainability, this PR should now be closed and replaced with a new cleaned PR containing the stabilized final implementation.