Story: Port domain concept notes to knowledge documents

Convert nine personal domain notes from /home/marco/Development/Notebooks/summaries/ into v2 knowledge documents under doc/knowledge/domain/. The notes cover FX volatility surfaces, compute infrastructure, P&L attribution, pricing configuration, rates and curves bootstrapping, reporting, risk reporting, time structures/tenors, and the trade blotter. They need to be split where appropriate, cross-linked, and updated to use ORE Studio terminology (e.g. "compute engine" rather than "grid", ORE Studio's report/batch concepts rather than generic "job" language).

• All nine source notes processed; none silently dropped.
• reporting.org (already marked superseded) merged into the risk-reporting and pl-attribution documents — not ported as a standalone doc.
• Each resulting knowledge document is a valid v2 .org file with correct frontmatter (#+type: knowledge, UUID, #+filetags:, etc.).
• Documents placed under doc/knowledge/domain/ with one file per coherent concept; a note that covers two distinct concepts is split into two files with a cross-link between them.
• Grid/job terminology updated to ORE Studio equivalents:
  • "grid" → "compute engine"
  • "Job Set Definition / Job Definition" → ORE Studio batch/run concepts (or explicitly noted as an unresolved mapping if no equivalent exists yet)
  • "trade blotter" section cross-linked to the ORE Studio Qt UI concepts (TradeDetailDialog, instrument view) where applicable.
• Every new knowledge doc linked from doc/knowledge/domain/knowledge.org (or the relevant index) so it is reachable from the graph.

• Implementing any functionality described in the notes (this story is documentation only).
• Resolving every terminology gap — notes can flag unresolved mappings for a follow-up story.
• Porting notes that are not in the summaries/ directory.