feat(manager): persist CMS sync job context

[lumberman]

Summary

• add typed manager keyword support and persistent enrichment-job options to the CMS GraphQL contract
• persist the related CMS video and notifyCms intent when /api/enrich creates Manager jobs
• update the feat-002 plan with Unit 1 and Unit 2 progress

Validation

• pnpm install --frozen-lockfile
• pnpm --filter @forge/graphql generate
• pnpm --filter @forge/manager typecheck
• pnpm --filter @forge/graphql typecheck
• pnpm --filter @forge/cms typecheck
• pnpm --filter @forge/manager lint
• pnpm --filter @forge/graphql lint
• pnpm --filter @forge/cms lint
• pnpm --filter @forge/cms test
• pnpm --filter @forge/manager test (package currently prints no tests configured)
• pnpm format:check -- apps/cms/src/api/enrichment-job/content-types/enrichment-job/schema.json apps/cms/schema.graphql apps/manager/src/app/api/enrich/route.ts apps/manager/src/lib/state.ts apps/manager/src/types/job.ts docs/plans/2026-04-23-001-feat-manager-metadata-cms-sync-plan.md packages/graphql/src/graphql-env.d.ts
• git diff --check

Residual Review Findings

• Residual actionable work: none.

Follow-up Scope

• Unit 3 remains: implement the manager-side metadata-to-CMS keyword sync service.
• Unit 4 remains: wire the cms_notify workflow step after metadata succeeds.
• Unit 5 remains: run end-to-end CMS linkage and idempotency verification once Units 3-4 land.