spec-driven-promote

To merge next-version documentation, collect Markdown files from docs/v{next}, map them to existing equivalents in docs/features/ and docs/topics/, update cross-references, and remove the obsolete folder to maintain a single source of truth.

The best way to consolidate versioned Markdown files is to promote content from docs/v{next} into current directories, update internal links to reflect new locations, and delete the next-version folder after validating structure integrity.

Documentation promotion handles cross-references by updating links during the merge process, ensuring all references point to the current docs/features/ and docs/topics/ directories instead of the deprecated docs/v{next} folder.

No, you cannot keep the docs/v{next} folder after promotion. The integration policy enforces removing docs/v{next} after successful content merge to prevent fragmentation and documentation drift.

During next-version documentation consolidation, OVERVIEW.md files are excluded from the candidate collection process, meaning they are not mapped or merged into the current docs/features/ or docs/topics/ directories.

Versioned documentation drifts from current customer-facing docs when next-version content in docs/v{next} is not integrated into existing structures, causing fragmentation across separate directories over time.