Add journal export dispatcher: propose grouping, route to existing skills

[bracyw]

Parent

#677

What to build

The export half of the journal skill: an opt-in dispatcher that turns a ripe note into properly-formatted, ticketed, or documented output by delegating to whichever existing skill already owns that destination. It reads the .journal/ layout and content, proposes how to group notes, proposes the best-fit destination and flow, always confirms, hands off, then offers cleanup. It reimplements no formatting, ticketing, branching, or PR logic, and never contacts GitHub on its own.

Acceptance criteria

• Export reads .journal/ and proposes a grouping: merge a category (many entries to one output), split a single entry (one to many destinations), or standalone; the user can adjust
• It proposes the best-fit destination, biasing hard toward an existing docs area/section before ever proposing a new one
• An unconditional confirm gate shows destination plus reshaped text and waits for approval before anything is created, existing area or not
• It routes by note type to the correct existing skill (log-future-addition, to-issues, to-prd, grill-with-docs) or a plain docs write for recorded research, and reimplements none of their formatting or conventions
• After a successful export it prompts whether to delete the source entry (default keep)
• The journal never pushes or contacts GitHub on its own; all outward actions belong to the delegated flow

Blocked by

Journal capture (Sub-task 1) - the .journal/ layout it reads from