feat: extend --version with commit, date, dirty flag, and build profile

[justin13888]

Add Commit, Dirty, BuildDate, and BuildProfile ldflags variables so --version outputs granular build identification details. Falls back to debug.ReadBuildInfo() for dev builds without injected ldflags.

Update Makefile to inject all metadata for build/install/install-dev/ build-all targets, and .goreleaser.yml to pass ShortCommit, Date, and profile=release for release pipeline builds.

[justin13888]

This resolves #227

[marcus]

Hey @justin13888! Starling here (AI assistant on the project). 👋

Nice — this is the standard Go pattern for build info, done right. A few observations:

• ✅ Using -ldflags for injection is the idiomatic approach and keeps the binary lean
• ✅ The debug.ReadBuildInfo() fallback for dev builds is a solid touch — no broken --version in local builds
• ✅ Updating both Makefile and .goreleaser.yml so release and local builds are consistent
• ✅ The dirty flag will be genuinely useful for bug reports ("are you on a clean build?")

The output format in the issue looks clean and readable. Flagging @marcus to review and merge — this one seems pretty ready. ✦

[marcus]

Hi @justin13888, and apologies for the long silence here. You got a comment back in March saying this looked ready to merge, and then it sat. That is on me.

Here is where things landed. Since this PR opened, the managed dev install path in scripts/dev-install.sh started encoding branch, commit, and dirty state directly into the version string, so a local build now reports something like sidecar version devel+main.577c47fc, and make install-status records which sibling module revisions were compiled in. That covers most of what issue #227 was asking for, but through a different design than this PR: one composite version string rather than separate ldflags variables. The two approaches conflict, and reconciling them means reworking dev-install.sh as well, which is a different piece of work than what you signed up for.

So I am closing this rather than asking you to rebase into a moving target. I want to be clear that the PR was not the problem. It was clean, and it sat too long, and the ground shifted underneath it.

The part your PR solved that is still unsolved is release builds. Goreleaser still injects only the bare version, so a Homebrew binary cannot be traced back to a commit or a build date. Rather than leave that on the floor, I am pulling that piece of your work in directly, adapted to fit the current version scheme, with you credited on the commit. #227 stays open until it lands.

Thanks for the contribution, and sorry again for the wait.