feat(documents): surface filesystem work-products in Document Center

The Document Center only read the `documents` table, which is prose
content POSTed via /api/documents. Everything the agents wrote via
`bash` / `write` / `edit` — the bulk of their output on a real
project — landed in `work_products` and never appeared on the page.
Operators saw "0 items" after a full night's run.

Lift work_products into the same UI:

  - `listWorkProductsForCompany` returns a newest-first slice with a
    500-row cap so the snapshot stays bounded.
  - `ProfileSnapshot.workProducts` flows through `useCompanyData` as
    `companyWorkProducts`, filtered to the current company.
  - `DocumentCenter` renders two labelled sections in order — prose
    documents (editable) on top, files & deliverables below. Each
    work-product row opens the underlying URL or filesystem path
    when clickable, so the agent's bash-generated markdown, PRs,
    and artifacts are one click away.

`WorkProductRecord` lifts into `@shared/types/records-extended` so
the renderer, snapshot, and database shells all reference the same
shape. The store-test fixture learns about the new field.

src/renderer/i18n/en.ts

@@ -871,6 +871,8 @@ export const en: Record<string, string> = {
 
   // ── Company Operations ──
   "ops.documentCenter": "Document Center",
+  "ops.documentsProse": "Prose documents",
+  "ops.documentsWorkProducts": "Files & deliverables",
   "ops.knowledgeBase": "Knowledge Base",
   "ops.meetings": "Meetings",
   "ops.sprintBoard": "Sprint Board",

src/renderer/i18n/zh.ts

@@ -871,6 +871,8 @@ export const zh: Record<string, string> = {
 
   // ── 公司运营 ──
   "ops.documentCenter": "文档中心",
+  "ops.documentsProse": "文稿",
+  "ops.documentsWorkProducts": "文件与交付物",
   "ops.knowledgeBase": "知识库",
   "ops.meetings": "会议",
   "ops.sprintBoard": "迭代看板",