Journal skill: export dispatcher end-to-end via log-future-addition

[bracyw]

Parent

#677

What to build

The export half of the journal skill as a complete, opt-in pipeline — wired to a single downstream flow so every gate is proven end-to-end. Export reads the .journal/ layout plus content and proposes how to group notes: many-to-one (merge a category's entries into one output) and one-to-many (split a single entry holding distinct notes across destinations). The user adjusts the proposal.

Destination selection biases hard toward an existing docs area/section; a brand-new section is a last resort and is always surfaced for approval. An unconditional confirm gate shows the chosen destination and the reshaped text and waits for approval before anything is created — existing area or not.

For this slice the dispatcher delegates only the rough-idea flow, to log-future-addition (already merged; a stated dependency of #677), which files an un-triaged issue. The journal itself never pushes or contacts GitHub — all outward action is owned by the delegated skill. After a successful export the skill prompts whether to delete the source entry (default keep).

Acceptance criteria

• Export reads .journal/ and proposes a grouping (standalone, many-to-one merge, one-to-many split); user can adjust
• Destination selection prefers an existing docs area; any new section is surfaced for explicit approval
• Confirm gate shows destination + reshaped text and blocks creation until approved, even for existing areas
• A rough-idea note exports by delegating to log-future-addition, producing an un-triaged issue
• The journal skill never pushes or contacts GitHub itself
• After export, the skill prompts whether to delete the source entry, defaulting to keep

Blocked by

• Journal skill: local capture into gitignored .journal/ #678