review-archive

To archive completed manual checks with traceability, migrate completed items from the tasks artifact into docs/manual-review-archive.md. This process preserves original #N numbering and maintains a clear history for auditing.

Yes, you can archive a specific range of tasks by specifying scoped inputs like #1~#5. If no scope is provided, the system defaults to migrating only items marked completed within the tasks artifact.

After archiving completed checks, the source tasks artifact status is updated accordingly. The migrated items are written as a new section under the separator in the manual review archive file to maintain provenance.

An audit trail for completed review tasks works by writing archived items into a centralized markdown documentation file. This preserves the original task numbering and provides a clear historical record of what was checked and completed.

Yes, you can automatically migrate all marked done items by running the archive all command. This moves all completed checks from the task list into the documentation archive, effectively serving as a change log.

No, archiving tasks does not remove the original numbering. The migration process explicitly preserves #N numbering in the archive file to ensure complete traceability and historical reference.