spike: native assistant shortcuts integration

[SebastianBoehler]

Issue Spec: Native Assistant Shortcuts Spike

Summary

Evaluate whether Siri Shortcuts, App Intents, Android intents, or similar native assistant integrations are useful as an input layer for StudyOS.

Goal

Decide whether native assistants can provide value without compromising customization, privacy expectations, or project independence.

Scope

• Research current native assistant integration options for the app platform.
• Prototype one small action if feasible, for example "open StudyOS next action" or "ask StudyOS what is next."
• Compare privacy and data routing implications.
• Compare customization limits against the local agent approach.
• Document whether this should be part of the demo, a later enhancement, or rejected.

Out Of Scope

• Building the whole StudyOS assistant around Siri, Google Assistant, or one vendor API.
• Depending on hosted assistant processing for sensitive university data.
• Full production shortcut coverage.

Acceptance Criteria

• Platform capabilities and limitations are summarized.
• At least one concrete StudyOS action is evaluated.
• Privacy tradeoffs are clearly stated.
• The spike compares native assistant integration against push-to-talk/hotword/local agent options.
• The output includes a recommendation: adopt, keep as optional, defer, or reject.

Gates To Pass

• Feasibility gate: the target platform APIs are checked against current documentation or a working prototype.
• Lock-in gate: the approach does not make the core app dependent on one assistant vendor.
• Privacy gate: any external processing path is documented.
• UX gate: the native shortcut adds real convenience over opening the app manually.
• Maintenance gate: implementation effort is small enough for the course timeline.
• Decision gate: the team can decide whether to invest further after the spike.

Suggested Branch

spike/native-assistant-shortcuts