v0.2.8-alpha — Change-History Tracking

What's New

Change-History Workflow (Section 13)

Introduced .ddd/change-history.yaml — an append-only log that tracks every spec change across all four pillars (Logic, Data, Interface, Infrastructure).

Why this matters: Instead of running /ddd-implement --all (which regenerates everything, 5–30 min), you now run /ddd-implement with no flags and it implements only what actually changed.

Change sources — all four write pending entries to the same file:

• DDD Tool — when you save a project with canvas changes
• /ddd-update — after applying natural language spec changes
• /ddd-create — after generating a full project spec
• /ddd-sync — when detecting new spec logic drift

Entry format:

- id: "chg-0001"
  timestamp: "2025-01-15T10:30:00Z"
  source: "ddd-tool"          # or ddd-update, ddd-create, ddd-sync
  scope:
    level: L3                 # L1=domain, L2=domain+type, L3=specific item
    domain: "users"
    flow: "user-register"
    pillar: logic
  spec_file: "specs/domains/users/flows/user-register.yaml"
  spec_checksum: "a1b2c3d4e5f6"
  status: "pending_implement"  # → implemented after /ddd-implement runs
  implemented_at: null
  code_files: []

New command behavior:

• /ddd-implement (no flags) → implements pending entries only
• /ddd-implement --ignore-history → forces full scope selection
• /ddd-status → shows pending entries section
• /ddd-test (no flags) → scopes to recently implemented entries

Full documentation in DDD-USAGE-GUIDE.md → Section 13.