[bug] All the repositories shows the commit as "latest"

[deusmachinea]

What happened?

I indexed lots of repositories on my local machine and when I listem them all after 4 days.
They all have the commit "latest" even though they all have commits on top of them.

Steps to reproduce

1.Bytebell boot
2. Bytebell index <repo_url>
3. Wait for three days.
4. Bytbell ls "shows commit "latest"

What did you expect to happen?

The commits at which the indexation was done.

Bytebell version

0.4.2

Which part of Bytebell is affected?

No response

LLM provider

None

OS and architecture

No response

Bun version

No response

Logs or error output

Anything else?

No response

Before you submit

• I searched existing issues and didn't find a duplicate.
• I've redacted any secrets from the information above.

[Dorivika]

I was able to reproduce the bad state at the metadata/listing boundary: when a GitHub knowledge entry has commitId: "latest" but also has a real indexed SHA in commitHashes, bytebell ls was trusting commitId directly and printing latest.

The fix makes the listing path resolve the indexed commit from validated Git SHAs only. If commitId is not a full 40-character SHA, ByteBell now falls back to the newest valid SHA in commitHashes. I also added guards so future writes cannot persist "latest" as a commit, and updated pull no-op checks to use the same normalized commit resolution.

I added tests for the reported "latest" case, legacy commit history shapes, uppercase hashes, invalid hashes, duplicate history entries, and empty/missing commit history.

All tests passed.

The direct repro now resolves from:

{
  "beforeCommit": "latest",
  "afterCommit": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
}