feat(manager): rewire coverage to CMS after import

[lumberman]

Background

apps/manager coverage still reads local job state instead of the Strapi CMS data that has now been imported from the old media API. As a result, /dashboard/coverage shows fake collections derived from job status rather than canonical collections/videos from CMS, and the coverage flow cannot queue work for existing imported assets.

Expected outcome

/dashboard/coverage reads canonical coverage data from Strapi CMS, renders collections using the existing Video.label + childGatewayIds model, loads language geo data from CMS, and can queue jobs for existing imported videos without changing /dashboard/jobs into a content browser.

Acceptance criteria

• /dashboard/coverage renders collections from CMS even when there are no local jobs.
• Coverage no longer groups jobs into fake collections like "Completed Jobs" or "Running Jobs".
• Coverage statuses are derived from CMS subtitles, variants, and metadata fields.
• GET /api/languages serves the geo payload expected by the language selector from CMS data.
• Coverage can queue jobs for existing imported videos using muxAssetId.
• URL-based ingest from the jobs dashboard continues to work unchanged.
• /dashboard/jobs remains a queue/workflow view rather than a content browser.

Possible solution(s)

1. Replace the coverage page's listJobs() dependency with typed CMS GraphQL queries through @forge/graphql.
2. Restore the missing coverage domain modules from the original VideoForge app as a starting point, but map them to CMS-backed reads.
3. Extend POST /api/jobs to accept existing-asset payloads inferred from request shape while keeping the current URL-ingest flow.

References

• docs/plans/2026-03-24-001-feat-manager-coverage-rewire-after-cms-import-plan.md
• apps/manager/src/app/dashboard/coverage/page.tsx
• apps/manager/src/features/coverage/coverage-report-client.tsx
• apps/manager/src/app/api/jobs/route.ts
• videoforge/src/features/coverage/types.ts

[lumberman]

Execution plan

1. Replace /dashboard/coverage server data loading so it reads CMS-backed coverage data instead of listJobs().
2. Recreate the missing coverage domain modules from the old VideoForge app as the starting point (types, submission, estimate-cost, optional refresh helper), but map them to CMS-backed reads instead of gateway data.
3. Add a manager GET /api/languages route backed by CMS language/country data so the existing LanguageGeoSelector can load geo data and remote search results.
4. Extend POST /api/jobs so coverage can queue work for existing imported assets using muxAssetId while preserving the current URL-ingest flow.
5. Reconnect coverage selection, cost estimation, and submit-to-queue behavior, while keeping /dashboard/jobs as the queue view only.
6. Validate with route tests and coverage UI checks that collections come from CMS and coverage no longer depends on .data/jobs.json.

Plan doc for this scope: docs/plans/2026-03-24-001-feat-manager-coverage-rewire-after-cms-import-plan.md

[lumberman]

Updated execution plan

Refined the plan doc to make the implementation decision-complete.

Key clarifications added:

1. Coverage should load from a server-side CMS query + mapper layer, not a client fetch path and not new /api/coverage/* routes.
2. Queueability should be derived from imported CMS relations, specifically VideoVariant.muxVideo.assetId and playbackId.
3. GET /api/languages should stay a thin adapter over CMS GraphQL data, preserving the current LanguageGeoSelector contract.
4. POST /api/jobs needs to explicitly support both current entry shapes because the existing jobs form already posts muxAssetId while the active route still only accepts inputUrl.
5. The scope remains manager-only unless imported CMS data is missing required Mux mappings, in which case that becomes a follow-up issue rather than silent scope expansion.
6. Added repo-specific implementation constraints and risks, including the src/features/coverage/ staging gotcha from the root coverage/ ignore rule.

Updated plan doc:
docs/plans/2026-03-24-001-feat-manager-coverage-rewire-after-cms-import-plan.md