changelog-rewritelisted

# Changelog Rewrite Replace a mechanically generated changelog (one version bump per feature/vertical) with a meaningful, phase-grouped changelog using proper `0.x.y` pre-release semver. Also corrects all version references across the project. ## Usage ``` changelog-rewrite [app] ``` ## Inputs When invoked, determine the target project: 1. If a path is provided as an argument, use it directly 2. Otherwise, use the current working directory **Required files:** - `docs/CHANGELOG.md`: the existing changelog to rewrite - `package.json`: root package.json with version field **Optional files (read for context if present; do not bump their versions):** - `backend/package.json` - `frontend/package.json` If `docs/CHANGELOG.md` does not exist, create it from the available Git history. ## Instructions ### Phase 1: Gather Build History 1. **Read the existing changelog** to understand what the script produced: ```bash # Read existing changelog cat docs/CHANGELOG.md ``` 2. **Get full commit history with dates:** ```bash git log --oneline --reverse --format="%h %ad %s" --date=short ``` 3. **Count commits to understand scale:** ```bash git rev-list --count HEAD ``` 4. **Read package.json files** to get current versions: ```bash cat package.json cat backend/package.json 2>/dev/null cat frontend/package.json 2>/dev/null ``` ### Phase 2: Identify Build Phases Analyze the commit history and existing changelog to i