Notion Factory Tasks DB → intake manifest generator

[khaliqgant]

Deliverable

A generator that queries the Factory Tasks Notion database and emits the Factory intake manifest (the NotionIntakeManifest shape consumed by src/intake/notion.ts), so rows set to Ready for Agent become dispatchable Factory tasks.

Context

• Factory's Notion intake (src/intake/notion.ts, PR feat(intake): deliver private Notion specs across fleet nodes #215) reads a manifest of {page, bootstrap:{authorizedPageId, reason, status:"ready", title, recipe, summary, targets:[{repo,labels} | {projectPath,node}]}}, mounts each authorized page, and publishes a GitHub issue Factory then dispatches (idempotent by source key). It does not read a Notion database directly — this generator bridges that gap.
• Source DB: Factory Tasks — https://app.notion.com/p/813700d768e14cc3b0348d1459f08df3 (data source collection://a7fb83ad-c667-4003-a1dc-132c6826aac1).
• Tracking row: https://app.notion.com/p/3b46800c1c90814c8b09c25a70b7b4bc

Mapping (DB row → bootstrap)

• page / authorizedPageId ← the row's own Notion page id
• include only rows with Status = Ready for Agent (→ status: "ready")
• title ← Task · recipe ← Recipe · summary ← page body (the brief) · reason ← Reason
• targets ← Repo + Labels → {repo, labels} OR Project Path + Node → {projectPath, node}
• Route labels merged into the issue labels

Definition of done

• CLI/script emits a manifest that passes manifestSchema (zod) validation from the live DB.
• Only Ready for Agent rows are included; re-runs are idempotent.
• Round-trips through runNotionIntake to publish/refresh GitHub issues.
• Tests cover both a repo-target row and a workspace-target (projectPath/node) row.

Safety gates

Do not merge; open a PR parked in human-review. Do not auto-flip any DB row's Status — humans move a row to Ready for Agent.

---

Recipe: single. Filed from the Factory Tasks Notion DB.