integrate with existing DigDir CMS if possible

## Description
A time-boxed discovery spike to determine whether integration with Digdir's existing CMS is technically feasible and operationally worthwhile for managing KI Hub V2 content.

## Business Goal
KITT needs a sustainable, low-friction way to manage editorial content. A CMS integration could remove the need for content editors to use GitHub — but only if the right system is accessible, compatible, and worth the integration effort.

## Spike questions to answer
1. Does Digdir have an accessible CMS with a usable API or export capability?
2. Is the data model compatible with KI Hub's content needs?
3. What is the integration effort, and how does it compare to alternative approaches?

## Expected output
A written recommendation (viable / not viable / conditional) with supporting rationale, proposed approach if viable, and estimated effort. This output becomes the direct input for a follow-up story if integration is viable — or closes the question if it is not.

## Acceptance Criteria
- The spike is completed within the agreed timebox
- A written recommendation exists and has been reviewed by the KITT team
- If viable: a follow-up story is created with defined scope and acceptance criteria
- If not viable: this issue is closed with the documented reasoning on record

## Dependencies
- Access to information about Digdir's existing CMS systems — coordinate with the KITT board team

## Parent epic
Epic 3 — Content, News & Editorial (#40)

No files, tests, or entry points are named. Start by coordinating with the KITT board team to identify Digdir's accessible CMS and API or export options, then compare its data model and integration effort with alternatives. Done means a reviewed viable, not viable, or conditional recommendation, with a follow-up story if viable or documented closure reasoning if not.

Written by the indexing model from the issue text.