chore(release): promote CHANGELOG to v0.20.0, bump version, update ROADMAP

[MScottAdams]

Summary

Release engineering for v0.20.0 -- the Phase 2 vBRIEF Architecture Cutover version boundary.

Closes #335

Changes

Version bump:

• Taskfile.yml VERSION: 0.19.0 -> 0.20.0
• run CLI VERSION: 0.4.3 -> 0.20.0
• Go installer version set via ldflags at build time (no manual change needed)

CHANGELOG.md promotion:

• Promoted [Unreleased] to [0.20.0] - 2026-04-13
• Added new empty [Unreleased] section
• Added Breaking Changes subsection documenting all 6 breaking changes:
  • SPECIFICATION.md/PROJECT.md replaced with deprecation redirects
  • All skills renamed from deft-* to deft-directive-*
  • vbrief/ directory restructured with lifecycle folders
  • New task commands (scope:*, roadmap:render, project:render, migrate:vbrief, vbrief:validate)
  • PROJECT-DEFINITION.vbrief.json replaces PROJECT.md + specification.vbrief.json
  • Migration path via task migrate:vbrief

ROADMAP.md update:

• Moved all 21 Phase 2 stories (RFC: vBRIEF-centric document model for Deft Directive #309-Story T: Release and version boundary items (v0.20.0) #335) to Completed section with v0.20.0 tag and 2026-04-13 dates
• Cleared Phase 2 body (replaced with completion note)
• Struck through all Phase 2 entries in Open Issues Index

CI/PR template:

• Reviewed .github/workflows/ci.yml and release.yml -- no skill names or old document model references
• PR template has no deft-* skill references to update

Related Issues

Closes #335

Checklist

• /deft:change <name> -- N/A (release engineering, <3 surface changes)
• CHANGELOG.md -- promoted [Unreleased] to [0.20.0] with Breaking Changes
• ROADMAP.md -- all Phase 2 stories moved to Completed
• Tests pass locally -- 1383 passed, 1 pre-existing failure (broken See also link in deft-directive-swarm/SKILL.md -> ../deft-review-cycle/SKILL.md, not introduced by this PR), 2 xfailed

Post-Merge

• Verify issue auto-close: After squash merge, confirm Story T: Release and version boundary items (v0.20.0) #335 closed -- gh issue view 335 --json state --jq .state

[greptile-apps]

Greptile Summary

Release engineering boundary for v0.20.0, the Phase 2 vBRIEF Architecture Cutover milestone. The PR bumps VERSION in Taskfile.yml and run, promotes [Unreleased] to [0.20.0] - 2026-04-13 in CHANGELOG.md (with all six breaking changes documented), and closes out all 21 Phase 2 stories in ROADMAP.md. The only minor note is a duplicate ### Added section in the v0.20.0 changelog block.

Confidence Score: 5/5

Safe to merge — pure release-engineering changes with no logic modifications.

All four changed files contain only documentation and version-string updates. No logic, tests, or build pipelines are modified. The single finding is a P2 style note about duplicate CHANGELOG section headings that does not affect functionality.

No files require special attention beyond the cosmetic CHANGELOG structure note in CHANGELOG.md.

Important Files Changed

Filename	Overview
CHANGELOG.md	v0.20.0 section promoted from [Unreleased] with Breaking Changes, Added, and Changed entries; contains two separate ### Added sub-sections separated by ### Changed, which is unconventional for Keep a Changelog
Taskfile.yml	VERSION variable bumped from 0.19.0 to 0.20.0; no other changes
run	Python CLI VERSION bumped from 0.4.3 to 0.20.0 to align with the project version; intentional per PR description
ROADMAP.md	Phase 2 body cleared with completion note; all 21 stories (#309–#335) moved to Completed with v0.20.0 tag and 2026-04-13 dates; Open Issues Index fully struck-through for Phase 2 entries; audit trail footnote appended

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR 335 merged] --> B[Taskfile.yml VERSION 0.19.0 to 0.20.0]
    A --> C[run CLI VERSION 0.4.3 to 0.20.0]
    A --> D[CHANGELOG.md]
    A --> E[ROADMAP.md]

    D --> D1[Unreleased promoted to 0.20.0 - 2026-04-13]
    D1 --> D2[Breaking Changes: 6 entries]
    D1 --> D3[Added and Changed: 21 Phase 2 stories]
    D --> D4[New empty Unreleased section added]

    E --> E1[Phase 2 body cleared with completion note]
    E1 --> E2[21 stories 309 to 335 moved to Completed]
    E2 --> E3[Open Issues Index Phase 2 entries struck through]

    B & C --> F[Version aligned at v0.20.0]

Loading

Prompt To Fix All With AI

This is a comment left during a code review.
Path: CHANGELOG.md
Line: 33

Comment:
**Duplicate `### Added` section in v0.20.0**

The `[0.20.0]` release block contains two separate `### Added` sub-sections (lines 20 and 33) with a `### Changed` block between them. Keep a Changelog convention expects each section type to appear at most once per release entry; some CHANGELOG parsers (e.g. `git-cliff`, `release-please`, changelog linters) may surface a warning or silently drop the second block. Consider consolidating both `### Added` groups into a single section.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (2): Last reviewed commit: "fix: remove duplicate/malformed CHANGELO..." | Re-trigger Greptile}