[Draft] Explore friend-aware event discovery with VRChat social context

[BASIC-BIT]

Problem

Friend-aware context could make VRDex event discovery much more useful: people may want to know whether VRChat friends are connected to, interested in, or attending an event. This needs careful privacy and platform-boundary design before implementation.

Scope

• define what friend-aware event discovery means for VRDex
• evaluate opt-in VRChat friend-list import or linking boundaries
• define how friend-interest signals differ from public attendance, lineup, or event popularity
• define privacy-safe display rules for friend-derived context
• leave room for home-page and event-page modules such as friends interested

Non-goals

• scraping private presence
• public attendance claims without consent
• background polling of friend presence
• importing private friend data without explicit user authorization
• implementing VRChat integration in this issue

Acceptance criteria

• friend-aware discovery is captured as an intentional future feature
• VRChat data and privacy boundaries are explicit
• the model avoids equating friends, interest, attendance, and live presence
• opt-in and disconnect/delete expectations are documented
• the direction is clear enough to guide later integration work

Related

• [Draft][Epic][v0.5] Events and profile associations #7
• [Draft] Document public API posture, rate limiting, and open platform rules #39
• [Draft] Add Google Calendar sync/export direction for event workflows #41

[BASIC-BIT]

Follow-up issue filed from the v1.5 event automation triage:

• [Draft] Evaluate optional VRChat MCP bridge tools for event workflows #122 for optional VRChat MCP bridge tools in event workflows.

Linking here because local VRChat context, friend-aware discovery, and operator-only presence/readiness signals need shared privacy boundaries.