v0.2.14-alpha — Change-History Tracking + Reliability

What's New

Change-History Tracking

The DDD Tool now writes to .ddd/change-history.yaml whenever you save a project. This enables incremental implementation — instead of /ddd-implement --all (which regenerates everything), you run /ddd-implement with no flags and it implements only what actually changed on the canvas.

What gets tracked:

• Flow node/connection edits → L3 entry (domain + flow + pillar: logic)
• Domain add/delete → L1 entry
• Flow add/delete → L2 entry

Entry format:

- id: "chg-0001"
  timestamp: "2025-01-15T10:30:00Z"
  source: "ddd-tool"
  action: "updated"           # created | updated | deleted
  scope:
    level: L3
    domain: "users"
    flow: "user-register"
    pillar: logic
  spec_file: "specs/domains/users/flows/user-register.yaml"
  spec_checksum: "a1b2c3d4e5f6"
  status: "pending_implement"
  implemented_at: null
  code_files: []

Reliability Fix

• Flush pending saves on project close — debounced saves that hadn't fired yet are now flushed before the project closes, preventing silent data loss on quick close after edit.