v0.1.6

Highlights

• Version provenance in every command. tangly check, build, and migrate now stamp the running version into their output, and validation errors print a footer naming the version that produced them. This makes the most common upgrade false alarm self-diagnosing: a stale global install (npm i -g tangly) shadowing a freshly-updated local one on PATH, where npm list tangly reports the new version but the typed tangly command still runs the old global. The footer points you straight at tangly --version.
• Update notifier. In an interactive terminal, the CLI checks npm at most once every 12 hours and prints a one-line notice when a newer tangly is published, with the upgrade command. It is fail-silent (offline or slow registry: nothing prints), never runs in CI or piped output, and opts out with TANGLY_NO_UPDATE_CHECK or NO_UPDATE_NOTIFIER.

Prompted by @quader864's follow-up on #6: the reported errors were a stale global binary, not a schema bug. These changes make that obvious next time.

Changes

Features

• feat(cli): stamp running version in output + npm update notifier (#6, 0f437cc)