Prompt: Implement CMS Issue

Use in anuvax-cms after $anuva-development:linear-implement-issue validates the issue.

Implement Anuva Linear issue {{ISSUE_ID}} in anuvax-cms.

Treat the normalized issue kind, its Product Main contract or standalone
preflight, and approved contracts as scope. Inspect the repository and applicable
AGENTS.md instructions. Refuse inconsistent ownership, status, dependencies,
marker, or inputs.

For an implementation child, show the exact
`anuva work start {{ISSUE_ID}} --confirm` mutation and obtain approval before
running it. For a marked standalone issue, verify its guarded intake branch; do
not run the child start transition. Revalidate repository ownership and Product
Main documentation disposition before creating artifacts. Then create
docs/changes/{{CHANGE_FOLDER}}/index.md and
docs/changes/{{CHANGE_FOLDER}}/ImplementationPlan.md before changing code. The
plan must map each acceptance check to code areas, tests, documentation, and
integration dependencies. Ensure MkDocs and preview the plan.

Then end the current turn. Do not change implementation code, configuration,
migrations, tests, durable behavior docs, ImplementationLog.md, or
CompletionReport.md, and do not create a PR, until a subsequent user message
explicitly approves this exact ImplementationPlan. The original skill
invocation, Linear status, Product Main approval, and CLI `--confirm` do not
count. Never infer approval or continue in the same turn. If the plan changes
materially, preview it and repeat this mandatory approval gate.

After approval, implement only the CMS-owned behavior. Maintain
ImplementationLog.md with decisions, deviations, and commands. Add or update
unit/integration tests and relevant Playwright tests. Run the repository lint,
typecheck, tests, Playwright scope, and strict MkDocs build.

Create CompletionReport.md containing acceptance-check evidence, exact commands
and results, changed docs, known limitations, integration notes, and rollback or
recovery considerations. Update the change-folder `index.md`, validate that every
docs folder has an index, and return exact Cloudflare preview links for all changed
docs. Create and link a draft GitHub PR through the Anuva CLI, then move the
Linear issue to In Review. Do not merge or mark Done in this workflow.

For a standalone issue with a `Required` Product Main documentation disposition,
create only the recorded bounded companion after the implementation PR exists,
strictly preview it, and create one linked draft docs PR through
`anuva repository-change docs`. A child or `Not required` issue must not create
that companion.