Decide how PM-specific features (Jira/GitHub sync, actions) fit a studying-focused product

[nazim117]

Context

The stated main goal of Research Agent is to help with studying and learning new things. But a large, working part of the codebase is built specifically for a project-manager persona: Jira/GitHub sync (sync.py, mcp-server's jira.go/github.go), human-approved write actions (<<DRAFT_ACTION>> in main.py, actions.py), and PM-shaped transcript extraction (decisions/action items/risks — see #63). None of that serves someone studying a subject.

Question to resolve

Pick one before building more study-focused features on top of the current dashboard/wizard:

1. Keep both personas, make it explicit — e.g. a mode switch, or just accept the dashboard serves two different audiences and label things clearly so PM features don't confuse a studying-focused user.
2. De-emphasize/hide PM features by default — keep the code (it works, it's tested) but don't surface Jira/GitHub/actions in the UI unless a project actually has those external refs configured (some of this may already happen implicitly via external_refs).
3. Split into two products/entry points long-term, if the two use cases keep diverging.

Related

#61–#68 all assume "study/learning" is the primary framing going forward — worth deciding this before those land, since it affects how prominently they should live in the UI relative to the existing PM surface area.