Changelog
Current highlights
Section titled “Current highlights”- Flow-Next 1.1.4 makes
## Acceptance Criteriathe canonical spec heading - Acceptance criteria parsing remains tolerant of legacy
## Acceptanceand lowercase## Acceptance criteria - Flow-Next 1.1.3 aligns cross-spec plan-sync on
planSync.crossSpec - Repo-root
SPEC.md/spec.mdtemplate discovery for project-customized spec scaffolds /flow-next:setupcan opt into a rootSPEC.mdwithout clobbering custom templates- Spec vocabulary stabilized in 1.0
- Symmetric
--scope=business|technical|bothinterview - Source-tagged capture with mandatory read-back
- PR-as-cognitive-aid generation
- Agent-native memory audit and migration
- PR feedback resolver
- Strategy and glossary grounding
- Ralph autonomous mode with receipts
Source of truth
Section titled “Source of truth”The canonical changelog lives in the Flow-Next repository:
What belongs here
Section titled “What belongs here”Use this page to explain release highlights for humans:
- new slash commands
- changes to spec or task semantics
- review receipt changes
- migration requirements
- breaking or deprecated behavior
- docs, team workflow, or Ralph changes that alter how people should work
The repository changelog remains canonical. This page should summarize the current public story, not duplicate every commit.
1.1.4 note
Section titled “1.1.4 note”Use ## Acceptance Criteria in new specs and examples. Flow-Next still parses legacy ## Acceptance and ## Acceptance criteria headings so existing specs do not need a migration.
Release checklist
Section titled “Release checklist”flowchart LR Change["Behavior change"] --> Docs["Update docs"] Change --> Tests["Run tests"] Docs --> Changelog["Update changelog"] Tests --> Release["Cut release"]
If Flow-Next behavior changes and the docs site does not change, assume the release is incomplete until proven otherwise.