Cannot view other users' calendar via WorkIQ — calendars are accessible in Outlook but return empty results

Summary

When querying other users' calendars through WorkIQ (both via MCP and M365 Copilot), the response returns no meetings found. However, the same calendars are fully accessible through the Outlook client
with delegated access.

Environment

• WorkIQ usage: Copilot CLI plugin (MCP) and M365 Copilot
• Platform: Linux (WSL)
• Outlook access: Delegated calendar access is configured and working

Steps to Reproduce

1. Confirm that another user's calendar is viewable in Outlook via delegated access
2. Query WorkIQ: "What are [User]'s meetings scheduled for today?"
3. WorkIQ returns: "No meetings were found"
4. Try the same prompt in M365 Copilot (not WorkIQ) — same empty result
5. Verify in Outlook — the user does have meetings scheduled

Expected Behavior

WorkIQ should return the other user's calendar events, consistent with the delegated access permissions already granted and functional in Outlook.

Actual Behavior

WorkIQ returns "0 meetings found" for all queried users, despite confirmed calendar visibility in Outlook.

Additional Context

• This issue reproduces with multiple different users, not just one specific person.
• The same query for my own calendar works correctly via WorkIQ.
• M365 Copilot also fails with the same result, suggesting this is a Microsoft Graph API layer issue rather than a WorkIQ-specific bug.
• Possibly related to delegated calendar permissions not being exposed via Graph API, even when they work via Exchange protocols (EWS/MAPI) used by Outlook.
• Similar pattern to #22 (SharePoint file access) and #21 (OneNote access) where resources accessible via native clients are blocked through the API layer.

No repository files, tests, or entry points are identified in the issue. Reproduce the delegated-calendar query through the WorkIQ MCP and M365 Copilot paths, then compare their results with Outlook and investigate whether the Microsoft Graph API exposes the delegated permissions. Done means the access behavior is fixed or the external API limitation is documented with supporting evidence.