release

To close out and archive a completed workstream, run the release process after QA shows a PASS verdict. It synthesizes your artifacts, generates a changelog, and moves the workstream directory to the archive.

Finalizing a workstream release requires spec.md, plan.md, tasks.md, handoff.md, and qa-report.md as inputs to synthesize the workstream and produce a changelog and status.json.

Yes, you can generate a changelog by applying the release process to your workstream artifacts. It synthesizes spec, plan, tasks, handoff, and QA report files to produce a changelog and update reference docs.

You should run the workstream archival process only when your qa-report.md shows a PASS QA verdict. Running it earlier skips the required validation and prevents accurate changelog generation.

Yes, the release process updates tracked-work records by refreshing them during the archival step. It moves the workstream directory to archive and updates the status to archived.

Archiving a workstream after QA passes preserves knowledge and frees up resources by moving the completed directory to an archive. It also generates a changelog and captures handoff details for future workstreams.