chore: release v0.15.0

[MScottAdams]

Release v0.15.0 — CHANGELOG promotion and ROADMAP update.

Changes

• Promote CHANGELOG [Unreleased] to [0.15.0] - 2026-04-09
• Add version link references for v0.14.0 through v0.15.0
• ROADMAP: move Project should be fully bootstrapped with its own framework #51, deft-roadmap-refresh skill: add explicit table row format to prevent double-pipe || index entries #221, refactor: rename RWLDL skill/tool to remove acronym collision and add auto-suggestion triggers #226, docs: README should document where user artifacts are stored in a consumer project #234, Roadmap refresh does not create or surface spec task coverage for triaged issues #248 to Completed
• ROADMAP: strike through in Open Issues Index, remove from Phase 2 body

Release scope (v0.14.2 -> v0.15.0, minor bump)

• New content: strategies/rapid.md, strategies/enterprise.md, docs/getting-started.md
• Skill rename: deft-rwldl -> deft-pre-pr
• Skill improvements: roadmap-refresh scaffolding, swarm spec coverage
• Doc: README artifact storage, stale ref cleanup

[greptile-apps]

Greptile Summary

This is a release-housekeeping commit that promotes the [Unreleased] CHANGELOG section to [0.15.0] - 2026-04-09, adds the corresponding compare link references for v0.14.0 through v0.15.0, and updates ROADMAP.md by moving five completed issues (#51, #221, #226, #234, #248) to the Completed section, striking them through in the Open Issues Index, and removing them from the Phase 2 body. All structural changes are mechanically correct and consistent with the project's established release conventions.

Confidence Score: 5/5

Safe to merge — documentation-only release commit with correct structure and a single minor prose fix available.

All changes are limited to CHANGELOG.md and ROADMAP.md. The promotion, link references, completed-item moves, and index strikethroughs are all mechanically correct. The only finding is a P2 stale "[Unreleased]" prose reference in the v0.14.2 entry that can be fixed now or in a follow-up without affecting correctness.

No files require special attention.

Vulnerabilities

No security concerns identified. Changes are limited to documentation files (CHANGELOG.md and ROADMAP.md) with no code, configuration, or credential modifications.

Important Files Changed

Filename	Overview
CHANGELOG.md	Promotes [Unreleased] to [0.15.0] with correct date and adds link references for v0.14.0–v0.15.0; one stale "[Unreleased]" prose reference in the v0.14.2 entry (line 32) should be updated to "[0.15.0]"
ROADMAP.md	Correctly moves #51, #221, #226, #234, #248 to Completed with v0.15.0 dates, strikes through all five in the Open Issues Index, removes them from Phase 2 body, and appends a v0.15.0 update footnote

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["[Unreleased] section\n(#51, #221, #226, #234, #248)"] -->|"Promote to v0.15.0"| B["[0.15.0] - 2026-04-09"]
    B --> C["Add link reference\n[0.15.0]: compare/v0.14.2...v0.15.0"]
    D["[Unreleased] link"] -->|"Update target"| E["compare/v0.15.0...HEAD"]
    F["ROADMAP Phase 2 body\n(#51, #221, #226, #234, #248)"] -->|"Remove entries"| G["Phase 2 body\n(items removed)"]
    H["Open Issues Index\n#51, #221, #226, #234, #248"] -->|"Strike through"| I["~~#51~~ ~~#221~~ ~~#226~~\n~~#234~~ ~~#248~~\ncompleted -- v0.15.0"]
    J["Completed section"] -->|"Prepend 5 entries"| K["#51, #221, #226,\n#234, #248 -- v0.15.0"]

Loading

Prompt To Fix All With AI

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

Comment:
**Stale `[Unreleased]` cross-reference after promotion**

The v0.14.2 entry for #251 reads "renamed in [Unreleased]", but this PR promotes `[Unreleased]` to `[0.15.0]`. After the release, this inline prose link points to an empty section rather than to the actual version that contains the rename. It should be updated to `[0.15.0]`.

```suggestion
- **Semantic contradiction check for !/⊗ rules** (#251, t1.12.3): Added 2 `!` rules to `skills/deft-build/SKILL.md` pre-commit checklist and `skills/deft-pre-pr/SKILL.md` Read phase (formerly `deft-rwldl`, renamed in [0.15.0]) -- when adding a `!` or `⊗` rule, search the same file for conflicting `~/≉` rules referencing the same term; when strengthening a rule, verify no weaker-strength duplicate remains; added `⊗` anti-pattern to both skills prohibiting adding a prohibition without scanning for softer-strength conflicts
```

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

_{Reviews (1): Last reviewed commit: "chore: release v0.15.0" | Re-trigger Greptile}