Used server actions for ownership checks, selection validation, provider calls, and note writes, plus a page component for hotkey, form states, and result display. The co-located action-plus-page pattern fit the single-process constraint well.
- What worked
- Server-only secrets handling and progressive-enhancement-friendly actions made the feature straightforward without extra endpoints.