commit-bundleslisted

# Commit Bundles Review the dirty tree for an aidd-managed application, split related work into coherent commit bundles, and commit only validated, documented changes. ## Usage ``` commit-bundles <app> [--dry-run] ``` ## Arguments - `<app>` - Target app from `<applications-root>/AGENTS.md` or an explicit project path. - `--dry-run` - Group and describe bundles without committing. ## Workflow 1. Resolve the target to a local app directory and verify it contains `.aidd/`. 2. Run `git status --short` and `git diff --stat` in the target. Do not use `git stash`. 3. Group changes by user-facing outcome or metadata workflow. Keep unrelated generated files out of a bundle unless they were produced by that bundle's validation. 4. For each bundle, confirm documentation and aidd metadata are accurate: - update affected `.aidd/features/*/feature.json` when behavior changed; - update `.aidd/CHANGELOG.md` only when the app's workflow expects it; - leave roadmap propagation to aidd: it applies the roadmap when the run ends and reports the `updated / unchanged / errors` summary. Do not shell into the aidd installation for it. 5. Validate before committing: - `bun run format` in the target when available; - leave feature-contract validation to aidd: it re-validates every record when the run ends and reports what it found; - targeted tests for code changes; - `bun run smoke:qc` before claiming the app is working. 6. Commit each evidence-backed bundle with a c