Evaluate orphaned community-feed page branch

[ashryanbeats]

Context

The hackathon audit found origin/feature/community-feed, an orphaned branch with no associated PR. It adds a separate /community-feed page with filters, but appears to use static/example data and overlaps with the homepage community feed plus notifier direction.

Known concerns

• No open PR is associated with the branch.
• Uses static/example community feed data.
• Imports zod without adding it to package.json.
• Conceptually overlaps with the existing homepage community feed and the Community Feed Notifier work.

Goal

Decide whether anything from the branch is worth keeping. If useful, extract the UI/product ideas into a clean implementation. Otherwise archive/delete the branch.

Suggested approach

• Inspect the branch once for reusable UI ideas.
• Do not merge the branch directly.
• If the page is still desired, define how it differs from the homepage feed.
• Use real generated feed data rather than static/example data.
• Add any missing dependencies deliberately, or avoid them if unnecessary.
• Run full checks before opening any replacement PR.

Outcome

Either create a fresh landable PR for a real community feed page, or delete/archive origin/feature/community-feed after confirming no useful work remains.