[P3.7] Bulk/overwrite CLI ops are non-atomic or overwrite without confirmation — batch fix

[frankbria]

Severity: low | Category: data-integrity | Phase: P3.7

Problem

tasks set --all commits per-task and aborts mid-loop on an invalid transition (partial state); init --generate-config overwrites an existing CODEFRAME.md with no --force; batch stop/status/follow silently act on the newest of an ambiguous prefix; batch follow double-counts due to reversed event ordering.

Evidence

codeframe/cli/app.py:2138 (tasks set --all), :217 (init --generate-config), :4068 (ambiguous batch id), :4377 (batch-follow double-count)

Acceptance criteria

Bulk update pre-validates or reports partial progress; config write guarded by --force/confirm; ambiguous batch id errors with candidates (like work start); batch follow resumes from the newest event / guards non-idempotent counters.

Dependencies

None

---

_{Filed from the SaaS launch-readiness audit. Atomic: one developer, one session. Work order: strictly P0.1 → P3.12 (no forward dependencies).}

[coderabbitai]

🔗 Related PRs

#234 - fix(ui): make TaskStats phase-aware to fix late-joining user bug [merged]
#382 - fix: return non-zero exit codes from work retry and batch run [merged]
#440 - feat(core): per-state concurrency limits for batch execution [merged]
#450 - feat(config): dynamic configuration reload during batch execution (#402) [merged]
#537 - feat(core): WorktreeRegistry, orphan cleanup, and get_base_branch (#533) [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!