[codex] support custom outline generation

[NewRudy]

What changed

• Add a custom outline upload flow for technical plan outline generation.
• Persist uploaded outline metadata and parsed markdown in the technical plan workspace.
• Allow outline generation to use the uploaded outline as the base structure, then complement it against tender requirements and knowledge base documents.
• Expose the IPC/preload/types/UI wiring needed to import Word, PDF, or Markdown outline drafts.

Why

Users often already have a preferred technical-bid outline. This lets them provide that outline as the generation skeleton instead of always starting from tender requirements only.

Impact

The default generation path remains unchanged. When a custom outline is uploaded and selected, the system extracts that outline first and uses it as the base for AI-assisted completion.

Validation

• npm run build
• node --check electron/services/outlineGenerationTask.cjs
• node --check electron/services/technicalPlanStore.cjs
• node --check electron/services/sqliteDatabase.cjs
• node --check electron/ipc/technicalPlanIpc.cjs
• node --check electron/preload.cjs

[FB208]

@codex review