v0.7.3

Fixed

• An undo or travel no longer reports files as restored when something else wrote them while it ran (a formatter or
  codegen still going). It checks each file again just before writing it, leaving one changed since the restore
  began as it is, and checks every file against the snapshot afterwards. If any differ, it says the restore is
  incomplete, lists them with a diff, and marks the snapshot "(incomplete)".

v0.7.2

Fixed

• The band's keys are digits, pressed at an empty prompt as you answer Claude Code's surveys: 1 undoes the turn, 2
  reviews it, 3 undoes its sensitive changes. Before, they needed the band to have the focus, which some terminals
  (Warp) never gave it. An undo asks once more, so one stray digit undoes nothing.
• The band stays until you send the next prompt. A turn Claude starts by itself, such as after a background task ends,
  no longer clears it.
• After /tm undo, /tm redo or /tm travel, and an undo from the pane, the band shows what was done instead of
  still offering to undo the turn.
• A long prompt is cut at a word with … in titles, not in the middle of one.
• /tm projects says when a project last changed in seconds, minutes, hours or days, not "0d ago".
• The status line counts this session's turns ("3 turns this session, undoable"), not every turn of the project.

Added

• On a Claude Code older than 2.1.287, the time machine says so and stays off instead of half working.
• README: how it compares with committing often, bashward and sandboxes, and how to uninstall it.

Changed

• The security diff is now called sensitive changes in the docs and /tm help: it flags files worth a second look; it
  is not a security check. The README no longer promises your work is "safe", and says that what /tm prints becomes
  part of the conversation with Claude.
• The band says what a turn did in a sentence: "Claude edited 3 files, created 12 and deleted 4" instead of
  "Claude changed 3 modified · 12 created · 4 deleted".
• Undo, redo and travel say what they did the same way: "Restored 3 files, removed 12 and brought back 4".
• The pane's Travel to after is now Travel here and comes first; it also works on the baseline and checkpoints.

v0.7.1

Security

• Secrets are left out of snapshots: .env files (not .env.example), keys and certificates, .npmrc, .pypirc,
  .netrc, credentials and kubeconfigs are never copied, and undo and travel never write them, even from an older
  snapshot that holds a copy. A turn whose file tools wrote one still flags it in the security diff. In a history made
  before this, the next snapshot records them as removed from snapshots (not from your project); older snapshots keep
  their copies until the history is deleted with /tm projects rm N --yes.

Added

• /tm secrets keep | skip: keep secrets in a project's snapshots, so they can be undone, or leave them out.

v0.7.0

Added

• Security diff: after a turn that touched CI config, git hooks, dependencies or an install script, secrets, container
  or infrastructure config, a new executable or many deleted files, the band says what with Undo these (x) to
  revert only that. /tm show lists it under "Sensitive" and the pane marks those files.
• /tm undo [N] --sensitive: revert only what the security diff flags in a turn.

v0.6.0

Added

• /tm heat: where Claude worked, as a treemap of the project in a pane (folder by folder, colored by Claude's
  churn, rework, undos or Claude's share against everyone else's) plus the hottest files. Picking a file lists the
  turns that changed it.
• /tm heat open: the same map as a self-contained, zoomable HTML page opened in the browser.
• npm run sandbox for contributors: a throwaway project with a real history, and --run to run every /tm
  command on it through claude -p.

Changed

• The README has license and support sections.

v0.5.0

Changed

• Source code moved to src/; the time machine is split into the shadow repository, history, pending turns, restore
  and prune modules. No change in behaviour.
• Code is formatted with Prettier, checked in CI.

Added

• Release workflow: pushing a v* tag publishes a GitHub release from this changelog.
• CI checks that package.json, plugin.json and the changelog agree on the version.
• Contributing guide, security policy, code of conduct, issue and pull request templates.