Enrich checkpoint cli_version with tag and dirty state

[pjbgf]

https://entire.io/gh/entireio/cli/trails/432

Enrich metadata.json's cli_version field with version + dirty information.

versioninfo.CheckpointVersion() now mirrors Go's pseudo-version scheme
via runtime/debug.ReadBuildInfo(): release/nightly/mise builds keep their
ldflags Version and gain a "+dirty" marker when vcs.modified was set at
build time; plain go build binaries fall back to the embedded module
pseudo-version (e.g. v0.6.3-...-15d80761c74b+dirty), which already
carries the last known tag, the originating commit, and the dirty marker.

---

Note

Low Risk
Metadata field format change only; no auth or runtime behavior changes beyond richer version strings on new checkpoints.

Overview
Checkpoint metadata now records a richer cli_version via versioninfo.CheckpointVersion() instead of the plain ldflags Version.

WriteCommitted sets CLIVersion on both root CheckpointSummary and per-session CommittedMetadata using that helper. Stamped release/nightly/mise builds keep their ldflags version and append +dirty when vcs.modified was true at build time; local go build binaries with Version == "dev" fall back to the Go toolchain’s embedded module pseudo-version (tag, commit, dirty state).

versioninfo adds describe, readBuildInfo, and table-driven TestDescribe. Checkpoint tests assert CheckpointVersion() in agent and CLI-version coverage. fetch_no_config_pollution_test drops an unused checkpoint import and uses v2CheckpointFixtureOptions for the export fixture.

^{Reviewed by Cursor Bugbot for commit ca2c1cf. Configure here.}

[Copilot]

Pull request overview

This PR adds an Entire-Version git trailer to committed checkpoints on entire/checkpoints/v1 so each checkpoint commit message records the CLI build version that created it. It introduces version formatting that preserves release/nightly versions verbatim while augmenting local dev builds with the short commit digest.

Changes:

• Added versioninfo.FormatVersion and versioninfo.CheckpointVersion helpers for checkpoint provenance version strings.
• Introduced trailers.VersionTrailerKey (Entire-Version) and appended it to committed checkpoint commit messages.
• Added unit tests for version formatting and extended committed checkpoint tests to assert the new trailer is present.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
cmd/entire/cli/versioninfo/versioninfo.go	Adds version formatting helpers and a checkpoint-focused accessor.
cmd/entire/cli/versioninfo/versioninfo_test.go	Adds unit coverage for FormatVersion.
cmd/entire/cli/trailers/trailers.go	Defines the new Entire-Version trailer key constant.
cmd/entire/cli/checkpoint/committed.go	Writes Entire-Version trailer into committed checkpoint commit messages.
cmd/entire/cli/checkpoint/checkpoint_test.go	Verifies the committed checkpoint commit message includes the new version trailer.

[Soph]

@pjbgf why as a trailer and not in metadata.json?

[pjbgf]

@Soph fair point, we already have a version field in the metadata.json. Let me just amend that to ensure we have some sort of version/hash for dev versions instead.

[pjbgf]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit ca2c1cf. Configure here.}

[pjbgf]

Note to self: test with #1273 before merging.

[toothbrush]

Ah, i just saw this – i feel like #1273 probably already does what you need?